I would argue they are a great distraction but ultimately it falls apart when individuals come to realize that you really only have so much time to spend on stuff that doesn’t really provide much value to your life or other people you care about. The real problem is how addicting they are

I suppose its a perspective of priorities. I would much rather grind out a promotion or a financial plan rather than play video games because it provides greater overall value, and more importantly for consistency, a greater sense of satisfaction in the progress and put-togethered-ness of my life. But more paramount is the issue that with the friction-less society that we have built around consumerism it makes it really hard to even think about what we actually want and properly take the time to consider the cost-benefit analysis of our decisions.

Now with AI, I fear the offloading of cognitive function and friction will worsen this further in the short term (20ish years)

Hah! 😂

People who use their blinkers only half the time should be penalized more than those who don’t at all.

Where does that put you in terms of your relationship with USENET?

The ISP competitions ah yes.

I also want to say (as in other comments I have posted) there are some communities exclusive to just discussion but they are rather slow and small.

I would love to hear your opinion on the gemini protocol

Holy hell, $35 is still crazy!

I fail to find much a difference between our conclusions in your post. I would imagine I probably came at it from the incorrect angle to think it was a contrary idea to mine, so instead I’ll further the thought about still potentially receiving the author’s message.

Something I didn’t realize until now is that when you publish a pay walled book, in most countries there is a form of copyright, a system that is very akin to the solution that you and I have concluded on. Its something that allows for the progress of general humanity while also providing profit for the author. The real question is this.

How long should a creative or descriptive paywalled work be allowed to be paywalled before it placed into the public domain? In my opinion I think something like 75 years is far too long. Even 20 Years may be too long since now society progresses so fast.

@[email protected] (and others) What is your opinion on that time?

The relative anonymity that I refer to is the lack of validation of posting profiles. This isn’t on a level of layer 1, 2 or 3 but on how providers don’t need any information linked to an ID or at times even emails (for those servers that don’t require authentication for posting) You could define any email, name and user agent in the header fields as a posting profile and it would just accept it.

However, this particular aspect that in my eyes, as a whole, was a good thing regarding the system it did provide a strong foundation for the systemic spam problem that was seen across the board in all newsgroups. Accountability could not be maintained and the only thing to stop bad posts from getting through was quickly overwhelmed moderators.

So no, this isn’t the same level of anonymity that we would expect from modern solutions but there also wasn’t the same guardrails and requirements of identity that has been imposed upon the public like with modern accounts requiring email addresses and phone numbers.

There was a time where accounts didn’t require an email. Side note, this is precisely why I like XMPP as a concept. Though I have found little use for it due to the network effect.

No I do not, The only reason to really pay for it is to be able to download warez or use specialized newsreaders that integrate with indexers and the like. Just not my speed.

You would use it for the same reasons that you use lemmy. Just back in the late 80s until the early 00s; and with a lot more spam…

No options other than web based applications (which pretty much none exist beyond paywalls)

This is just overkill 😆!

Thanks for paying attention 😜

sadly, yes

I kinda wish the binary newsgroups stayed exclusively in the paid ones, but alas that wasn’t how it played out

I never used it but I heard it was rather similar to USENET

Its honestly about connecting with the conversation, reading everyone’s replies and seeing if it is something you would want to comment on and think you could bring something to the table in doing so. Or you could just join in the memery

Just like these forums you see now.

However, I do think the format substantially encouraged a higher level of engagement since you’re comments and thoughts weren’t squished in between everyone elses’. If someone wanted to read your thoughts on the thread it was exclusively your’s that they would look at. Like I said in other comments, its a more intimate experience compared to normal comment sections.

Thats what I love to hear!

the lack of JS is one of my fave features about it. I don’t have to really worry about running remotely provided code when I just want to read a discussion.

Also, I do agree. Usually the conversations are rather insightful, though thats probably just the people

Wide range of powerful, mature clients with extensive filtering functionality, offline reading support.

