Yeh, it’s an http site. So any browsers that require https will block/warn.

But also, holy hell is it obvious once you realise.
Arms up, then swipe down out to the sides, and repeat. Like frantically trying to fly.
As SOON as they are in trouble, it’s arms flailing in that pattern. Like, look for white splashing water and assess if it’s playing or panic.

A few you can tell who it is gonna be because they flip off their donut. And a few you can tell cause they are trying to swim but are looking up and aren’t keeping their mouth above the water (I clicked on one of these to be told “it’s fine” only for them to start thrashing and get rescued when I resumed the video)

I’ll add that it works on a system of delegation.
So there are authoritative servers (which own a part of a domain) which can then have actual records or delegate to other authoritative servers.

So the authoritative server for “com” (yes, as in .com, com is technically a valid domain name) will delegate google.com to a DNS server (likely one owned by Google). And then Google will have DNS records for mail.google.com and so on.

So looking up mail.google.com, technically you ask com DNS for the mail.google.com. It won’t have an actual record, but will essentially say “go talk to this DNS server to get google.com records”. So your computer asks this new DNS server for mail.google.com and it might have an answer, or it might have delegated the mail.google.com somewhere else.

What your computer most likely is using, however, is a recursive DNS service. You ask it for mail.google.com and it will “walk the tree” to finally return the IP address.
And then it will cache the results (for com google.com and mail.google.com) so the next queries are significantly faster.

Client -> Reverse Proxy -> Upstream Server

It’s quite rare these days for a client (eg web browser, video game, phone app… anything that needs an internet connection, really) to directly connect to the server that is actually serving the request.

It often goes through a reverse proxy which can direct the request to the “best” server (reverse proxies can have multiple upstream servers, either as a cluster that can share the load all dealing with the same service, as a bunch of different services, or both).

This has a lot of benefits for service admins (at the cost of mild complexity), and has near-zero cost for clients.

As a non-american, the speed with which trump has dismantled international relations and the lethargic (even non-existant) reaction of the “checks and balances” that should prevent such things says to me:
If America has done it once, America can do it again.
It can spend 30-50 years building strong relationships, or it can devastated them in 1-2 years.
Seems better to work without America, and let America do it’s own thing.
If America wants to join in, fine. But it’s gonna be on the world’s terms, not Americas.

That’s not a big financial incentive.
Microsoft will remove stuff when it actually gets in the way.
If it’s easier to leave in and not have to touch dozens of other programs/services then they will.
They might mark it as depreciating, and start planning a suitable replacement. They might just mark it as depreciating and kick the can down the road.
When enough services that relied on that depreciating thing have been touched due to other updates, then they might look at actioning the depreciation.

But if it doesn’t actively break the thing they are currently working on, the cost overhead or ripping it out is insane.
There might be other dev teams working on features that now rely/leverage the thing marked as depreciating. But the thing getting marked as depreciating happened towards the end of the other teams new feature development cycle. At which point actually depreciating the thing might invalidate that other teams entire project.
And maybe the rip it out, and it turns out one of their large clients (or a large amount of the user base) was relying on it.

Addressing technical debt is always hard to justify, but it always makes a better project.
If management doesn’t care about a better project, they will prioritise features and things that make money

Mumble is fantastic.
I designed and implemented a very complex voice system for an old guild. Like 100 people, 8 groups of 15, group leader’s private chat, priority speech all that. It worked so well, and never failed.
This was many many years ago, to be fair.
I wish it’s positional audio was more supported.

Never used librewolf.
But it sounds like the conveniences you want are a compromise for fingerprinting.

Don’t let perfect stand in the way of good.
The internet has been significantly ruined by large companies.
There is a loop where companies with the resources to create and maintain frameworks/tooling/whatever are large enough to help define “features” for browsers.
Browsers don’t make money, not really. To even be considered, they have to be able to run what the big companies are pushing.
All of this makes it very easy for smaller companies to deliver better websites. Or abuse the features big companies are pushing.

It’s like: email was awesome, then spam emails happened. Websites were accessible, then SPAs happened. Search engines were useful, the scraping/AI happened.

I don’t know what I am trying to say.
Other than browsers do not get the support they deserve to actually be decent unless they are backed by a company that wants to loss-lead them… Which has resulted in the web being pretty fucked

However, the international response to Trump’s call for the dispatch of warships has so far proved vague and reluctant, with countries unwilling to commit to a military response that could prove treacherous for their navies.

This is the correct response.

