redjard

op on their recent shopping trip

I’ve had it on my todo for years to work through ddc and trusting trust.
Which is a method to verify a compiler is matching its source and thus trustworthy.

An orthogonal approach is reproducible builds, which among many benefits can make sure a few people verifying things benefit everyone who can then see they have the same verified binaries.

Also known as zombie files. If you are unlucky they can take up all space on a drive, or even tmpfs (so your ram) and you can’t easily find them. At least until you end the right process or restart.
Had that happen once and had to write my own script to trace it to the log of an open terminal emulator tab that had billions of lines.

What about the typod grep spamming a million lines, or running htop and interactive things?

Sega doesn’t want to preserve the ownership of their ip, they were bought by a gambling company who took on their name and is using sega as a public relations shield.
Their aim is to keep sega in high public esteem.

Meanwhile Nintendos ip is extremely valuable compared to the size of their company, so their aim is to protect ownership way more than making new games or other ongoing business.

International ip law is weird, so letting fanmade games go runs a risk of loosing ip. For Nintendo that is even more dangerous than for other studios whose ip value compared to revenue is not as extreme. While for sega ultimately loosing ip control is basically the point of the investment.

And this spray bottle

the sad reality is that to play at the peak of any modern sport, you have to take some tradeoffs on your health.

Also seo, I’ve sadly seen 4 year abandoned random forks rank as the first result and the actual project way below, just because it was on a self-hosted git. iirc that was the freedesktop one, so definitely not small, new, or low volume either.

njalla. Privacy is their point and they have a simple to use api.

That’s interesting, what tld was that on? That has to be done by the domain authority right?

If your registrar goes rogue there’s not much you can do. Custom NSs may buy you 12h.
This separation gets you that it either breaks 100% or 0%. You’re safe from ongoing enshittification until they kill custom NS.

Yes, they do have a contract with you, and do have phenomenal reputation, but they are a second entity with technical ability to take your domain, in addition to the regular registrar they run through.
In practice their status and contract with that partner probably makes it less likely your domain will be taken for for example legal reasons, compared to a typical registrar end-user contract.

All are that the first year. I had someone in person tell me how they were put on a severely increased price despite being on a domain that should be very cheap. Sadly I don’t recall who it was, so I can’t ask them for the details.
The jist iirc was their domain got popular (due to their website), so xyz decided it belonged to a higher price category.
This was definitely not 1.111b specifically, but with a short search there I found reports that xyz has apparently decreased the scope of the 1.111b category before, making the minimum length 6 instead of 3, and then refused renewals for people that had 3-digit domains under the old price.

So I would expect arbitrary price increases on 1.111b too, it’s not something I’d rely on. xyz always has the right to charge whatever they want, so you are one policy decision away from switching everything with no notice or shelling out whatever they think they can charge.

Compared to say .com, where there is a rigid contract of what verisign can charge, mandating a single price category, a set number of price increases with a set maximum increase, no difference between first year and renewal, …
Or .eu which is free and only has registrar fees, so you could just migrate to a different registrar.

Edit: 1.111 not 1.1111

Others let you set custom NSs, so you can fuck off from their bullshit. You are stuck with cloudflares lineup here.

Issue is you are locked into the cloudflare system that is gradually enshittifying. Apparently NS changes are blocked, so you are stuck with them. This is not the case for other registrars.

Also for .com they are below wholesale, so they are banking on that enshittification.

xyz get you on renews, it’s a scam. Once you are set up with the domain and it’s hard to switch, prices explode. This is enforced as tld pricing.

It’s below wholesale for .com
(this is because you’re part of the price)

cloudflare sells below cost, so expect to be nagged by “features” and have trouble e.g. using your own nameservers to get away from them.

Also they don’t sell the truly cheap stuff like .eu because they’re not nonprofit.

For .xyz they do make a good compromise, but xyz itself is a bad choice to start with.

xyz isn’t that cheap (and shady (in reputation and pricing practices)), you might wanna pick a better tld.
I don’t see a wholesale price so it’s hard to judge with certainty, but xyz might be around 14$/y. Dynadot is selling .com at a loss, so I assume they do the same for xyz. Don’t use them, they will make that money off you some other way.

Wholesale for .com and .org is 11$; I recommend njal.la who charge 15$ and for those 4$ add the by far best privacy available for domain registration.

For a cheap reliable tld, maybe .eu is a good pick. From the looks, the wholesale price is 0, so legitimage registrar’s costs can get very low. .eu only allows non-profit registrars.

With IPv4, assuming you have a residential contract without cgnat, your router has your ip. Loosely your device calls your public ip, realizes it is not on your local network, and sends it to your router. The router will nat it, and send it to its own internet-facing networking side, where the same router will realize that the target ip is the ip of it’s own interface and will immediately accept it. Then it is handled like any other packet arriving from the internet, presumably port forwarded to some internal machine.

So we expect one hop to the router, then one internal hop from the private to the internet-facing interface of the router, and then presumably another internal hop back to the private network interface and another proper hop to the server on your lan.