The spirit of Christmas future.
The spirit of Christmas future.
That’s like asking if I can resist reading a book. Sure I could, but I want to read a book - why would I resist?
They actually did:
The Voyager team sent commands over the weekend for the spacecraft to restart the flight data system, but no usable data has come back yet, according to NASA.
Unfortunately, that didn’t help. So now they’ll have to find out what’s causing this, and then see if they can fix it.
Same for translations btw, Firefox didn’t have built-in translations for a while because Mozilla had to painstakingly work on a research project to figure out how to do translation locally, on your machine, without sharing the page you’re looking at with an external server.
Spell-check doesn’t send things to a server in Firefox - that’s Chrome (and only with a particular setting, IIRC).
I’ll emphasise that the “handful of concessions” are concessions to usability, not to having to share data with Google or DuckDuckGo. Firefox is still an incredibly private browser, especially if you consider the rest of the landscape.
It’s not dangerous at all, superheating is rarely a thing and you can avoid it in a multitude of ways including slapping a spoon in your cup
Ah, so I should just put my metal teaspoon in my cup and I’ll be fine?
(Don’t put metal in the microwave.)
It’s not dangerous at all, superheating is rarely a thing and you can avoid it in a multitude of ways including slapping a spoon in your cup
Ah, so I should just put my metal teaspoon in my cup and I’ll be fine?
(Don’t put metal in the microwave.)
Ah yes, RDM is a clever workaround for that - I should remember that.
You don’t even need to open Responsive Design Mode - when you select Take Screenshot, there are two buttons “Save visible” and “Save full page” in the top right-hand corner.
Legit one of the most underrated Firefox features that I use all the time: right-click -> Take Screenshot (or Ctrl+Shift+S). No need to look up the relevant node, just hover the relevant part with your cursor.
I have no idea, unfortunately :/
I wouldn’t call it a mistake, more like being caught between a rock and a hard place, where Android basically forced them to give up on SMS support even though they’d have liked to keep it: https://community.signalusers.org/t/signal-blog-removing-sms-support-from-signal-android-very-soon/47954/57
But yes, it was really nice when I could use it as my SMS app. Then again, very few people in my country use SMS in the first place - it’s all WhatsApp, and it was never able to have support for that. Luckily, most of my friends have adopted Signal by now.
Btw, the main thing to realise, is that Signal is trying to tread the delicate balance of being accessible and private. If you have the perfect private messenger but nobody uses it, that doesn’t help democracy one bit. So starting out with an easier-to-implement mechanism that also helps adoption (because people can get notified when people they already have in their contact list join), that still protects against indiscriminate mass surveillance, makes sense to me, even if it means your contacts can still know who you are.
They’ve repeatedly stated that they’re working on removing the need to share your phone number with your contacts, but that’s taking some time, because they want to implement it in a way that does not involve storing your entire social graph on their servers.
You’ll still have to sign up with your phone number, but the only thing that can be traced back is that your phone number is registered on Signal - and only by subpoenaing Signal, I believe.
It’s linked to your account. If you view YouTube without logging in, you should have no issues. You can use the Multi-Account Containers extension to log in selectively per tab, if you need to.
Y’all, there’s a full video, this single image doesn’t do it justice: https://birdbutt.com/@barnibu/110995778137311940
What does “blocked on the search engine” mean?
Hehe, I can be more explicit: why would Chromium “resist” MV3 when the Chromium developers are the ones pushing it?