piaste

Yeah, I've been running Kinoite since it came out and I agree. The name is still very obscure, I'd be happier to just tell people "I run Fedora KDE Atomic".

I run GrapheneOS. It's an amazing project, and I always pay attention to what their developers say.

But you should keep in mind that the GrapheneOS project is very laser-focused on a certain threat model: aggressively malicious software that tries to exploit vulnerabilities to escape its sandboxes. And they fight against that threat very well (there have been a couple of recent high-profile Android CVEs to which GrapheneOS users were immune).

But they are - rightfully - less concerned about the far more common threat of apps including crapload of tracking libraries, battery-burning ads, or dark patterns requesting unnecessary permissions. They provide you with tools to fight them - Storage Scopes and Contact Scopes are amazing! - but ultimately it's up to the user to e.g. choose a serious calculator app like Calculator++ instead of some spyware.

And against that threat, it is an excellent idea to search on F-Droid first instead of the Play Store (where the first non-Google, non-Samsung result is indeed an ad-filled spyware calculator). Then, if you want to secure yourself against the possibility of the F-Droid signing keys being compromised, you may choose to delay/disable automatic updates, or simply to download the Play Store version of the F-Droid-hosted apps.

> It's almost as if the creator(s) built that site ironically.

No, the site's advice is simply more narrow and fine-grained than a blunt 'never use jquery'. From the front page:

> jQuery and its cousins are great, and by all means use them if it makes it easier to develop your application.

> If you're developing a library on the other hand, please take a moment to consider if you actually need jQuery as a dependency. Maybe you can include a few lines of utility code, and forgo the requirement.

This seems eminently reasonable to me. For a website, adding a jquery dependency costs little and you get much nicer, more maintainable code.

But for a library, every transitive dependency introduces the possibility of future version conflicts for applications that depend on it. And at the same time, library code shouldn't need to change and grow nearly as much as application code.

So library authors should strongly consider forsaking mere convenience for the sake of reducing dependency baggage. This isn't even JS-specific advice, it applies to most ecosystems.

Who said anything about trust? Server-side validation still applies; you don't just DELETE /user/{id} without verifying ownership, regardless of where the id comes from.

But client-generated IDs make idempotency easier and remove whole classes of errors. They're typically a huge win.

When I lived in a small European town a few years ago, upon hearing that I was a software developer, regular-ass business dudes would regularly want to talk about NFTs, inbetween a conversation about football and one about cars.

I'm sure there are weirdos in the web3 spaces, but I feel like they're very outnumbered. Projects like ENS or IPFS are probably much more interesting to weirdos than most "crypto stuff". I2P too, though I don't think this twenty-year-old project should be lumped in with "web3".

I think the Fediverse is a better place to go. Lots of little communities, almost all of run by regular nerds, each one with their own quirks and petty personal drama and constant UI tweaking? It's like forums all over again, except it's now safe to use one password for everything.

Copyright covers the specific work of art you created, not anything that looks like it. Birdman didn't violate Batman's copyright even being an international callback. Nor did every superhero movie that tried really hard to copy Nolan's style after his trilogy.

It was perfectly fine in 2023 to create a cartoon about a prankster mouse called Nicholas sailing a steamboat. What became legal in 2024, with the copyright expiration, was to give him those exact pants and ears and call him Mickey.

I'm not familiar with Pokémon, so I'm not sure if the PW cartoon monsters are literal copies of the originals or just drawn in the same style.

Thanks for the link! I think I had in mind another one, where the UB fuckery happened at a lower level (I think you ended up with a semicolon/brace effectively "disappearing"?). But that's a good example too.

The parent's point is that there is no separation between "before" or "after", it all ends up in the same artifact. And when you write invalid code, you have no guarantees about the compiled artifact anymore.

There is an example of C code (fairly sure I saw it on HN) where violating a UB rule caused an entirely dead piece of code to suddenly be executed, which even made sense after explanation.

In the linked article, Rust-minus-borrow-checker somehow caused an invalid number to appear inside a compile-time static array.

Sure, poke around the results of UB all you want. Curiosity is great. But at some point you'll have to compile your hypothesis as part of valid code, to be able to trust the results.

When internet infrastructure was much less advanced, the server application used to be part of the delivered product so you could host it yourself at a LAN party.

I understand that packaging, documenting and supporting an additional application is a cost that the company would rather avoid if possible. But upon shutting down a game's servers, it would cost them nothing to provide the discontinued app code "as is" with no warranty or support, to let fans figure out how to run or improve it themselves. I doubt most game companies have any incredibly valuable and cutting-edge networking code worth protecting.

They don't. Freemasons as we know them grew established about a century later than the institutions described in this book, and their origins are in Northern Europe.

Yet. On March 6 WhatsApp will need to be compliant with the Digital Markets Act, which includes an interoperability requirement. We'll see what they hash out between Meta and the EU Commission.

I think OP's point was that SEPA and IBAN are completely different things.

SEPA is the Eurozone area that treats all transfers as domestic - usually free or near-free, and fast (max 1 day normally, max 10 seconds for instant transfer).

IBAN is just a numbering scheme to uniquely identify bank accounts worldwide. It has nothing to do with transfers. The closest thing would be SWIFT, though that's just an information protocol and says nothing about fees or times.

> maybe Mathematica will turn out to be the FTX, or Tesla auto-pilot, or ..., of mathematical software/languages.

You can install Mathematica at any time. It produces graphical output. You can see for yourself what it does, and what it does not do.

If Wolfram were making claims about a future unreleased version of Mathematica, sure, I would absolutely weigh his ego against those claims. But they are largely irrelevant when it comes to a currently existing and available product. If he were to claim that Mathematica 14 cures cancer, that would deserve eyerolls but it wouldn't tarnish the quality of the software.

