you can do something really cool called webmentions where your tweets will basically ping back to your website so you can have all your content forever. i would never do that bc most of my twitter is shitposts but i would love to see if there's something similar for instagram— christina (@_christinadan) October 17, 2020
Another interesting option is @KevinMarks’s noterlive.com which will compile your threaded tweets for cutting/pasting HTML to your site. Perhaps one day he’ll add Micropub functionality as well?
I’m hoping that future versions of this provide the Twitter permalinks for the syndicated copies there to be returned to my WordPress site for storage. In my case, I’m using the simple Syndication Links plugin which has storage and/or finds the storage location in WordPress to allow for the display of those permalinks in my post to indicate where I’ve syndicated the copies. This does two things: it’s a reminder of where my content lives elsewhere on the web (especially if I later want to go back and delete them, or to delete them if I’m deleting or making the original post private/unpublished) and it allows services like Brid.gy to find my original post and backfeed replies to the Twitter versions back into the comments section of my post using the Webmention spec (via the Webmention plugin and the Semantic Linkbacks plugin).
Soon after I finally took the leap and signed up for a mico.blog to explore that platform. ❧
Be sure to check out how you can post your content to your own website and syndicate your material into micro.blog (maybe via RSS or using plugins). If your site uses the Webmention and Semantic Linkbacks plugins, then any replies to your posts will be automagically ported directly back to the comment section of your post.
In addition to some of the others in education who you’ve mentioned, I’ve got a list with some others (be sure to check the comments too–both for the others you’ll find, but also for the example Webmentions I’ve received from Micro.blog.)
Annotated on September 26, 2020 at 01:57PM
I am going to start getting serious about headless WordPress development for my new website at jimgroom.net, inspired by Tom Woodward’s talk for #HeyPresstoConf20 ❧
A lot of the posts I make to my WordPress site are done in a headless manner using the Micropub spec and the Micropub plugin with a huge wealth of Micropub clients.
I did a presentation on this at a WordCamp a while back: https://wordpress.tv/2019/06/26/chris-aldrich-micropub-and-wordpress-custom-posting-applications/
Annotated on September 26, 2020 at 01:59PM
Chris Aldrich ❧
By linking my site here, Jim has sent a Webmention notification, so I know he posted about my site: https://telegraph.p3k.io/webmention/14qD8olgI7lyGjRy0q/details
Annotated on September 26, 2020 at 02:27PM
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.
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.
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.
(p.s.: Great Twitter handle!)