WeChat ID
aaronpk_tv
-
-
-
-
-
Two of my podcast editing students just launched "The Psychology of Nothing" -- where two women (who are also psychologists!) talk about the minutiae of things they overthink. Episodes are a tight 30 minutes, because my students learn well :) https://psychologyofnothing.com/
-
Jamey Sharp
https://toot.cat/@jamey
•
Jul 13
@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?
That's true, it's based around the assumption that clients display posts in a stream, rather than a model like email clients where only the subject line is displayed.
In practice you can't store just an ID, you need to store something else in order to give some indication to the user of what the thing is before they click it anyway.
In a similar vein as to what I think you're getting at, we do need to extend Microsub somehow in order to support "conversation" views. Think clicking on a tweet to see the full thread. I think that same mechanism could be used to lazily load a large post if needed too. -
Jamey Sharp
https://toot.cat/@jamey
•
Jul 13
@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?
Microsub doesn't actually say anything about feeds or how long data is stored, it's an abstraction for browsing channels of content, where the contents are not specified by Microsub.
I could definitely implement a Microsub server that doesn't actually store entries and just loads from RSS feeds on demand, tho I probably wouldn't do that exactly for performance reasons.
The main things that Microsub cares about are
• Return a list of channels for the client to display
• Return the top posts of a channel (doesn't have to necessarily be date-ordered)
• Indicate whether there are "more" items in that channel that can be loaded
Everything else is an implementation detail, including if/how old content is stored. -
Jamey Sharp
https://toot.cat/@jamey
•
Jul 13
@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?
Well that's an interesting thought... The ever-growing storage requirement was my main concern with launching Aperture, so I limited it to only storing the last 7 days of posts. If I knew I could show a "read more" link and fetch the feeds on demand that would certainly make my life easier while still letting people browse through more content than I want to cache/store permanently. -
I was just having a conversation with a few ActivityPub developers about this exact thing. It is very confusing! I'm pretty sure my site is also doing things wrong but oh well.
-
The fact that Mastodon and Pleroma already support this type of discovery makes it a good candidate for including in the spec. I think the language in the original proposal is a great start and we should continue iterating on it.
-
I think there may be some unexpected edge cases in the way that I implemented deleting items older than 7 days in Aperture, causing them to sometimes reappear. I'll have to look into that some more.
As for Monocle, luckily it's not the only client you have to choose from! Try out Indigenous for iOS and Android, or Together! I haven't implemented feed following in Monocle because I normally do that from Aperture. The other clients support it though! I also mainly treat my feeds as a stream, so I am less concerned about marking individual items read/unread, which is why that feature is not in Monocle. Aperture supports it though so again another client might give you a better experience! -
Eugen
https://mastodon.social/@Gargron
•
Jul 13
@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.
Oh, does Mastodon already look for <link> alternates now? I would love to do that instead of content negotiation on my posts. -
Reposting @aaronpk's interface they implemented for #ActivityPub mentions in #p3k (https://indieweb.org/p3k) for better visibility and inspiration. Bridging the #indieweb and #fediverse is so exciting. Lets hope this trend continues infinity!
