I’m especially curious about existing implementations anyone uses here on Lobsters. My Lobsters-based POSSEs have been manual so far; the only automated POSSE-ing I do is via a shell script that calls toot to post to the Fediverse.
I use this for my blog. I post to my blog and then have it poke another service that spreads out notifications. I wrote about it in my most recent talk.
You get the idea, the workflows looks for RSS feed from my blog, my public espial bookmarks and my public espial notes.
On any new item, it is published to twitter (and the bookmarks are copied to pinboard).
I did some manual POSSE to Lobsters in the past for comments, and when I’ve posted blog posts I’ve made sure I’ve recorded the syndication / cross post to Lobsters, but would prefer to move to more of a backfeed approach where I can write posts in the Lobsters UI then later they’ll automagically sync back to my site
The problem with PESOS is that it prevents original-post-discovery, undermining the “own your content” goal of the IndieWeb. POSSE-over-PESOS also fits nicely into the logic behind POSSE before sending Webmentions.
Backfeeding does make sense for aggregating responses, though. It’d be cool if Lobsters gave replies permalinks (rather than anchor-links) so we could enable that functionality…maybe I’ll file a ticket.
I can’t say it would be truly automatic, but if I had to spend a lot of time copying and pasting text across multiple sites, that’s when I’d start using some level of copy/paste and browser tab automation. Nothing fancier than echo $text | xclip -sel clipboard and using a firefox $url invocation to spawn each site’s URL to make a new post on. This is what I did for a job with not-so-great automation aspects.
I’ve been looking at this stuff as a way to drive traffic to my new blog but my sensibilities are at odds with that goal. I’ve tweaked my Markdown pipeline so much that I think at least 3 (out of less than 10) of my posts so far would fail to render properly anywhere else. I don’t like the idea of the full text of my stuff showing up on other sites. I should make a Twitter account and automatically cross post to that, but I deleted my Twitter account in 2016 and I can’t make myself sign back up. I do manually post links to my new stuff on my Mastodon account, but that’s even less discoverable, and somewhat on purpose.
Markdown tends to get flavored like that because it lacks so many features for actually writing anything beyond a comment or the simplest of READMEs. It’s a shame developers haven’t embraced more lightweight markup languages. It’s not just you, but you can’t even take the same Markdown document from GitLab and assume it renders fine on Gitea.
I appreciate the pragmatic approach the author is taking. Rather than building yet another castle in the clouds that we then need to struggle to get non techies to adopt, we’re bringing our content to them where they live.
I’m especially curious about existing implementations anyone uses here on Lobsters. My Lobsters-based POSSEs have been manual so far; the only automated POSSE-ing I do is via a shell script that calls
tootto post to the Fediverse.I use brid.gy a lot
I am using my own[1] to cross-post to mastodon[2], pleroma[3], pinboard[4] and twitter[5] accounts. The last via https://crossposter.masto.donte.com.br/.
Currently rewriting to be an activitypub instance on it’s own[6].
[1] http://mro.name/shaarligo
[2] https://digitalcourage.social/@mro
[3] https://pleroma.tilde.zone/@mro
[4] https://pinboard.in/u:mro/
[5] https://twitter.com/mrohrmoser
[6] https://seppo.app/en/
I use this for my blog. I post to my blog and then have it poke another service that spreads out notifications. I wrote about it in my most recent talk.
I personally self-host an espial instance (https://github.com/jonschoning/espial). Then I also self-host a node-red instance (https://nodered.org) where I created 4 workflows:
You get the idea, the workflows looks for RSS feed from my blog, my public espial bookmarks and my public espial notes. On any new item, it is published to twitter (and the bookmarks are copied to pinboard).
More details:
https://her.esy.fun/posts/0004-how-i-internet/index.html
I did some manual POSSE to Lobsters in the past for comments, and when I’ve posted blog posts I’ve made sure I’ve recorded the syndication / cross post to Lobsters, but would prefer to move to more of a backfeed approach where I can write posts in the Lobsters UI then later they’ll automagically sync back to my site
See also: https://indieweb.org/PESOS
The problem with PESOS is that it prevents original-post-discovery, undermining the “own your content” goal of the IndieWeb. POSSE-over-PESOS also fits nicely into the logic behind POSSE before sending Webmentions.
Backfeeding does make sense for aggregating responses, though. It’d be cool if Lobsters gave replies permalinks (rather than anchor-links) so we could enable that functionality…maybe I’ll file a ticket.
I can’t say it would be truly automatic, but if I had to spend a lot of time copying and pasting text across multiple sites, that’s when I’d start using some level of copy/paste and browser tab automation. Nothing fancier than
echo $text | xclip -sel clipboardand using afirefox $urlinvocation to spawn each site’s URL to make a new post on. This is what I did for a job with not-so-great automation aspects.I’ve been looking at this stuff as a way to drive traffic to my new blog but my sensibilities are at odds with that goal. I’ve tweaked my Markdown pipeline so much that I think at least 3 (out of less than 10) of my posts so far would fail to render properly anywhere else. I don’t like the idea of the full text of my stuff showing up on other sites. I should make a Twitter account and automatically cross post to that, but I deleted my Twitter account in 2016 and I can’t make myself sign back up. I do manually post links to my new stuff on my Mastodon account, but that’s even less discoverable, and somewhat on purpose.
Why not just post the title and the link to your blog posts? It’s what I do for Facebook and Linked In (manually).
Markdown tends to get flavored like that because it lacks so many features for actually writing anything beyond a comment or the simplest of READMEs. It’s a shame developers haven’t embraced more lightweight markup languages. It’s not just you, but you can’t even take the same Markdown document from GitLab and assume it renders fine on Gitea.
The linked page says you don’t have to:
Just a link and a summary would probably be okay as well, right?
I appreciate the pragmatic approach the author is taking. Rather than building yet another castle in the clouds that we then need to struggle to get non techies to adopt, we’re bringing our content to them where they live.