Tag: IndieWeb

All my postings talking about, or relating to IndieWeb

In reply to Een rsvp op Seblog by Sebastiaan Andeweg

Have fun, it’s been a while since I visited (or rather organised) an IndieWebCamp. Dropped of the radar somewhat. Mostly as I was playing around with the local stuff that interacts with my website but isn’t my website, and with ActivityPub. Less IndieWeb in other words than indie personal tools. Didn’t feel those tangents fit the IndieWebCamp community or efforts.

Maybe we should organise an IndieWebCamp in NL at some point again?

I will be going to IWC Nuremburg this weekend.

Sebastiaan Andeweg

(also posted to Indienews)

Bookmarked Twitter Has Stopped Working in NetNewsWire (by NetNewsWire)

By the end of the month the free tier of the Twitter API will disappear. Some apps using the API will stop doing so because of too high costs to continue, such as Brid.gy. Others are being kicked out by Twitter itself even before the deadline at the end of April, such as Netnewswire. These steps have one thing in common: they disable the ability of reading Twitter without using Twitter directly. Tightening the walls of the silo, in short. The Web is much better off with at least semi-permeable boundaries between services, so that one can interact and read from their own preferred perch. That of course clashes with various business models, although at this point I’m not sure Twitter knows what its businessmodel is supposed to be.

Twitter suspended NetNewsWire today. …. Twitter has stopped working a little sooner than expected. We’ll have updates to NetNewsWire soon that stop trying to connect to Twitter

Bookmarked So long, Twitter API, and thanks for all the fish (by Ryan Barrett)

The Twitter API is moving to paid tiers for anything but the tiniest use cases by the end of the month. I’ve been using Brid.gy to get back webmention notifications about interactions on Twitter with my blogposts here. Brid.gy depends on the Twitter API obviously, and the scale of their needs puts them above the free and affordable tier, even if well below the more expensive tier above it. Therefore Brid.gy will stop supporting Twitter. Silo’s gonna silo I suppose.
It does help remove an action from my backlog: changing the way I show such backfeed on my blog without going counter to Twitter users’ common expectations of where their interaction and avatar might end up.
Unless Musk changes his mind once again, or can’t find an employee capable of implementing the changes.

…assuming it sticks, Bridgy Twitter will stop working on April 29, if not before.

Ryan Barrett

Posted on
by

For some time I have been able to directly post things to this blog from my feed reader. My feed reading client is connected to a simple feed server, the Yarns WordPress plugin. Now I have connected my feed reading client to the API of the FreshRSS instance I use for feedreading daily.

The Yarns feeds server works, but it requires a WordPress install to run in and is somewhat limited. I could run it in this here WordPress, but then the many feeds I follow would pollute my blogs database. So until now I ran it in a separate WordPress install. All a bit hacky, and more proof of concept than really a smooth fit for my daily routines.

I do however daily use FreshRSS, which I run as a self-hosted instance on a VPS. FreshRSS has an API, or rather it has two API’s, meaning that I could run my feed reading client on top of FreshRSS by talking to its API.

FreshRSS has two APIs, one is the Fever API, the other is the Google Reader API of old. Both aren’t very well documentend w.r.t. their implementation in FreshRSS, because they assume you’d use it for a mobile client using a local database. I don’t want to replicate the database, I want to only directly talk to the API to fetch the things I need. After some experimentation in Postman I could talk to the Fever API, but haven’t worked out how to talk to the Google Reader API of FreshRSS.
The Fever API doesn’t support calling items by feeds and feeds by groups, the way I actually read in my ‘reading by social distance set-up‘. It can give me groups, feeds and items, but not cross-referenced. In terms of content it can basically only give me a bunch of feed items, at most limited by the item number of the oldest unread item. But it works. The previous post was created directly from my feed reading client, while fetching the item itself from FreshRSS.

Now, I need to figure out how to use the other API, so I can do more of the things that I want from my ideal RSS reader.

In reply to highlight.js, an extension to highlight text on web pages by James G.

Nice project, James! I’m not sure I get the distinction you make between this and an annotation extension, as highlighting is annotation too and the pop up box even calls the highlights annotations. One question: do you apply the W3C Web Annotation Data Model recommendation? That would make highlighting with this potentially interoperable with e.g. Hypothes.is. Or allow interaction with the Hypothes.is API further down the line.

I don’t presently have plans to expand this into an annotation extension, as I believe that purpose is served by Hypothesis. For now, I see this extension as a useful way for me to save highlights, share specific pieces of information on my website, and enable other people to do the same.

James G.

In reply to How can my posts integrate better with ActivityPub? by Chris Aldrich

I’m trying to add AP to my site here to be able to provide streams to approved followers of otherwise unlisted content in my site. E.g. travel plans like Dopplr did, or Swarm style check-ins (normally posted to WP with micropub, e.g. here). Both those activities exist in ActivityStreams and thus in AP. That would be possible to follow with various existing AP clients. If more people do it, it might be useful to create a client surface to combine the various travel plan streams of others I follow and show crossing paths etc.