#microblog
-
Don't forget: Next week is the Homebrew Microblog Meetup in Portland! 💬🍻 Thanks to @oktadev for sponsoring drinks! https://indieweb.org/events/2018-04-18-homebrew-microblog
-
🔔 The Homebrew Microblog Meetup is tonight! 6pm at Rogue Eastside! 🎉🍻 And a great sunny day for it too! ☀️ #indieweb #microblog #pdx https://indieweb.org/events/2018-03-14-homebrew-microblog
-
Homebrew Website Club PDX is back, and joining forces with the Microbrew and Microblog meetup! Come to Rogue Eastside this Wednesday for the first "Homebrew Microblog"! https://indieweb.org/events/2018-03-14-homebrew-microblog #indieweb #microblog
-
Sunlit 2.0 Released as a Micro.blog and WordPress Photo Blogging App – MacStories (www.macstories.net)
-
Stepping back a bit, I think we should look at the end goal from the users perspective.
This seems to be a problem primarily when both people have their own website and their content is automatically pulled into micro.blog from their own feeds.
With that in mind, the best solution is one which will require the least amount of behavior change as well as technical change on behalf of both people. This likely means micro.blog will have to do some additional work, but that seems appropriate since in this situation micro.blog is acting as an aggregator between two independent websites.
The way micro.blog can best facilitate this kind of interaction would be to match up the replies itself, and not require any additional steps for the user replying. Since micro.blog is already consuming a feed from my site, if it encounters any posts in that feed with an in-reply-to url, micro.blog should check whether that url is one of its own, or whether it's indexed as a canonical url from someone's site that it has also previously pulled in. Then it can match up the conversation thread. If there is no match, then a perfectly acceptable first version would be to just ignore the post and not pull it in to micro.blog at all. This way neither the person replying nor the person being replied to need to fiddle with any markup or make additional feeds or make decisions about syndicating at each post.
I believe JSONFeed has the concept of an in-reply-to url, but Atom/RSS do not. This means this feature will only work with JSONFeeds, but I think that is an acceptable compromise. Of course if micro.blog started consuming h-entrys that would also work but that's a different conversation. -
Multi-Photo Support in OwnYourGram
After far too long, I finally launched support for importing multi-photos from Instagram via OwnYourGram!
The OwnYourGram dashboard showing a multi-photo post I used for testing I had to make a couple tough calls, which I'm not entirely happy about, but I think it's an acceptable compromise for now. The main limitation of the way it currently works is that Instagram posts that mix photos and videos in the same post will import the videos as just their poster frame. Additionally, you can tag people in the individual images on Instagram, but when that's converted to a Micropub request and sent to your site, the person tags are combined into one list associated with the main post.
The multi-photo post rendered on my website The reason for doing it this way is there were already several websites and Micropub implementations that support the "multi-photo" concept, but very few that support "collections." The difference is a multi-photo is a single h-entry that has multiple photo URLs, whereas a collection is an h-entry that contains multiple h-entrys inside of it. The collection concept allows a much richer representation of things, since you can have a collection containing photos, videos, or anything really, and each h-entry within the collection can have its own tags, person-tags, etc. There are some more notes on the advantages and limitations of each on the IndieWeb wiki.
But right now, there are very few implementations of collections at all, and as far as I know, nobody's Micropub endpoint supports creating collections anyway. In contrast, there are several examples of multi-photos along with support in Micropub endpoints, including recent support for it in micro.blog. So that's a compelling argument for making OwnYourGram support the simple case first, and eventually I'll see about adding support for full collections later.
Since not everyone's site supports multi-photos, I decided that for all existing OwnYourGram users, I would maintain the existing behavior where it only posts the first photo to your site. This way I avoid surprising people with a new kind of Micropub request. If you're an existing user and want to accept multi-photos, then you just need to be prepared for the "photo" property to be an array, and you can enable multi-photo support in the settings. New users will have this enabled by default.
I talked about this upcoming change on episode 1 of my new microcast "Percolator," so please subscribe if you're interested in following along with other developments I'm thinking about!
Looking forward to seeing some multi-photos on all your websites!
-
Jackson Palmer
http://ummjackson.com
•
May 24
Anyone in the IndieWeb space know if http://micro.blog is going to be an OSS protocol vs. a closed source company?@ummjackson You can use the micro.blog iOS app to post to your own Micropub website, and the site also sends Webmentions! -
I have high hopes for @manton2's http://micro.blog Kickstarter project! Today's the last day to back it! https://www.kickstarter.com/projects/manton/indie-microblogging-owning-your-short-form-writing #indieweb
