I use a personalised feedreader (running on top of a self-hosted instance of FreshRSS‘s API that handles the RSS subscriptions) since about 4 years.
My feedreader allows me to interact with the Web, not just read it. I can post to this blog (and a few other websites) directly from it and keep reading my feeds. Same for adding an annotation to Hypothes.is, and for adding a note in markdown to my filesystem in the folder where Obsidian lives.
Recently I mentioned I want to make my habit of annotating web postings in my Hypothes.is easier to keep up.
As I wrote then:
… currently from within my feedreader I can post to either my blog or to Hypothes.is, but not both. I want to change that, so that the same thing can serve two purposes simultaneously.
I now have adapted my feedreader interface and related scripts to do just that.
It can post to a few websites AND to hypothes.is AND to Obsidian all at the same time now. It used to be either just one of the sites, hypothes.is or Obsidian. Posting to both hypothes.is and Obsidian simultaneously won’t happen a lot in practice as my hypothes.is annotations already end up in Obsidian anyway. I use the saving to Obsidian mostly to capture an entire posting, where I use hypothes.is in my feedreader to just initially bookmark a page so I might return later to annotate more. The current version of the response form in my feedreader is shown below.
One element I added to the interface that I haven’t coded yet in the back-end: posting to my personal and/or my business Mastodon accounts. [UPDATE I did that now too]. When Now that is done, I can write to all the places I write the web, right from where I read it, as in Tim Berners Lee’s original vision:
The idea was that anybody who used the web would have a space where they could write and so the first browser was an editor, it was a writer as well as a reader. Every person who used the web had the ability to write something. It was very easy to make a new web page and comment on what somebody else had written, which is very much what blogging is about.
I’m thinking about it the same way. Feed reading and writing belong together, the closer the better. 😉
@ton
I just got a “507 Insufficient Storage” error reading this post
Insufficient Storage
The method could not be performed on the resource because the server is unable to store the representation needed to successfully complete the request. There is insufficient free space left in your storage allocation.
Additionally, a 507 Insufficient Storage error was encountered while trying to use an ErrorDocument to handle the request.
@ton trouble went away after a moment, no worries
@w8emv Yes, linking to myself in a Toot does a DDOS as all the instances my followers are on hit the server at the same time to try and get a preview of the URL I mentioned. I already switched off previews to mitigate the load, but still. Design issues in ActivityPub/Mastodon
@ton Exactly what CList is intended to do. https://www.downes.ca/cgi-bin/page.cgi?presentation=589 Something like this is coming, but the trick is to get the design right. There was zero takeup of my version.
It’s time to redefine how we connect
Looks like a clever tool, is any part of it visible/opensource? Same thought: I’m a bit disappointed that most feed readers aren’t investing more in features for interaction (I like FreshRSS, but frankly it’s quite old school when it comes to sharing/interacting with the rest of the Internet).
Yes, it’s at https://github.com/tonzyl/responsivefeedreader (mind it’s basic, messy and intended for local on-device usage as no precautions have been taken at all to verify inputs etc.) It’s not the latest version, I will update it.
I’ve reached 2000 bookmarks and annotations in Hypothes.is. A large chunk of those 2000 bookmarks came this month, some 20% of them. Because, mostly I…
Early December I blogged about wanting to build a stronger habit of bookmarking and annotating in Hypothes.is (which sends everything on to my notes in…