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-entry vocabulary, whereas other kinds of posts support totally different properties. Things like h-event or h-review where they are completely different things. Continuing down this path it would make sense to scope these properties to note that they are part of the h-entry vocabulary.
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.
kaa
https://micro.blog/kaa
•
permalink
@aaronpk WAAAAAY to much work. @replies should just be an option that gets published on your site somewhere automatically. Feature request.
adrianizq
https://micro.blog/adrianizq
•
permalink
@aaronpk I added the webmentions plug in on my WP site. Just not exactly sure how to use it. Can you link an example?
adrianizq
https://micro.blog/adrianizq
•
permalink
@aaronpk I’m a complete noob. How do I do this???
mdhughes
https://micro.blog/mdhughes
•
permalink
@manton Which makes replies problematic, since they're only hosted on m.b right now. I need a way to have my replies end up on my site, permanently.
This episode marks a full year that I’ve been creating weekly audio summaries of the IndieWeb newsletter! Thank you for listening!
I’d love any feedback that you have. Also, if you’d take a moment to leave a rating and a review wherever you get your podcasts, that’d be 💯!
I’d say the single most important lesson to take away here, for a technology project at least, is that interoperability is key.
- Assume that no matter how amazing your new tech is, people are going to adopt it slowly.
- Give your early adopters every chance you can to use your offering together with the existing tools that they will continue to need in order to work with people who haven’t caught up yet.
- And if you’re building a communication tool, make it as simple as possible for others to build compatible tools, because they will expand the network of people your users can communicate with to populations you haven’t thought of and probably don’t understand.
