inbtwn

here comes the no notes ghost 👻

  • he/they

hi there. i'm inbtwn. nice to meet ya!

i sometimes post about Things, mostly niche internet things like youtube videos, webcomics, etc. but i also reblog (rebug) a LOT of cool things so uhhh be warned


You must log in to comment.

in reply to @atomicthumbs's post:

i totally get that, on twitter a while back i started using the latest tweets feed and found after a few months of it i had been completely missing stuff from some of my favorite people on there due to the sheer quantity of stuff and the fact that the periods of them posting on twitter and me looking at twitter were too far out of phase for various reasons. which perhaps indicates i need to curate my follow list more, but that sucks.

my only concern is figuring out how you actually make a good While You Were Away panel. how do you make a thing that even has any hope of knowing what's important for you to see without introducing a bunch of analytics and models that are kinda antithetical to what cohost is doing. idk! it might be possible, but i certainly don't know how.

Since Twitter got big I've wanted an algorithmic feed where I can say give me at most N tweets, prioritized as follows, and ordered by (date/reverse date/user+date/...):

  1. a. Nothing from my blocked or muted list. b. Only one instance of any tweet, preferably the original and not a retweet.
  2. Everything by [my husband, ...] no exceptions.
  3. No tweets containing [list of muted regexps]
  4. Everything by people who have only tweeted a couple times in the past month.
  5. From now on, only top-of-thread tweets.
  6. Everything by [friend 1, friend 2, ...]
  7. From now on, only include retweets / quote-tweets if you still haven't got N tweets.
  8. Everything from [hilarious influencer 1, acquaintance 2, ...]
  9. From now on, only tweets with a lot of likes/replies.
  10. ... and so on.

I think a schema like this is generalizable to any content feed that is in principle infinite, though obviously the control directives based on metadata will be different per feed. And frankly, I'd like a solution that lets me centralize all my feeds, at least with respect to filtering, blocking, and muting. (But "an easy-to-set-up proxy server" is basically a non-starter because it's a contradiction in terms...)