#Loqi[preview] [aaronpk] reviews dialback auth again
gRegor joined the channel
#[iambismark]for those folks who have built their own CMS: whats your approach to stored post content format: “markdown” or html or …? i say “markdown” because once you toss in frontmatter, shortcodes, etc, is it really markdown anymore? then if you want to microformat all the things, that involves quite a bit of custom type handling or postprocessing ASTs or some such… but the beauty of “markdown on the file system” is alluri
#LoqiIt looks like we don't have a page for "Mastodon server" yet. Would you like to create it? (Or just say "Mastodon server is ____", a sentence describing the term)
#[KevinMarks]Ben's right about the follow problem, wrong about the name problem and naive about the consistent conversation problem, as that is equally true of twitter, as conversations fork.
#barnabywell, at least on twitter there’s one “true” copy of the conversation, although their API and UX around threads and replies are so bad that different clients do end up presenting different views
#[KevinMarks]on a semi-related note, this problem is making me wonder about going in on indie readers more (though my 'follow thousands' approach on twitter/mastodon may be asking for trouble there too)
#barnabydo you end up having performance/UX problems due to the amount of people you follow?
#[KevinMarks]There isn't really a true copy of the conversation, because each reply or quote is the root of a different fork - twitter will follow in-reply-to's up to the root from a post, but won't show all the responses below if that forks, nor will it show the quote responses. In a big conversation, it's the "publics" problem.
#[KevinMarks]I do in twitter & mastodon quite often - the web app copes better than the client apps mostly, but they do chew RAM
#barnabytrue, quote tweets complicate it significantly. but at least twitter avoids the “multiple federated copies which each show a different set of replies” problem which I think is what Ben’s mostly focused on in that post
#aaronpkit doesn't really though, because you're going to see different replies than i see when we look at the same post, once a post gets big enough
#barnabyaaronpk: due to algorithm stuff? I guess twitter is sufficiently login-gated now that it’s not really possible to claim that the logged-out view avoids that
#aaronpki even clicked "mute conversation" on one thread i was in that got messy and it mostly worked but occasionally another reply would come through
#barnabyI think that article’s point is more that the problems with tracking threads on mastodon is a regression from twitter’s already-flawed thread UX
#[KevinMarks]It's more that the conversation is a graph, not a linear one, and different people in it see different subsets and respond to those subsets. Rifkind is getting criticism from lots of others as well as me and is responding with a similar shrug on each fork.
gRegor, barnaby and geoffo joined the channel
#[KevinMarks]looking at a twitter tab and a mastodon tab opened about the same time, the mastodon one is growing ram faster, the twitter one uses more when I scroll but seems to GC when I background it.