151–160 of 207 posts
Usenet was good for file sharing back when newzbin indexing existed. Is there anything around like that today?
Is still worth giving Usenet a try again? Are there any technology Usenet groups that are still active and worth subscribing to?
news:alt.folklore.computers is active
I enjoy the news:comp.sys.acorn hierarchy but then I was an Archimedes user.
Google has seemingly reached the pinnacle of uselessness > To find a client, do a web search for "how do I find a usenet text client" Result: https://imgur.com/a/8VrfuPu
And here is DDG https://imgur.com/gallery/i9OU844 I've had so many people tell me that DDG is inferior to Google Search, but that has not been my experience, at all.
I use DDG for ideological reasons but in my experience Google Search has always been the better engine when searching for specific queries while for general queries most search engines are roughly the same. In terms of overall performance I'd say Google takes the cake, followed by Brave and then DDG/Bing/...
Earlier quoted context omitted.
> 2) There is no administrative ostracism. Nobody gets kicked out by brownshirts for expressing their view. To be clear, you are on record as equating content moderation on private platforms with Nazism: https://en.wikipedia.org/wiki/Sturmabteilung#:~:text=The%20S... .
I see; I was not aware that there is a specific connection between Nazis and the "brownshirt" term, though it is obviously a reference to some kind of uniform.
:-o
Earlier quoted context omitted.
What doesn't work between Firebase and Bazel, out of interest? Bazel seems to be super generic?
https://github.com/firebase/firebase-ios-sdk/issues/6115 https://github.com/material-components/material-components-w... Two examples that come to mind but there are plenty
While I understand the frustration, I see package managers and Bazel as quite distinct approaches, and I'm not surprised that they are incompatible. There shouldn't be anything incompatible between Firebase itself and Bazel – I can assure you that Bazel is used to build wildly esoteric things at Google – but the Cocoapods/SPM layer is sort of fighting an uphill battle because Bazel is built on the assumption that it's building everything itself.
I work on a very large mobile app that is built with Bazel, and can attest to how worth it the experience is at scale, but I realise it takes a lot of doing to make it work, and that doesn't pay off until a certain point.
What’s the state of the art in Usenet clients these days? Last time I had a giganews account I was still using Mozilla lol
[flagged]
> Nobody gets kicked out by brownshirts for expressing their view. Who kicks out the actual brownshirts? I and most people have no interest in trolling.
(Not expressing an opinion about the content moderators that work/worked at twitter/x; just the organizational structure that led to disaster over there).
Earlier quoted context omitted.
no. it's just a tcp client/server model like any other. your isp probably won't let you host services but that's been the case for decades
> your isp probably won't let you host services but that's been the case for decades How would your ISP know? NNTP originally was originally store-and-forward over dialup like links, no? So, if I contact a different server and upload/download the changed data, how would they even know? I guess the big issue would be having some "rendezvous" server in order to help with NAT punching as well as authentication.
NNTP is to USENET what ActivityPub is Mastadon. USENET is a confederation of cooperating peers, currently using NNTP, but it could be any mechanic to move the messages. You could wire it up using SCP I imagine if you were motivated to do so.
Specifically, the NNTP protocol does not talk directly to how USENET works. For example, you can find out how to exchange messages for particular topics using NNTP, but not how to actually create those topics. That left to the actual software and administrators. USENET using the concept of "Control Messages" to exchange information about things like newsgroup status, but the content and format of those messages are not specified in NNTP.
As a USENET peer, pretty much all peers are "equal". You host your own news server, you tell it what groups you're interested in, it peers with another host and exchanges messages about those groups. At that level, they're equal.
But just because you create a newsgroup on your system, doesn't mean that group is instantly propagated across the planet. That's where the USENET governance kicks in as to who is going peer and distribute new groups, or not. Each individual relationship within the peer group can be different.
I can't say exactly how a news client differs from a news server. It may not have any of the peering logic, posting and reading groups directly from a server which then handles the peering. News servers "peer", clients are lighter weight.