I'm testing with the new bucketed fetching of feeds. The algorithm is similar to algorithm Aperture uses. The difference is that the buckets are powers of 2 at the moment. Every tier is the exponent of 2 minutes, after the last fetch.
In the middle of a rewrite of the backend of Ekster. The next version will have a full Postgres-based backend.
I'm trying to add the "_source" field to items in Ekster. At the moment it adds the information from the FeedHeader when it is available.
What would I need to send the webmention notifications to Ekster? It seems that I need to post the webmentions as Micropub posts to a channel.
→ www.zylstra.org/blog/2021/02/revisiting-my-ideal-feed-reader
List of use cases for a feed reader.
Ekster happily created new channels with the same as existing channels. Now the channel name is unique and returns the current uid and name of that channel. It seems this currently isn't specified.
It does improve the scriptability of Ek. I can now follow feeds while creating the channel like this:
ek follow ek channels Blogs https://example.com/blog/
→ thoughtbot.com/blog/writing-a-server-sent-events-server-in-g…
Nice implementation for SSE in Go.
I created a new release of Ek(ster) which checks status codes in the HTTP responses of the microsub server. See version 0.8.3 on Github.
And as always please use the -verbose option to show the actual requests and responses. An example:
ek -verbose channels
This way you get the actual headers and body of the requests, which could help with debugging.
Ekster now contains a new feature. The backend now supports two types of Redis based timeline backends. The default is still the timeline based on sorted sets. The new type is based on streams. The notification channel will now use this new stream type. Not many entries are posted to this channel, but I will use it for more things in the future.
It's still amazing to me that these posts show up directly in my reader, seconds after I post them.