My colleagues having a chat about their favourite tv shows in the operations channel at 7am have entered the chat.

Holy shit that’s too real. I come here to get away from work!

Lossless compression algorithms aren’t magical, they can’t make everything smaller (otherwise it would be possible to have two different bits of input data that compress to the same output). So they all make some data bigger and some data smaller, the trick is that the stuff they make smaller happens to match common patterns. Given truly random data, basically every lossless compression algorithm will make the data larger.

A good encryption algorithm will output data that’s effectively indistinguishable from randomness. It’s not the only consideration, but often the more random the output looks, the better the algorithm.

Put those two facts together and it’s pretty easy to see why you should compress first then encrypt.

100% on Safari with just Wipr.

Shit no! You know what you can’t change if/when they inevitably leak your data? Your fucking hand.

It’s not subscription business models that will be affected by this, it’s ad-supported ones.

The problem is you’re running Chrome now*. Google are in the process of severely restricting the mechanism by which adblockers work in Chrome and its derived browsers - so it’s happening now. The only viable alternative left is Firefox, if Google manage to get this proposal past then there’s nothing stopping ad-supported sites from forcing you to use Chrome or another browser they know they can serve you ads with. Those types of sites are already comfortable with aggressive anti-adblock tech so no doubt they’ll be comfortable with this too.

Switch to Firefox!

* statistically speaking!

You can trademark dictionary words. You can’t trademark anything too generic, like you might struggle to trademark a drink called “drink” or something (although you might be able to trademark, eg, shoes called “drink”!), but there’s nothing stopping you trademarking words.

Adobe is an english word, too.

It depends on the movie and how they market it. Usually once it hits streaming services good rips will be available very quickly.

Personally I don’t bother with CAMs or TSs, I’d rather wait until there’s a good rip.

Use Radarr, set the quality you want, watch stuff when it shows up.

That’s an amusing name but they take a photoshop competitor to market using that name they’re going to lose a trademark dispute in milliseconds.

Problem is the effort to find a vulnerability and exploit it is often higher than the effort required to patch it. Because by its nature a browser and the server it talks to are internet connected, Google will be able to revoke keys for older exploited versions at will. As long as it’s well-engineered I think there’s a good chance they’ll be able to keep that secure.

Though I’m sure there will be some successful approaches to ad blocking etc but if something like this gains traction it could completely change the internet. If enough people are running browsers like this then sites could effectively be able to kill off competing browsers that aren’t restricted.

I think the key is to not let it happen in the first place, and boycott browsers that implement stuff like this.

The point of the proposal is to allow servers to be sure the software (ie browser) running on the device is what it says it is, and take away the ability to spoof what browser you’re running (which is currently fairly trivial).

So if someone makes a browser that doesn’t allow adblockers and always shows ads, the server can do things like only serve content to that browser.

Pi with Kodi on it is pretty good.

                                 has entered the chat.

I’m in the same kinda situation as you, I need some storage but need it to be expandable, want to run some docker stuff, while I could (and have in the past) build and maintain something like that from scratch, I don’t want it to take over my life and I want it to be easy to maintain. My previous NAS was fully set up from scratch on FreeBSD, it was pretty good but was a lot of work to get it right.

So I set up an Unraid server on a parts-bin server as a kinda compromise between a fully DIY and just buying a NAS. Meant I could use some old stuff I had and some cheap components rather than paying out hundreds for a NAS. Slapped in some shucked drives and some old NVMe drives (took the opportunity to upgrade my gaming machine, so used the old stuff for this), now got 42Tb of storage and 2Tb cache.

I have to say it’s bloody fantastic. Was a bit on the fence about a paid OS but it’s cheap, the UI is solid, and thus far totally worth the money.

Alongside about a dozen services running in containers, I’ve got an Arch VM to satiate my DIY cravings, which suits me fine because I can do what I want with that without messing up my file storage/services/etc.

Block accounts can get expensive if you’re doing a lot of traffic.

The setup I recommend is one unlimited account and a block account on a different backbone. That way you can download as much as you like and the block account gives you extra coverage.

Brave have said they’ll retain support for Manifest v2, but realistically that’s likely to be non-trivial amounts of work, and get harder as their upstream codebase moves away from it and the internals get switched over from the old webRequest mechanism.

They’ll have to patch things manually to keep it working, which is likely to get harder and harder. If Google want to make it hard for them to retain support, they can do so.

At some point they may not have the resources to keep doing that and might have to decide between forking the codebase and losing manifest v2. If they fork then they’ll have a load more work to do in backporting security changes etc.

They’ll also have to find a way to retain the old manifest v2 versions of extensions, as they’ll disappear from the Chrome store. Might mean maintaining a separate store. The authors might not care enough to maintain a Brave version of their extensions.

All in all it’s not great path forward for Brave. At best they’ll have an increased maintenance burden. At worst it gives Google the power to force them to drop Manifest v2 or be overwhelmed by maintenance. But this is what we get for handing an effective monopoly to Google.

Switch to Firefox!

It changes how extensions work in Chrome (and derived browsers), notably it modifies the API that adblockers use to block requests and dramatically restricts the number of rules they can support. It’s a change pretty clearly designed to limit the scope of adblockers and make it easier for companies like Google to work around them.

https://www.eff.org/deeplinks/2021/12/chrome-users-beware-manifest-v3-deceitful-and-threatening

Google must be fucking salivating at the prospect of manifest v3 going live and adblockers being gimped.

I wish more people would switch to Firefox.

Fuuuck’s sake that’s going to be such a ridiculous mess.

Eh, I don’t think it’s be a big deal. Slap a giant warning on it, all good. Super common on all sorts of platforms. Anyone trying to claim their encryption doesn’t work because they have a (scarily labelled) option to disable it can be easily demonstrated to be disingenuous.

And worst case if someone does disable it but doesn’t implement their own then their email I just falls back to… the same as any other platform.

They might not want to take the time to build it, but I think what this dude is asking for is a totally reasonable thing.