It doesn't prevent much in this particular case though. I closed my Facebook account some 12-13 years ago and I recently contacted them and asked to see what data they had on me (under the GDPR, because of shadow profiles). They absolutely refused to neither confirm or deny that they were building shadow profiles but kept repeating that if I didn't have an account, they didn't hold any data on me and then followed up by answering that if someone let Facebook rummage through their contacts and I was among them, then they'd of course hold that data until that someone decided to delete it... So, yeah...
Remember the dude whose garage port opened and closed seemingly at random because his /toggle endpoint ended up in his browser's "most visited" list: https://news.ycombinator.com/item?id=16964907 ?
I have a feeling the same thing could happen here.
That's why you have to use a POST request. GET should be read-only and a browser will not re-issue a POST for things like most-visited, tab restore, pre-fetch, etc.
Yeah, that's what the guy in the linked post is talking about. Various services (Skype/Teams, Slack, Twitter, etc.) will also send a GET if the URL is shared there. I once saw an accidental hotel booking triggered by Skype because the booking was performed through a GET request with a brazillion parameters.
Lots of people here mentioning that concert pitch wasn't always A = 440 Hz. Here's an interesting 12tone video explaining how we ended up at exactly that: https://youtu.be/BzznBt8tVnI (Spoiler: It involves nothing less than the Treaty of Versailles.)
Aw, man! I'd forgotten this existed. My gf and I used to do the "mah mah mah mah", "oh toh toh toh"-thing when pouring drinks for each other. Thanks for posting it and reminding me.
The person who the drink is being poured for is saying that it's too much and it's about to spill. The person pouring the drink wants to continue pouring out of generosity. "o-to-to" (sort of like "oops") and "maa maa" ("no no" / "doesn't matter") are normal things for the respective parties to say in this situation. It just won't go on for that long, or be done every time with those exact words like a ritual, which is the joke.
If you're sitting 5 meters from your speakers, you add about 15 ms of latency and, in some cases, people all the way across the globe will hear your sound before you hear it yourself.
It's pretty wild to think about. My dad used to point out to me that, if I was watching a live concert on the TV, the sound would reach me before it reached much of the live audience.
I found that most of the latency in networked audio applications, when jamming within 800 km within domestic internet, mostly comes from (a) a large network buffer (to prevent sound stutter when the network isn’t reliable, e.g. due to wi-fi interference) and (b) extra audio processing on top (echo cancellation, noise suppression), and not the limitation of light speed.
> in some cases, people all the way across the globe will hear your sound before you hear it yourself.
You're vastly exaggerating. FTL communication is not here yet.
The theoretical limit for half the planet is ~67ms, in practice it's north of 100ms for Jamulus (plus the additional delay of a user's sound reproduction system).
That's not necessarily true[0]. It's a widely repeated claim but there doesn't seem to be much actual evidence supporting it. Rather it seems that letter size and spacing are the main factor when trying to make text more readable to dyslectics.
Depending on your preferences you might enjoy Vivaldi, Qutebrowser or Chromium. That's just off the top of my head. There are obviously many other good browsers out there.
I've tried Vivaldi and it's great. My understanding is that it shares the same components as Chrome. Are there other 'fully independent' browsers? Does that even matter?
Vivaldi's built on top of Chromium, but they've written an inhouse UI layer, built-in ad blocker and tracking protection and run their own sync services. (Some other Chromium derivatives do, too: Brave and Edge being the most prominent ones)
Brave and Vivaldi default to privacy friendly search engines, try their damndest not to track you, have built-in adblockers and run their own sync services. Easily the best options for Chromium-based browsers.
Edge is also excellent if you don't care about privacy, but their sync service doesn't even include end to end encryption for all classes of synced data.
By search engine deals with not-Google companies (privacy friendly engines, Bing, etc.) and from their founder. I don't remember how many users they needed to be at break even, but they're not there as far as I know.
If we are talking at least somewhat independent (not a rebasing fork) and somewhat maintained (at least getting security updates) I think it is as follows:
The only modern browser engines are webkit, chromium and gecko. The next step down would be EdgeHTML (no longer shipped by default in any major browser, but maintained for security patches) and Sciter (only geared towards building application UIs, not general browsing. Not free as in both beer and speech). The next step after that is Trident (the old IE engine, somewhat maintained for security patches). The next step after that is probably things like netsurf, lynx and other browsers that do not and do not aim to support normal browsing.
I am not entirely sure what a rebasing fork is, but it sounds like there are only three practical choices, from Apple, Google, and Mozilla. I haven't used Netsurf and the rest but it looks very interesting. My main worry is that some limitation may cause certain websites to break in unknown ways - that could be a huge problem when doing things like logging into a bank account.
To browse the modern web you have those three choices, yes. You could probably still get by on the EdgeHTML based Edge, but support will wind down over the coming years.
If you manage to even load your banks website in netsurf that's impressive. For me it crashes even loading wikipedia, and it does not support JS at all, so basically all interactivity on the web besides forms and links is not supported. I don't think anyone, even netsurfs developers recommend even trying to use netsurf as your main browser for things like banking.
A "rebasing fork" is something like waterfox and similar projects that essentially have modifications to one of the big three engines and periodically pull in all the changes the source engine did. A lot of the chromium based browsers do this to be able to include modifications to chromium in places where it is not officially supported.
A non-rebasing fork would for example be when google forked webkit (to create blink which is a core component of chromium), which took a much more divergent path.
I forgot to mention two other engines that might be interesting to read about: kHTML (the original source for webkit so it is chromiums grandfather in a sense. Not developed since 2016) and Goanna (a fork of firefox from before firefox quantum. It is developed but last I heard they couldn't keep up with new standards and security. Development seems a bit chaotic).
