It’s been removed in most of the US.

On some phones you won’t get anything when searching for “lockdown” but you most likely have it, it’s typically under Display > Lock screen > Shown lockdown option.

If you like this you may like Chrome too, because that’s exactly how Google is trying to do things now.

Here’s the thing. I don’t want my browser to do things under the hood. It’s either protecting my privacy or it’s not. That means it’s either sending cookies to the website I’m visiting or it’s not.

When Firefox takes it upon itself to bypass cookies and collect information about me, that’s surprising and unpredictable and may fail in ways unique to Firefox. It’s one more thing to worry about.

If Mozilla wants to outright and overly protect me they can offer an “allow cookies” button like LibreWolf does, our how you can get with the CAD add-on (Cookie Auto Delete).

If they won’t do that then stick to blocking third-party cookies and get out of the way.

I don’t want Firefox to second-guess what I want to share with anybody, and assuming I want to share anything with advertisers, even anonimized data, is an abuse of my trust.

We don’t owe advertisers anything, btw. They’re a parasitic industry and the sooner it dies and we move on the better.

It will fall through much faster than that. I’m thinking two years, tops.

What bug? It’s super easy to do this in an app that already has access to your microphone, like Whatsapp, then extract only keywords from conversations and send them to Meta packed as innocuous numeric codes piggybacking on the overhead of encrypted connections.

A single byte here and there is all you need to know people were talking about cats, or perfume, or shoes etc.

Whatsapp protocol, app and servers are closed source, and Meta apps will download and compile native code upon installation, which escapes normal JVM restrictions and does God knows what.

On certain brands of phones (like Samsung) Meta apps come with a manufacturer-preinstalled system stub that can do pretty much whatever it wants, but is typically used to elevate the rights of Meta apps that were installed via normal means and to collect information from them as well as any app that’s running ads from Meta.

And this is a company that’s a third party to the Android ecosystem — it’s a lot easier for Google themselves, who are datamining the shit out of everything you do on a phone, from second-by-second location to email. And Meta is datamining the shit out of absolutely everything you put on Facebook and Instagram, in spite of any fines and sanctions. And Microsoft are datamining the shit out of everything you do on your PC and they’re openly pushing Recall and Copilot and have been pushing Cortana for so long.

What do you think Cortana and OK Google were listening for?.Hell, Amazon and Google were both caught storing recordings of people’s conversations in the beginning, before they started hiding it better.

So you’re being watched in every way possible in every single thing you do that touches any technology from these companies, we have countless documented instances of them breaking privacy in heinous ways like giving up people to authoritarian governments and to anti-abortion governments in the US and so on…

…and you’re seriously wondering if they’re snooping on your conversations? They have every means at their disposal, they’re using it every second, and you’re wondering if they’re doing that too?

Why wouldn’t they? It’s obvious that we live in a world where it’s ok to ask forgiveness (and you’ll get a slap on the wrist, if that) rather than permission. What would possibly compel them to not do it?

Consequences? What consequences? We already know for a fact they spy on so much stuff and we keep using their tech. There are no consequences.

You don’t have to install drivers or CUPS on client devices. Linux and Android support IPP out of the box. Just make sure your CUPS on the server is multicasting to the LAN.

You may need to install Avahi on the server if it’s not already (that’s what does the actual multicasting). The printer(s) should then auto magically appear in the print dialogs on apps on Linux clients and in the printer service on Android.

On Linux it may take a few seconds to appear after you turn it on and may not appear when it’s off. On Android it shows up anyways as long as the CUPS server is on.

From what I understand OP’s images aren’t the same image, just very similar.

short of all using the same wordpress or whatnot hoster, that is.

That’s the thing, that’s common practice. It’s basically a given nowadays for shared web hosting to use one IP for a few dozen websites, or for a service to leverage a load/geo-balancer with 20 IPs into a CDN serving static assets for thousands of domains.

Jesus gets crucified.

with infrastructure the size of twitter you can also blackhole their whole IP range

Just one note, services the size of Twitter typically use cloud infrastructure so if you block that indiscriminately you risk blocking a lot of unrelated stuff.

Any PC can do that, it’s called “status after power off” or something like that.

I mean, the process is not dying in either gif, so…

It stops working occasionally but they release fixed versions pretty fast.

Bayesian filters are statistical, they have nothing to do with machine learning.

You should consider if you really want to integrate your application super tightly with the HTTP protocol.

Will it always be used exclusively over a REST-ful HTTP API that you control, and it has exactly one hop to the client, or passes through hops that can be trusted to never alter the HTTP metadata significantly? In that case you can afford to make HTTP codes semantically relevant for your app.

But maybe you need to pass data through multiple different types of layers and different mechanisms (socket protocols, pub-sub, file storage etc.) In that case you want all your semantics to be independent from any form of transport.

It’s a perfectly fine way of doing things as long as it’s consistent and the spec is clear.

HTTP is a transport layer. You don’t have to use its codes for your application layer. It’s often done that way but it’s not the only way.

In the example above the transport layer is saying “OK I’ve delivered your output” which is technically correct. It’s not concerned with logical errors inside what it was transporting, just with the delivery itself.

If any client app is blindly converting body to JSON without checking (at the very least) content type and size, they deserve what they get.

If you want to make it part of your API spec to always return JSON that’s one thing, but don’t do it to make up for poorly written clients. There’s no end of ways in which clients can fail. Sticking to a clear spec is the only way to preserve your sanity.

Endeavour differs very little from Arch once you’re past the installer. To the point I’ve never understood why it’s a standalone distro instead of an optional Arch installer, as an alternative to/part of archinstall.

They buy the hardware once then sell services based on it.

Oh definitely, Manjaro is all about “mommy knows best”. It’s why people who say “you should use Arch instead of Manjaro” are completely missing the point.

Technically, Manjaro used Arch exactly as intended, leveraging its flexibility, but it’s very ironic that it used it to remove said flexibility. I’m guessing it’s why some Arch fans feel betrayed and hate Manjaro.