The nice part is that this sort of model allows the user to collect this data and send these notifications on an as-desired basis to the publisher.
Replies
One can use a zero-width space (using something like ​
in their HTML) between the @ and a twitter user name on the original post and the syndicated copy will not have the traditional @mention link or notification functionality.
Here’s an example
- Original post: https://boffosocko.com/2020/09/17/55777062/
- Syndicated copy: https://twitter.com/ChrisAldrich/status/1306748549233815553
This reply can also serve as a test for the functionality within Github where I’ll “tag” both @kylewm and @snarfed, but if it works, Ryan shouldn’t be auto-linked or notified.
Here’s more on how I’ve thought about it before: https://boffosocko.com/2018/03/10/thoughts-on-linkblogs-bookmarks-reads-likes-favorites-follows-and-related-links/
The UI part that often bogs down the posting process is the complexity of Gutenberg or the myriad of meta-boxes. To remedy this I try to pair one of the many Micropub clients (I like Quill or Omnibear as flexible examples) for posting to my website and then allowing Post Kinds to handle the rest for creating reply contexts and posting the minimum necessary metadata.
One of my fav French bands dropped an album just recently and if you’re looking for something good to listen to this weekend, allow me to recommend it! https://open.spotify.com/album/1Eru3N6Rg0rxbV3DMdhhKU?si=OghhDlbOQ3ewu5o6fYpeVg
— Aram Zucker-Scharff (@Chronotope) August 28, 2020
Thanks, by the way!
There are lots of ways to syndicate content, some dependent on which platform(s) you’re using and where you’re syndicating to/from. Your best bet is to swing by the IndieWeb Dev chat and ask that very question.
Theorem: Syndication is easy.
Proof: “It’s easy to show” (I’m waving my hands here) that there are a lot of assumptions and baggage that go with the word “easiest.” ∎
I’ve personally found there’s generally an inverse relationship between ease/simplicity of syndication and control over exact display for most platforms. You could go low-fi and pipe your feed into something like IFTTT/Zapier for cross-posting all the way up to customized integration with available APIs for each platform. Many take a middle-of-the-road approach that I notice Jeremy recommended as I’m writing this.
The cross-posting wiki page will give you some useful terminology and definitions which may help you decide on how to syndicate what/where. Based on the context of the URL in your Twitter profile, the IndieWeb wiki pages for static site generator and syndication will give you some ideas and options to think about and explore.
Some of the pages about specific static site generators will give you some code and ideas for how to implement syndication. For example Max Böck has an article Indieweb pt1: Syndicating Content to Twitter, which is Eleventy and Twitter specific, but which could likely be modified for your purposes. SSGs may have some specific peculiarities for syndication that I’m not as familiar with coming from the more dynamic side of the fence.
Since you indicate a language preference for your current site, there’s also a page for Flask with a few users noted there. You might ask Fluffy (usually around in chat) for some advice as I know she syndicates to a few platforms and may have some ideas or even tools/code to share from the Flask perspective.
Q.E.D., right!?
(p.s.: Great Twitter handle!)
For more details look at Micropub and WordPress: Custom Posting Applications. It uses the W3C Micropub recommended spec and most of the current clients are open source if anyone wants to build their own web or mobile interfaces.
Sunlit for iOS is a Micropub compatible app that supports photos. PhotoPostr looks promising too for photos and collections.
If you want to go crazy to support some of the other niceties on your site, add Simple Location plugin for showing GPS location and weather conditions and Post Kinds plugin for custom (and customizable) photo display (meant to be compatible with Micropub, but doesn’t have Gutenberg support).
Here’s an example photo from this morning: https://boffosocko.com/2020/09/09/55776473/
Naturally it’d be awesome to see Micropub support in core.
It’s also the last time that Mt. Wilson was threatened, though tonight it’s from the East side of the mountain. I’m watching closely because I’m 8 miles from the Bobcat Fire to the East and we’re under an evacuation warning. Fortunately the live cam has some reasonably clear footage of the immediate danger as the observatory is 4 miles up the hill above us.
One person tinkers around with an idea and posts about how they did it. Someone else sees it and thinks it’s cool and wants it for themselves. They then modify it for their system, maybe with some changes or even improvements, and post the details on their site.
They’ve both syndicated copies to IndieWeb news or to the IndieWeb wiki, so that in the future, others looking for that sort of UI research or examples can find them and potentially modify them for their own personal use.
And the cycle begins anew…
This reads like Felix thinks the discover feed is the entire point of the platform and not simply a tangential discovery mechanism for new users. It feels like they didn’t realize they could subscribe to anyone they wanted and that feed is the one that most people find more valuable and use regularly.
It also reads like they weren’t getting any interaction at all in terms of replies/comments. Not sure if they had a paid account (and were just using micro.blog) or if they’re using their own site and just don’t have webmentions which means they have to manually go to find interactions.
On the other hand, micro.blog is doing a tremendous amount compared to simple silos like Twitter, Facebook, and Mastodon, so I’m not surprised that some people can misconstrue what is going on or even why. A lot of how you use it depends on what resources you have when you come to it. If anything though, micro.blog is the last thing out there that’s a walled garden in the social space.
Here’s an example of an event: https://2019.indieweb.org/summit and my RSVP to it: https://boffosocko.com/2019/05/30/55753006/ using this sort of set up.
There’s also a self-hostable service called Meetable that is IndieWeb friendly and accepts RSVP webmentions as well. If you’d like to test it out with your new webmention functionality, you can RSVP to one of the upcoming events at https://events.indieweb.org/. We’d love to have you join us if your schedule allows.
Other Meetup.com alternatives we’ve documented: https://indieweb.org/meetup.com#Alternatives