Sadly this isn’t really the case anymore. All the to previously used clients (other than command line) for most major platforms have been dead for over a decade now due to the drop in usage of USENET during the 2000s. With that as well there never were any actual mobile clients that were developed (as a side note).

Better client-side accessibility. I mean, you can be blind and use a screenreader or something on Usenet. Going to be a lot less ideal on the Threadiverse.

I think this has a lot to deal with just the tech stack required to run the modern Threadiverse. I honestly liked the simple and low-level aspects of USENET vs HTTP based alternatives. USENET was defined by objectively shorter standards than what current HTTP and Web technologies define. It also meant a larger selection of clients (and the possibility to create your own) due to the greater simplicity of standards required for it to function.

Since it was also was built as function over form vs the Web’s reciprocal approach it makes implementations like screen readers much more difficult unless the developers specifically include that into their Threadiverse software

Comment editors are probably better than the in-browser textarea editors or clients with limited text-editors that I’ve seen (though the Threadiverse has Markdown as a standard, which I think is generally preferable).

Markdown is nice I just find it hard to read sometimes due to it kinda being like a web page within a web page. Or better put it’s more like if you took a physical scroll of simple comments (no headers, no nothing, just text) and then pasted (physically) a fully formatted document as if it were just another comment ignoring any kind of page start or end. It just feels odd to look at. I hope that all made sense.

Though I haven’t been browsing Usenet in some time, and maybe they have MIME-encoded Markdown or HTML or something as a common thing now.

There is the option to include HTML in messages but I think that is generally considered bad form just due to the nature of embedding images into articles rather than having them as some kind of message attachment is not really in the spirit of the minimal nature of USENET.

More-standardized support for posting embedded binaries.

Maybe uuencode and base32/64 as yEnc wasn’t really a proper standard and more so defacto which lead to some clients that decided to not implement it at all (MS, Mozilla; along with other mail client news readers)

Commercial service is available. It’s great that people donate their time and funds to make Threadiverse servers run, but there’s something to be said for the resources available from commercial service. There’s nothing stopping someone from running a commercial Threadiverse instance, but AFAIK, nobody presently is doing so.

The only real reason why the commercial service because a real big thing for USENET and pretty much the exclusive way to access it was because of the large amount of binary newsgroups, which in my opinion really destroyed USENET since it cause mass desertion of the system, including the horrible amount of spam.

As for a threadiverse instance it probably is best that it remain non-commercialized, or if it were to become so it wouldn’t have as much an impact because the risk of storing gigantic binaries with little moderation is minimized.

Newsgroups are more discoverable than are communities on the Threadiverse — you really need to use the https://lemmyverse.net/ index to find any communities out there, as otherwise you’ll only see it once the exact name “!community@instancename” has been searched for on your local instance. Usenet (mostly) propagated newsgroups everywhere.

This is one of my biggest gripes I have with lemmy and the rest of the threadiverse. For me to discover new communities to subscribe to on a separate federated instance I have to navigate directly to said instance via the url bar of my browser and search them manually rather than be able to search for them from my instance. If they had some kind of community distribution function then it would be much simpler to find niche communities.

If this point isn’t addressed eventually it might end up actually inadvertently contributing to the centralization of communities where everyone peers to lemmy.world for example just to get all the communities rather than seeing existing communities on other instances.

Probably a larger userbase, though I haven’t dug up current numbers. Certainly a different group and set of interests.

Its mostly graybeards and a lot of binary uploads. There are still quite a few active newsgroups though, you just have to look through the endless onslaught of past uploads in supposedly ‘text only’ newsgroups that have been overrun by binaries.

Really the only good provider that you can use to get the classic experience is eternal September (which is free btw)

I would bet that Usenet servers can scale up to more load than can Threadiverse servers.

This could be argued by saying that there wouldn’t be a need to use web tech to service all the requests sure, but I honestly don’t think that the scalability would be much different. Though, I am not in a position to provide actually insightful commentary on this specific subject.