That's why they diplomatically added "in the x86 market" :)

That's actually the critical part and much more relevant than the exact scores achieved.

According to the linked article, the main reason Eliza got such a pass is because the testers were looking for a ChatGPT-esque giveaway. Long-winded, frightened of controversy, prone to hallucinations.

Which Eliza is not. And (presumably) not being familiar with Eliza, they thought it was another bored human test subject putting in the absolutely bare minimum effort.

Eliza didn't pass for a human - it passed for not-a-LLM.

What you describe would be literally worse than nothing. The use of those concepts would make about as much sense as the use of topological concepts in a Lacanian text. A typewriting monkey in a trenchcoat.

How did the moose damage the beaver habitat? Do they forage the same plants and outcompete the beavers at them?

The first talkies were artistically inferior to the best silent movies of the time, too. And shooting in black and white retained its charm for a long time after Technicolor.

Proclaiming that a strictly bigger toolset is "[a]esthetically inferior" because directors are still learning how to use it is pure reflexive conservatism. There's no reason you have to show wrinkles just because you're shooting in 8k, it just becomes possible to do so while it was impossible before.

So? 35mm movies were shot at 24fps while TV shows used higher frame rates. And because TV shows used to be cheap soap operas or comedies, for a long time high-FPS video gave you a feeling of cheapness. But that doesn't mean that 24fps was actually better! It was a technological limitation that got enshrined by its use in high art.

I imagine this is where the Firestick and TV came in - screencast termux or ConnectBot to the TV so you can use the phone in horizontal mode as a larger keyboard.

For context, this isn't an official mark created by China or any other entity.

It's just some fraudulent manufactures that are using a paper-thin excuse to illegally apply a fake CE mark.

It's a different style of introducing a fantastical setting compared to the classic exposition dump, or the clumsy audience- substitute narrator who keeps asking for explanations, but it's far more engaging if you just let yourself enjoy the ride for a bit.

For example, I believe that early on the narrator speaks about his mother 'going to Heaven' - you're supposed to be curious about what exactly that means, since it's clearly not the same way we use the phrase. You're supposed to look forward to the eventual explanation, and to trust that there will be one.

Of course if that explanation never comes, and the detail is critical to the plot, that's a failure of the author. But no different from any other plot hole - that's what reviews are for.

Any web search for 'social media mental health study' will provide as much evidence as one could possibly expect for that statement.

> Could it not tell if it's actually managing to play and keep up with time? Similarly to how (I believe) it'll degrade if the network is such that it's not loading 4k say quickly enough, it'll switch (if 'auto') to 1080p or whatever.

Probably, but it's pretty poor UX if videos start super-choppy by default and slowly downscale to a playable resolution over several seconds. Having a good default is still important.

> "BG3" on the otherhand innovates on Divinity: Original Sin 2 instead and then slaps a Baldur's Gate paint on the result.

Do you think that the setting, themes, story, and RPG rules are just 'paint'? Is the Infinity Engine so much more important than the Forgotten Realms?

> I also don't see why games should be inherently different from other media in this respect.

Because games aren't media: games are media generators. The same game can be a tragedy to one player and a comedy to another. So you can have two different kinds of follow-ups: ones that simply generate more media in the same way ( = expansion), or ones that improve on how the media is generate ( = sequel). The distinction doesn't make sense for fixed media like novels or films.

Note that I'm not talking about video games in particular, it applies to any kind of game. If I publish a book that adds a new secret level to the crypt of Acererak in the same style as the original, it's an expansion. If I publish a story about a different crypt that feels connected to the original but with its own unique design choices, that's when I can call it Tomb of Horrors 2.

> So yes, a different studio being given the license for the sequel (which is already a very questionable practice that rights holders should be called out for) should strive to mimick the feel of the original game very closely.

I'm just going to have to fundamentally agree to disagree. I would 100% endorse this quote if we were talking about novels or theatrical plays, and maybe 50% if talking about movies (Godfather? Yes. Alien? Nah).

But a game, outside of odd niches like visual novels or 'walking simulators', is a much more open-ended experience, and the expectation of a sequel is not merely to continue the story - that's typically called an 'expansion', a concept that doesn't exist in novels or movies. A sequel is generally expected to innovate, and the longer since the previous title the more innovation is expected.

Treating with respect != slavishly mimicking a previous studio's effort.

Just because there's a '3' in the name doesn't mean it should feel like a clone of '2', especially when the studio changes. Dune II was a completely different game from Dune. GTA 3 was completely different from GTA 1/2. Armored Core. Max Payne. Wasteland.

Sports game and certain shooters are widely mocked (among nerds) for being basically identical release after release.

Nostalgia is literally the only thing AD&D has going for it - it's a clunky, incoherent, and thoroughly unbalanced mess, designed when tabletop gaming was only a decade or two old.

We've had 35 years of experience with tabletop and CRPGs since then, both with systems that tried to stick closer to D&D and with ones that tried new things altogether.

The Divinity system isn't perfect by any means, but I can't imagine how rose-tinted your glasses must be to think that THAC0 and the golden age of Linear Fighter, Quadratic Wizard are better.

Even that may not be immediately necessary. I don't think SQLite has it yet, but Postgres can build partial indexes on JSONB fields.

Though most of the time, in that situation, I would pull it out.

There's a gradual approach there, where you start out with a JSONB column, and then as each piece of the data structure stabilizes* you move it out of json fields and into its own columns/tables.

* meaning, when there's enough code that depends on it that changing it would require some planning