1. Do some clustering on my `following` collection.
2. Make lists for each cluster. I can then label them manually ("High school", "Breather").
3. Make a list for "used to follow" just in case.
3. Unfollow any account that doesn't follow me back.
I wanted Micro.blog to be so strictly reverse-chronological and anti-algorithmic timeline, that I waited a long time to make this change: just flipped conversations to be oldest at top. The clicked post on the web is also lightly highlighted.
@aaronpk You could probably use the `/api/states` endpoint (https://developers.home-assistant.io/docs/en/external_api_rest.html#get-api-states) and filter the result with the `entity_id` starting with `zone.`
@aaronpk But if the Microsub server includes some post in a timeline response, it has to include the full body of that post, right? Even if the client doesn't need the body yet?
@aaronpk Do you have any statistics on storage costs for GUIDs vs post titles vs publication dates vs post contents?
I'm thinking there are multiple sensible levels of cache flushing. It seems nice to keep just enough information to browse the list of posts, while discarding the contents of a post until someone actually opens it. But if nobody scrolls back in the history for a feed for a while, it's probably okay to discard the old post metadata too.
Microsub couldn't do that as-is, can it?
@aaronpk Hey, on another note: after conversation with NewsBlur's developer, I'm thinking about RFC5005 as a way for feed consumers to reduce storage costs, and I wondered if this makes sense to you. If you know you can re-fetch any feed entry from the origin server at any time because it has paginated archives, then you can aggressively discard your cached copy of anything whenever you want... right?
@aaronpk id property has to be either content-negotiable or always json. url property can be html. you may use <link> tags in html to point to json resources, also.
@wakest
I have seen @aaronpk getting couple of times mentioned, but have never seen a reply back. So I'm not shure if messages are comming in. @xuv
@aaronpk hey its working! so how are you getting notified? you wrote an interface for it?
how did you get #ActivityPub working in #p3k? and is that part released yet? I didn't see it mentioned here https://indieweb.org/p3k
I started by reading @Gargron's tutorials and then kept going from there, a lot of trial and error, and I had to make Mastodon accounts on like 3 different servers because it caches things too much so I couldn't test it well. I'm probably not going to make this code public though.