The “.net” makes me think it would be some online service that runs on remote servers or ties you to some online platform without any real gain other than just to increase their level of control over the customer.

You share public keys when registering the passkey on a third party service, but for the portability of the keys to other password managers (what the article is about) the private ones do need to be transferred (that’s the whole point of making them portable).

I think the phishing concerns are about attackers using this new portability feature to get a user (via phishing / social engineering) to export/move their passkeys to the attacker’s store. The point is that portability shouldn’t be so user-friendly / transparent that it becomes exploitable.

That said, I don’t know if this new protocol makes things THAT easy to port (probably not?).

There are many games that had that mechanic before Arceus.

In particular, Craftopia (which is from the same developers of Palworld) had capsule devices that you can throw to enemies in a “virtual space” while characters “engage in combat” before Arceus was a thing.

Just because they wrote a patent does not make it enforceable… patents don’t really mean anything until they are actually tested in court so they are just tools to try and scare people away whenever a company wants to bully with the prospect of a lawsuit.

I feel that Palworld is likely to win this, this actually is an idiotic move from Nintendo and a win for Palworld… now they will get more publicity, perhaps another spike in sales, and they are finally given the opportunity to prove how they are in the right, so they can shut up all the naysayers who complained about it. I’m hoping all the paranoic empty claims about “blatant asset theft” will be settled once and for all.

I think that was already done a while ago with Swanstation libretro core.

If you are into open source, give Remnants of the precursors a try, it’s a modern spiritual successor of the oldie Master of Orion.

Bash. By default it might seem less featureful than zsh… but bash is a lot more powerful and extensible than some give it credit for. It might be more complex to set it up the way you like it, but once you do it, that configuration can be ported over wherever bash exists (ie. almost everywhere).

I have purchased every single open source game that I’ve seen listed on steam as paid. Examples:

• Shattered pixel dungeon (and also the original Pixel Dungeon)
• TOME
• Shapez
• Open Hexagon
• Mindustry
• Lugaru
• Mega Glest
• Marvellous Inc
• Hydra Slayer
• HyperRogue

For more FOSS games on steam, there’s a decent list collected on this curator (also pointing which ones are only partially open): https://store.steampowered.com/curator/38475471-Libre-Open-Source-Games/?appid=1769170

The thing is that we do have “Morning!”, “Hello”, “Hey”, “Yo!”, “Hi!”… and many other greetings that are not in the form of a question that actually leaves it open for the other person to respond with honesty and that is often also used as a conversation starter. If you really aren’t open to a conversation, use one of the shorter friendly greetings.

If I say “how’s it going?” and they answer with something I don’t have time to hear… at most I would excuse myself and politelly say that I don’t have too much time to talk… but complaining about the other person actually answering truthfully makes no sense.

Of course it’s just a comic, but still… I don’t think the one answering is in the wrong here.

like how not being able to sign up for something with tor and monero is a privacy violation, it’s not.

Note that “secrecy” and “privacy” are often understood in Security lingo as different things. One protects confidentiality, the other one protects anonymity.

It’s possible to have one and not the other…

You can have a very private system through onion routing but have the contents of the messages exchanged be in plaintext, open to the public. Nobody will be able to know the one who wrote the message was you. But they can see the message. (then there is privacy, but not secrecy).

Or you can have very strongly encrypted communications (say HTTPS) but have the DNS exchanges (or the TLS handshake, or the IP addresses) be in the clear, so people in the middle (eg. your ISP… or your workplace tech guys) can know exactly that the packages are sent by you and where you sent them, even if their content is encrypted. They can know which service you tried to access to, for how long and how many times (so you have secrecy, but not privacy).

I think part of the reason why the long extension is often preferred is because it’s much clearer and it’s guaranteed to be supported and decompressed by the respective tools. Even when they don’t suppot tar archives, they’ll just give you the uncompressed tar in that case.

It’s also very common to do that with other extensions (not just .tar) when compressing big files. For example, when archiving logs they’ll often be stored as .log.gz, which makes it automatically clear that it’s a log file directly compressed with gzip and meant to be examined with tools like zcat and zless to view it.

And in cases like that you really need it to be clear on what data does the gzip stores, since it does not keep metadata about the file so you might not be able to get back the original name/extension of the file if you rename the gz file.