WeChat ID
aaronpk_tv
#Micropub
-
Sunlit 2.0 Released as a Micro.blog and WordPress Photo Blogging App – MacStories (www.macstories.net)
-
Just implemented mp-destination on my site! I can connect multiple Micropub or Twitter accounts to my site to be able to post to other accounts from Micropub clients when I'm logged in as me. This is the first step of turning Monocle into more of a Tweetdeck-like experience!
-
EdwardHinkle
https://github.com/EdwardHinkle
•
Feb 20
Yep, exactly. Or a specialized app like Teacup that sends ate and drank posts. Those should still go through regardless.
As you said, @manton, it's more of a suggestion but especially a suggestion for generalized Micropub application, as opposed to specialized.
That makes sense, and also fits nicely with the idea of this as an extension rather than part of the base spec. -
manton
https://github.com/manton
•
Feb 20
@aaronpk I'm glad you mentioned Post Type Discovery, because to me that is the part to focus on. It seems too complicated to require spelling out every property, like category or photo. If an endpoint doesn't support accepting a category on a new post, no harm done.
What can we borrow from the Post Type Discovery spec that will help here? At the very least it seems like the Microformats class names should be consistent.
In my example (https://indieweb.org/Micropub-brainstorming#Query_for_supported_vocabulary) I included what I view as the common actions from an app like Indigenous: like-of, repost-of, and bookmark-of, but bookmarks aren't actually mentioned in Post Type Discovery. I wonder if they should be, or are they not different enough from a regular post to list separately?
Interesting, I didn't actually realize bookmark wasn't in Post Type Discovery. It looks like it was mentioned under "Other Types Under Consideration" before it was moved to the W3C repo. Now the W3C note links to the Kinds of Posts section on the IndieWeb wiki for that.
The way we were adding things to the list of types in the algorithm was roughly based on how well-established the markup was in the wild. I am kind of surprised bookmarks didn't make that cut, but oh well.
The one potential confusion here is that post types are not the same as
h-*types, e.g. there is noh-replybecause you use thein-reply-toproperty onh-entryto create a reply post. I think that just means we need to be explicit about what to call this. To build on your previous example, this could be a solution:{ "post-types": [ { "type": "note", "name": "Note" }, { "type": "article", "name": "Blog Post" }, { "type": "photo", "name": "Photo" }, { "type": "video", "name": "Video" }, { "type": "reply", "name": "Reply" }, { "type": "like", "name": "Like" }, { "type": "repost", "name": "Repost" }, { "type": "rsvp", "name": "RSVP" }, { "type": "bookmark", "name": "Bookmark" } ] }Clients should assume that if it's not in the list, then the server doesn't support it? Of course there needs to be some sensible behavior for servers that don't return this info at all.
Would it make sense to omit
notefrom this list since that's kind of a baseline? Or keep it in the list because it allows the client to customize the name of the button still? -
manton
https://github.com/manton
•
Feb 20
@EdwardHinkle Sounds great! I can implement it at any time on Micro.blog, although first I wonder if anyone has feedback on the JSON key names.
One thing to note is these are all properties of the
h-entryvocabulary, whereas other kinds of posts support totally different properties. Things likeh-eventorh-reviewwhere they are completely different things. Continuing down this path it would make sense to scope these properties to note that they are part of theh-entryvocabulary.The other question is how many of the supported properties would need to be defined? If not all of them, (e.g.
photo,category,published) why these ones in particular?Is it because these correspond with post types? If that's the case, then maybe this should be somehow tied to the Post Type Discovery spec which spells out what properties map to what kinds of posts.
In that case, it may make more sense to have the server advertise which of these post types it supports, and then clients would look at the spec to know which properties to send to create those posts.
-
New Micropub library + XRay
curl https://example.com/micropub -X POST -d h=entry -d content="Hello World" \continue reading... -
Automatically POSSEing Likes and Reposts
My #newwwyear goal this year was to make my likes and reposts automatically POSSE to Twitter when I favorite a Tweet URL.continue reading... -
"Checked In By"
Swarm has had a feature for a long time where you can allow your friends to check you in. It's more than just tagging a friend in a checkin, since it actually creates a full-fledged checkin on the other person's account. It's an interesting feature of Swarm, and not something I've seen elsewhere.continue reading... -
Example delete and undelete flow when storing posts as flat files:
• Create a post on disk stored at e.g. `/web/2017/10/15/1/post.txt` which has a public URL of `http://example.com/2017/10/15/1/`
• When the client deletes the post, the server moves the file to `/web/.trash/2017/10/15/1/post.txt`
• If the client sends an undelete request, the request will include the former public URL of the file `http://example.com/2017/10/15/1/`
• Similar to how the server knows where to find the file for live posts, it should know how to find the post in the trash folder if it's been deleted
• The server can move the file back to the public folder `/web/2017/10/15/1/post.txt` to complete the undelete -
Herbert
http://public.lanl.gov/herbertv/
•
Jul 13
Hey @aaronpk, why are "shortlink" and "syndication" not included in the IANA Considerations section for W3C Micropub https://www.w3.org/TR/2016/CR-micropub-20160816/
@hvdsomp "shortlink" and "syndication" are already in the rel directory, Micropub didn't make those up: http://microformats.org/wiki/existing-rel-values -
Jeremy Keith
https://adactio.com
•
Jul 4
<input type="file">
I also use OwnYourGram and OwnYourSwarm by @aaronpk to post photos to my site’s micropub endpoint.
@adactio @growdigital <input type="file"> is totally underrated -
"The great thing about OwnYourSwarm is that I didn't have to do anything. I already had the building blocks in place" https://adactio.com/journal/12349
-
Micropub is a W3C Recommendation
I'm excited to announce that Micropub is now a W3C Recommendation! It's been a long road, but we made it! This is the final stage in the W3C spec lifecycle, and means that the spec has gone through several stages of review, and all parts of the spec have been implemented by at least two people.continue reading... -
@dropshareformac Basically I want to use Dropshare instead of this hacked up folder automation workflow https://aaronparecki.com/2016/11/02/5/screenshots
-
@dropshareformac Micropub is a @w3c Recommendation now! I'd love to use Dropshare as a Media Endpoint https://www.w3.org/TR/micropub/#media-endpoint