Mumble was awesome. It probably still is, to be fair

Wireshark*

I love cli and config files, so I can write some scripts to automate it all.
It documents itself.
Whenever I have to do GUI stuff I always forget a step or do things out of order or something.

Yeh, the 16/32 in the screenshot and that 2 sticks are dead suggests they have 4x 8gb sticks, and lends credence that one channel is being messed with.
They said they tested the ram on multiple systems, but they might have just thrown both “dead” sticks in there at the same time - leading to a similar failure mode as they are both on the same channel.

I bet 1 stick is dead, and they could probably get away with 24gb of ram in a 3/2 channel distribution

Maybe 1 is causing the other to fail?
Could try the sticks individually.

It is strange that 2 sticks fail at the same time. It smells like a symptom instead of the root issue.

While true, quantity of poop particles also matters.
Your body can fight off loads of bacteria. But once it gets to an infection point, it can’t keep up and you become ill.

So yeh, poop is everywhere. As long as it’s small amounts, it’s fine.

Pretty much any mikrotik is a fantastic piece of kit to have.
It is so unbelievably versatile.
I love the various mikrotik routers, switches and APs I have. I use them all the time for little ad-hoc networks and projects and stuff.
You will learn a lot about networking when using them.

But Unifi is a hell of a lot easier to use, and I have not found anything I can’t do on unifi (but I don’t do bgp, mlag, etc at home).

Oh, and on the “fail often” thing…
Get a basic/old/free pc/laptop and install Proxmox on it.
Loads of tutorials out there, but the basic installer will get you to a “I’m learning” stage.

Create a VM, install Debian, play around.
Then: create a new VM, install Debian, create a snapshot, play around until it does what you want, restore the snapshot, do the steps that got you from vanilla to what you want. Create snapshots along the way as checkpoints. Snapshot, tinker, restore snapshot, advance.

Proxmox is amazing for learning VMs and server things

Raspberry pis are an easy intro to actually using computers (instead of using something like windows).
Raspbian is great (based on Debian) and there is a HUGE community for it.

So yeh, it’s a great started for $25, as long as you have a PSU and SD Card. And an hdmi cable + monitor + keyboard at your disposal (and a mouse if you are installing a desktop environment (IE something like windows, whereas headless is a full screen CLI).
And don’t get your hopes up for a windows replacement.

But… Why not run a Virtual Machine? If you have a windows machine, run VirtualBox, create a VM and install Debian on it?
That’s free. You can tinker and play.
And the only thing you are missing from an actual raspberry pi is that it isn’t a standalone device (IE your desktop has to be on for it to be running), and it doesn’t have GPIO (ie hardware pins. And if this is your goal, there are other ways).

If you really really want a computer that is on all the time running Linux (Debian, a derivative (like raspbian) or some other distro) - aka a server - then there are plenty of other options where the only drawback is lack of GPIO (which, in my experience, is rarely a drawback).
And that is literally any computer you can get your hands on. Because the raspberry pi trades A LOT for its form factor, the ethernet speed is limited, the bus speed is limited (impacting USB and ethernet (and ram?)), the SD card is slower and will fail faster than any HDD/SSD. The benefit is the GPIO, the very low power draw, and the form factor - rarely actually a benefit.

I’d say, play around with some virtual box VMs. See what you want, other than Fear Of Missing Out (things like PiHole? They run on Debian, or even in a docker container). Then see if you actually want a home server, and what you want to run on it.
It’s likely you won’t want a raspberry pi, but a $150 mini pc that can actually do what you want.

The majority of Europe survives.
Although their sockets are recessed.

I doubt it.
Tripping over a cable is as likely to damage the socket as it is to rip the cable out of the plug.
Any appliance that increases risk by being unplugged should probably not be using a consumer connection…

I think the 3 pin layout caused a lot of headaches, and the integrated fuse required a user-servicable plug.
So it would have to be a split-shell design of some type, where the appliance cable would have to be cable-gripped to the same part as the plug/socket pins.
Thus, a bottom-entry (heh) cable grip and a removable back plate that can only be unscrewed when it’s unplugged.
This was all in a time of bakelite. Plastic wasn’t flexible.

But no, I think tripping over an early bakelite g-type (I think it’s officially a g-type) plug cable would likely shatter the plug and pull the pins out of the socket… If it didn’t also damage the socket.

No, the cable comes out perpendicular to the pins (ie parallel to the wall).
Which pretty much guarantees foot-pain orientation