3 ms·
I think "This would dial the entire Internet ecosystem back to look a lot more like the 1990s" probably understates it, to be honest. In the 1990s, heavy USENET
by rsynnott 5y ago
I think "This would dial the entire Internet ecosystem back to look a lot more like the 1990s" probably understates it, to be honest. In the 1990s, heavy USENET users, say, would generally use tools which highlighted posts from users they were interested in, downranked or hid posts from users they were specifically _not_ interested in, and similar. This made USENET usable (for a while).
NNTP clients generally worked by just downloading the whole group, so this could be done client side. With the scale of modern internet services, however, you're not going to be downloading the whole day's twitter content and doing client-side filtering, so you'd need to provide your filtering list to the provider. At that point, you have a friends list, and on a naive reading this might be a problem.
- LinuxBender 5y agoI would just download headers and only pull the body for content I am interested in. Usenet doesn't have the same hierarchy as Twitter. One would not have to download all of twitter, just the sub-groups they are subscribed to. One could also filter what groups they want to pull down. alt.something.twitter.text-only.emotional-support-animals.fluffy-bunnies alt.something.twitter.text-only.checkmarked.public-figures alt.something.twitter.bin.sfw.memes The audience could optionally use some add-on in the news clients to validate things like twitter identities, validate checkmarks, etc... Another add-on to filter out what Twitter considers spam if you were so inclined, or maybe subscribe to a crowd-sourced spam filter. These addons could pull signed data from each respective usenet group. One could probably go as far as to make a Twitter Client that uses Usenet behind the scenes and communicates through a HTTPS gateway for VIP to avoid people needing firewall rules for NNTPS in corporate environments.