lemmyng

Do I read these top to bottom or clockwise?

It’s not free of risk (regional datacenter outage, account termination), but for a lot of companies the above are acceptable risks compared to the cost of managing this yourself.

Structure like a skeleton. Gives you the rough shape, but you have some freedom to arrange the squishy bits hanging off it.

Think of that human torso being a very complicated neck rather than a half of a human grown onto a horse.

Now I can’t stop thinking of centaurs as giraffes with arms stuck to their neck.

Reddit has been astroturfed so much the recommendations there have to be taken with a lot of salt.

shitdown -h now

Stupid sexy Flanders Patrick.

It has implications on the effectiveness of VPNs on public networks.

1. A static IP is actually not necessary, but what you need is a consistent identifier. For the server, that’s typically a DNS address, but for clients and peer to peer networks there’s other ways to identify devices, usually tied to an account or some other key kept on the device.
2. For centralised communications yes, you would need an always online server. For decentralised networks, you just need a sufficient amount of online peers, but each individual peer does not need to be always online.
3. Pretty much, yes. Even push notifications on cell phones work this way.
4. Route, yes. Manually. VPN is usually not necessary. In modern web-based services this is typically done with websockets, which are client-initiated (so the client address can change), and which allow two-way communication and typically only require a keepalive packet from the client every minute or so.

There’s other reasons why universal addressing is not done - privacy, network segmentation, resiliency, security, etc. And while IPv6 proponents do like to claim that local networks wouldn’t be strictly necessary (which is technically true), local networks will still be wanted by many. Tying this back to phone numbers - phone numbers work because there’s an implicit trust in the telcos, and conversely there’s built in central control. It also helps that it’s only a very domain specific implementation - phone communication specifications don’t change very often. On computer networks, a lot of work has been done to reduce the reliance on a central trust authority. Nowadays, DNS and SSL registries are pretty much the last bastion of such an authority, with a lot of research and work having gone into being able to safely communicate through untrusted layers: GPG, TOR, IPFS, TLS, etc.

Whoa, that’s a sizeable edit to the post! Regardless the answer is pretty straightforward: your VOIP client (either the device if you have one or the software) is connected to a VOIP service which acts like a gateway for your client. Since the client initiated the connection to the gateway and is keeping it alive, you don’t need to make any network changes. Once the connection is established, standard SIP call flows (you can Google that for flow diagrams) are followed.

So no, you router is not part of the cell service. The VOIP provider is part of a phone service that receives calls and routes them for you, just like the cell towers are part of a telephony provider that routes calls through the appropriate tower.

Laptops don’t get a new IP address every time they switch from one AP to another in the same network either. Your cell phone will get a new IP address if it switches to a different cell network.

Sure they can. If you put a network behind a router they will share an egress/ingress IP. And there are certain high availability setups where computers share IPs in the same subnet for hot/standby failover.

Just because it has a CVE number doesn’t mean it’s exploitable. Of the 800 CVEs, which ones are in the KEV catalogue? What are the attack vectors? What mitigations are available?

You did a recursive chown or chmod, didn’t you.

Here’s a third one: They have a Welcome Stamp visa program where you can work remotely from there for a year, and it’s renewable. You can even bring your family. Under this program you only pay income tax on your country of origin.

Bazzite is a good HTPC or living room gaming distro. It is not an ideal all purpose desktop distro, just like a Steam Deck is not an ideal all purpose desktop system.

If you want a Bazzite-like experience that is better suited for the desktop then use Fedora Silverblue, which is what Bazzite/ublue builds upon.

Slack? Threema?

deleted by creator

I used a Fractal Design case for a home server in the past. Pretty happy with them.

Just to clarify, the previous comment asked about benefits of XFS over ext4. But I completely agree with your reasons for choosing ext4.