Tag: PESOS

Replied to a thread by John-Mark Gurney, Dan McDonald, and Seth Wright (Twitter)
I’m pretty sure that many within the IndieWeb space have got this working with a variety of software, particularly using Bridgy for the responses. Here’s an outline of how I do it with WordPress https://boffosocko.com/2018/07/02/threaded-conversations-between-wordpress-and-twitter/

I’m always curious to see other implementations.

IndieWeb Syndication Sketchnotes: POSSE >> PESOS >> PASTA >> PESETAS >> POOSNOW
A sketchnotes diagram of IndieWeb Syndication practices featuring in decreasing order of desirability: POSSE, PESOS, PASTA, PESETAS, POOSNOW

I’ve been reading about sketchnotes for a bit this past week. As a first experiment I created some sketchnotes for a short talk on syndication in social media I prepared a while back. Here’s to hoping that no one ends up taking the actual spiral down to POOSNOW with their own social media presence.

Bookmarked Italic Type (italictype.com)
Italic Type is the simplest way to track your books, get trusted recommendations, and share the joy of reading with friends.
An interesting new competitor to Goodreads and Library Thing on the scene. The functionality is very limited in scope at present, but it’s rather pretty looking. Not nearly as fine grained as Goodreads in terms of data, but a good start.

I’ll have to look into the ease/value of starting into yet-another book silo though. I’d only really use it if I can get it to dovetail with posting to my own website as a syndication target (POSSE), or if I can use it to syndicate to my own site (PESOS).

 

IFTTT, when are you going to add the ability to add a “That” target using Micropub? Currently there is either native Microsub support or plugins for a variety of platforms or CMSs like WordPress, Drupal, micro.blog, WithKnown, Craft CMS, Jekyll, Kirby, Hugo, Blot, etc.

Similar to something like webhooks, these endpoints can be used to send a wealth of data from one place to another. Right now I can see a great use case for going from almost any target that’s currently supported to a variety of endpoints that are currently built for websites or blogging use cases.

Leveraging Micropub may also make it easier to target a simpler common “surface” instead of dovetailing with hundreds of individual CMS platforms and their APIs.

I’ve been able to use Micropub with Webhooks to get around the current IFTTT limitations, but there is a lot more you might be able to do with it as a company while making it easier for customers as well.

Replied to a tweet (Twitter)
@withKnown supports Micropub, so you could use @ThreadReaderApp to do it in the other direction before WordPress could. 

https://boffosocko.com/2020/05/28/threadreaderapp-micropub-to-blog/
Did you present at #HeyPresstoConf20 yesterday? You can use @ThreadReaderApp to quickly cross-post your entire presentation to your WordPress site with Micropub and a powerful plugin.

ThreadReaderApp now has beta support for the Micropub Spec so you can publish Twitter threads directly to your blog

Ten: A not-so “Hypothetical” Example

I use all the data I capture online using Hypothes.is to port my annotations, highlights, and notes I make online into my commonplace book.

#HeyPresstoConf20

More details and a video example:

Hypothes.is annotations to WordPress via RSS 

Nine: Micropub for collecting data

The Micropub plugin helps me by creating an endpoint on my site for quickly and easily capturing lots of data. IFTTT, Zapier, Integromat, n8n can all help to aggregate this data too.

#HeyPresstoConf20

Here are some more in-depth details about how I use some of these tools and recipes/walk-throughs so you can too: Using IFTTT to syndicate (PESOS) content from social services to WordPress using Micropub.

 

 

 

Replied to a tweet by @fourierfiend (Twitter)
Hello fellow mathematician!

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!)

Syndicating my IndieWeb Wiki edits to my personal website

I don’t have a specific “Edit” post kind on my website (yet!), but I’ve set things up–using a prior recipe–so that edits I make to the IndieWeb wiki are syndicated (via PESOS) to the Micropub endpoint on my website to create draft posts on my personal website!

Presently they were easiest to map to my website as bookmarks until I can create the UI to indicate edits, but changing the UI piece, and retroactively modifying some data for posts, should be fairly simple and straightforward for me.

