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
I wish I could do this with @withKnown - A New Way to Publish Your Blog Posts Simultaneously as Twitter Threads : https://t.co/FfTWMS0WIE
— Ricardo rmdes@mstdn.social (@rMdes_) October 15, 2020
WordPress should do a tool that goes the other way.
— dave@scripting.com (@davewiner) October 14, 2020
Let's you write a blog post in a series of tweets.
I know that probably seems counter-intuitive, but I learned today a fair number of users don't like the new block editor.
Twitter is, these days, a fairly fluid writing toolTry https://t.co/owWreGPP3J, it publishes twitter threads to blog posts via https://t.co/L8te8TddXN
— chaodoze (@chaodoze) October 14, 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'd also like to find a way to say thank you to Aaron Parecki who built webmention.io and Ryan Barrett, Kyle Mahan, et al who built brid.gy. However, I can't see a way to do either and, indeed, the latter explicitly say "We don't need donations, promise." ❧
Jetpack 9.0, coming on October 6, will debut a new feature that allows users to share blog posts as Twitter threads in multiples tweets. A recent version of Jetpack introduced the ability to import and unroll tweetstorms for publishing inside a post. The 9.0 release will run it back the other way so the content originates in WordPress, yet still reaps all the same benefits of circulation on Twitter as a thread.
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).
Chris Aldrich (BoffoSocko)Testing out adding email reply links to my RSS feed using the All In One SEO plugin documentation at: https://semperplugins.com/documentation/rss-content-settings.
"Multi WP Blog Search" - simple, straightforward tool for searching across the multiple WordPress sites that you choose to list - https://t.co/1je6xMlxFa
— Ian Guest (@IaninSheffield) September 25, 2020
*This* is why you always need to keep an eye on what @johnjohnston is up to. It slipped under my radar 1st time around.I too missed John's search tool, opps. Thank you for sharing it on Ian.
— Aaron Davis (@mrkrndvs) September 27, 2020
It has me thinking about @ChrisAldrich's recent reference to blogrolls/OPML. I wonder if something could be added to be able to search across the various sites listed on your own site?I think it would be a bit slow to get results from a lot of sites. Limited to WordPress too.
— john johnston (@johnjohnston) September 27, 2020
Jim Groom (bavatuesdays.com)This past Tuesday I attended the second Indie WebCamp generously hosted by Chris Aldrich focused on Domain of One’s Own. The format is a more focused 10-15 minute talk around a specific technology, in this meeting Tim gave folks a walk-though of Reclaim Cloud, and then opens up to the 21 attendees for anyone to share something they are working on. Tim shared the Cloud, and not only was I thrilled to see Jon Udell in attendance, but it’s always nice when one of your tech heroes tweets some love for your new project. Even better when you know they’re not one to offer empty interest and/or praise. Thanks Jon!
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
I wonder about this too! I mean, webmentions tell me who wants to really engage with my posts or whatnot, but not who dropped by to read. And yet I don't really want to deploy something as invasive as GA.
— @maya@occult.institute (@kixiQu) September 21, 2020
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.
Twitter interprets microsyntax whenever you post. There's no way around it. So if you have a post whose plain text says "Blah blah with @singpolyma" there is no way to tell twitter that "@singpolyma" is not the user named "singpolyma" and it will notify said user no matter what. In a silo this works, but when bridging to a federated environment it can cause issues (and especially annoyance of Twitter users).
One way to deal with this is to have my local implementation detect any such cases and not bridge them to Twitter, but this is not ideal. What should brid.gy do if it is asked to post something with the text @singpolyma in it? Here is my proposal:
- For the source HTML
@singpolymaI would suggest changing it to "@ singpolyma", however I could see an argument to also leave it as-is, since some users might be writing plain-text microsyntax and expecting it is always going to Twitter? Hmm.- For the source HTML
@<a href="https://twitter.com/singpolyma">anything</a>put "@singpolyma" into the tweet.- For the source HTML
@<a href="https://singpolyma.net">anything</a>put "@ singpolyma.net" into the tweet.Thoughts?
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
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.
Tantek Çelik (GitHub)The current h-entry change control process does not specify how to update the definition of a proposed feature, which means it falls back to being as strict as updating a stable feature which is more strict that desired for proposals. This issue is for considering a proposal for updating the definition of a proposed feature, as discussed during the recent Microformats Issue Resolution pop-up.
Proposal: the definition of a proposed feature may be updated to be more consistent with one or more real world public web sites publishing and or consuming the feature, by citing URLs for those examples in an edit summary. New proposed property or value definitions may also be added for consideration per the existing requirements for adding a proposed feature. If you’re not sure whether to update an existing definition or add a new definition, try to work with the proposer(s) of an existing definition to come to a consensus to update it. Lacking consensus, add a new definition for consideration, retaining any previous definition(s).
This proposal also adds a convergence requirement for moving a feature from proposed to draft. If there are multiple definitions for a proposed feature, an issue must be opened to discuss how to converge the definitions by consensus agreement among those with real world public web sites publishing and or implementations consuming the feature.
This is a rough first draft, feel free to propose alternatives, simplifications, editorial suggestions.
(Originally published at: https://tantek.com/2020/259/b2/)
I am using the Quill client to send data to my site. I have not tried out any other micropub clients but I could if I wanted to. They all support the same standard. ❧
When I think about it, likes and bookmarks are somewhat difficult to distinguish for my purpose. A bookmark inherently implies that I liked a post because I usually only bookmark posts on Pocket that I like and want to save for later. I use Firefox bookmarks to track the articles that I have not yet read and want to come back to later. There is a distinction. A like is clearer. It’s my way of saying that I did like your content. Not everybody will know my policy on bookmarks, so having a like feature is useful. ❧
Tell me what you dream of seeing in WordPress, whether your jokes or your most serious hopes, I'm not making product decisions so this doesn't constitute a promise, I just want to hear about it and get my brain back into that mode again :)
— Helen 侯-Sandí (@helenhousandi) September 8, 2020I've always been lowkey bummed that post formats got shelved.
— Jason Cosper (@boogah) September 8, 2020
Now that Automattic owns Tumblr, maybe it's a good time to revist that concept.I loved post formats. Learning how to add integration for them in child themes and designing each taught me so much PHP.
— Courtney Robertson (@courtneyengle) September 9, 2020
I'd like to see more psuedo HTML without learning markdown. In the block editor, type /hr. Now do that with all the things. /h2 please.
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.
I want to get started with #indieweb what is the easiest way to do that? Esp wrt syndication tools
— the big cauchy/cosh(y) couch (@fourierfiend) September 10, 2020
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!)
