JGrffn

When? I'm one video away from being blocked and I manually updated my ublock stuff like a week ago.

I haven't touched compilers in a while, but I was a dirty little MS pig boy back in college. Qt with MSVC just made sense for me, with the single exception of non standard byte lengths for longs (almost cost me a class due to not using std uints, totally my bad but you don't really expect compilers to understand basic data types differently).

The true shitfuckassface experience for me was ICC. Stupid little pig boy decided he wanted his Qt working with ICC, due to all dem optimizations for Intel CPUs. After hours of debugging nonsense errors and janking my way through Qt code which was way above my head, I finally got a Qt build, only to have ICC find thousands of completely removed errors in a project where no other compiler would find errors.

Yeah that was the day I stopped caring for C++, stopped licking intel's ass, and started getting ever so slightly radicalized due to the lies of the republic.

Still absolutely not true

Lol that's absolutely not true

Maybe it's a cultural or family thing? So it's just pre-cooked rice, you cook it as you would any rice I guess, but you add chicken stock, raisins, and butter (at the end, after you're done cooking it). Variations often also include peas and corn, maybe diced carrots, but we stick to just raisins. The savory mix of the buttery rice with tiny packets of moist raisins sprinkled about the rice makes it delicious!

Hard to follow that as a rule. Consider any YouTube video, the video id isn't exactly human readable.

Hear me out. Christmas rice with raisins. They absorb moisture from the dish and become these sweet little treats in the midst of a very buttery and savory rice. I hate raisins but I fucking love that rice.

I'm relatively new to usenet myself and have both torrent and usenet tied to my *arr automations. From what I can tell, for newer stuff they're less distinguishable than for older stuff. Things basically get uploaded in both places for the most part, so you can also get duds on usenet, the same duds you'd get on torrents.

They do! All of these backbone comply with takedown requests. Some comply with DMCA requests only, some comply with NTD requests only, and some comply with both. It's actually another thing you could consider when selecting your providers, you check their takedown policies. By mixing and matching, you increase your chances of finding every part of your file.

So, the thing saving usenet in particular, is that the pieces of the file get scattered through the usenet, and you require indexers to find the whole thing. This makes it difficult for takedown requests to actually take down the whole file. Sometimes the best they can do is remove a few parts, and you can repair your file with what's left. Sometimes they do win, but it happens infrequently enough that you should be able to complete most of your media library without issue.

You gotta pay. I posted an explanation on usenet as a reply to this post. You can find more info, such as specific providers and indexers, in the /r/usenet wiki.

OK, let me mention some important caveats, just so you can keep them in mind:

You can think of usenet like the internet. You have data on servers all around the world, you have sites such as Google which index these sites and content, and you have your ISP which gives you access to the internet.

Likewise, on usenet you have the data scrambled on servers all around the world, on different backbones of the usenet. These backbones are accessed through service providers for the backbones (sometimes they're resellers, sometimes it's the backbone selling access). These service providers operate just like an ISP, selling you monthly or yearly access to the usenet backbone of your choosing.

Then there's the Googles of usenet, Indexers. There's a ton, they vary a bit from one another, but essentially they find all there is to find on usenet, presenting the files to you as a whole. You want a specific... Ahem... Linux iso? An indexer will know where all the pieces are and it will tell you with an NZB file, kind of like how torrent files tell you where to look. Indexers can be a monthly subscription, but some of them offer lifetime subscriptions as well, and they don't break the bank.

The last bit you'll need is your download client, to do what you do for torrents. These are free tools, sabnzbd and nzbget. Either one works.

So, I did mention there's multiple backbones of usenet. Indexers don't lock themselves to specific backbones, and no indexer covers everything there is on usenet, which means that to get the most out of usenet, you'd ideally have multiple indexers and multiple providers (making sure you don't get providers from the same backbone as they'd essentially have the same data). Multiple indexers give higher chances of finding something on a search, while multiple backbones increase your chances of finding all the pieces needed to complete a file. This is not absolutely necessary, but dare I say you'll notice the difference as soon as you bump things up to 2 of each.

So, essentially, usenet is by far the best method for completing your media library (leaving torrents as a desperate backup route), but it can become expensive.

Are you for real here? Reducing the dependability on user interactions also reduces the chance for user error, and helps keep people alive in some cases. Even if that weren't the case, it's not your place to call out someone's medical treatments and compare them to your (at best) anecdotal experiences. It's not outrageous to want a CGM.