I’m not sure I’ll keep the entire diff content in the future, but may just keep the direct text added depending on the edit and the potential context. We’ll play around and see what comes of it. It’s reasonably sure that I may not post everything publicly either, but keep it as either a draft or private post on my website. In some cases, I may just add the edit syndication link on an original bookmark, read, watch, or other post type, a pattern which I’ve done in the past for articles I’ve read/bookmarked in the past and simply syndicated manually to the wiki.

I’ll also need to tinker with how to save edits I make directly in the chat channels via Loqi, though I think that is straightforward as well, now that the “easy” part has been done.

I only wish I had thought to do this before I made the thousands of edits to the wiki earlier this week. Both IndieWebCamp West 2020 and the edits for part of organizing that were the inspiration for finally getting around to doing this.

This isn’t as slick as the process Angelo Gladding recently did a demo of and is doing to syndicate his edits to the wiki from his website using a POSSE syndication workflow, but I’ll guarantee my method was way less work!

Also, since my edits to the wiki are made as CC0 contributions, the POSSE/PESOS flow doesn’t make as much difference to me as it might on other social silos.

I don’t edit Wikipedia incredibly often, but perhaps I set that functionality up shortly too.

Here’s the first example (public) post: https://boffosocko.com/2020/06/30/55772818/

I’ll get around to fixing the remainder of the presentation and UI shortly, but it’s not a horrific first pass. It’s at least allowing me to own copies of the data I’m putting out on the Internet.

I just automated my creating stars on Github to syndicate that intent and data (by PESOS) back to my website as bookmarks. Here’s an example on my site.

This is done using a variation of Using IFTTT to syndicate (PESOS) content from social services to WordPress using Micropub.

As part of this I used the feed pattern https://github.com/{{username}}.atom to input a feed which I’m filtering with my username and the word “starred” to pull out the correct items to syndicate.

I couldn’t find a permalink URL for the star itself, so I’m adding a syndication link that points to the page of “stargazers” for the individual repo that I’m bookmarking. 

While GitHub calls these stars and I might have mapped them to “likes” on my website, I’ve always thought of my intent as more of a bookmark. In practice I often use my stars as bookmarks for things I want to come back to visit on their site anyway. Since it’s my website and I have the control, I get to choose.  Of course I also have the facility to create a star post kind on the site too, but the semantic difference just doesn’t warrant the work.

Now to figure out how I might extract out all of my prior data to backfill old bookmarks like this…

I’ve now got about 20 webhooks set up to pull back data out of silos like this including ones for GoodReads, GitHub, Hypothes.is, Last.fm, Spotify, Untappd, Twitter, Letterboxd, Diigo, Reading.am, Huffduffer, Google Calendar, Meetup.com, YouTube and Pocket.

IndieWeb idea for the extension of ThreadReaderApp

I’d love it if ThreadReaderApp had the ability to authenticate into my personal website and publish a copy of my own tweetstorms into my blog using Micropub. 

This would be a great way to leverage their existing infrastructure and to allow people to put their own Tweetstorms onto their blog and solve the perennial “Why didn’t you just blog about this” commentary. 

Replied to a thread by Carter Rabasa and Boris Mann (Twitter)

Another great option is Kevin Marks‘ NoterLive which lets you Tweetstorm away and cut/paste (PESOS) the stream to your website (with appropriate mark up when done). Other ideas at: https://indieweb.org/tweetstorm

Replied to a post by Brett KosinskiBrett Kosinski (The “B” Ark)
Taking back control of my content, I’m pulling my (modest) book reviews from Goodreads back to my blog. An underrated favourite of mine is Last Chance to See by the astounding Douglas Adams.

Congrats! I love the increasing number of people I’ve seen even in the last few days working on this! Are you using IndieBookClub.biz to post to your website?

I’m waiting for people to start documenting examples of owning their knitting on their websites and syndicating to/from Ravelry. #​IndieWebKnittingChallenge