Amju Wolf

…and that’s how it still works.

Considering those scanners usually register as keyboards and just do a dumb input “typing” it shouldn’t even be hard, lol.

The worst part would probably be picking a barcode scheme where the inputs make sense…

Also, this isn’t even compatible with copyright law in some countries. I.e here you can’t give up authorship at all; you can only grant an irrevocable, perpetual license (that might even prohibit you from distribution yourself and such) but you’ll always be able to say “I made this” no matter what their license says.

That sounds very illegal, yeah. You can’t advertise a price and then charge something different. It doesn’t matter that the person didn’t notice it. At that point you might not have price tags at all (which is also illegal, just FYI).

For all the hate PHP gets (or used to get) it’s ecosystem is amazing. And so is the language and standard library itself for the most part. It still inherits some of the original issues, but a lot of work has been done to minimize them.

It’s funny because despite all the fearmongering about Microsoft’s Github acquisition it feels like it only improved since then, while Gitlab has done a shitton of questionable and shitty decisions, a ton of critical security issues and in general feels like (at best) they don’t know what they are doing.

The only thing Gitlab has going for itself is that it’s self-hostable, but they still retain a large amount of control.

It generates code and then you can use a call to some runtime execution API to run that code, completely separate from the neural network.

On the contrary, it’s the only comparison you can make, since they are literally the only options.

…and there is no way to do that, currently.

That’s not something that’d likely scale enough to bring any meaningful sum of money.

Even then it targets a tiny, tiny minority of their even current userbase, let alone if they want to approach more “average” users.

Unfortunately not; the UK is more or less an exception because they were there very early and copied the US model.

Time has shown though that everyone wants second level domains anyway so even .uk is now open to anyone and they have the weird hold-over .co.uk and similar domains.

Because a lot of the content on national TLDs is relevant only for people of that nation. It helps with name clashes and pushes off stuff that doesn’t make sense in any of the more “global” TLDs.

And for governments, banks and other institutions there should really be some official standard where they pick a single second-level domain and use it for stuff that needs to be secure so anyone anywhere can be sure it’s controlled by the correct entity and not a scammer.

They’re two separate(ish) issues.

But it’s still a bad idea to use national TLDs for stuff that has nothing to do with that nation.

Granted, is ICANN wasn’t just a money-grabbing machine with no forward thinking they wouldn’t give nations clearly “generally desirable” gTLDs, but since they did already that doesn’t mean they should be misused.

I had a similar issue and in my case it ended up being some AMD crap (I think an updater or something) that probably didn’t install properly or something.

IIRC I just ended up disabling the scheduled task that was running it and that was the end of it.

That would give random strangers (at least partial) control over what is indexed and how and you’d have to trust them all. I’m not sure that’s a great idea.

This is cool but it’ll be a nightmare to update.

Also, chances are that if you use Alpine the person using your image already has the base layer downloaded, so your image might actually be “bigger” for most people.

Sounds like cruel and unusual punishment to me. I wonder if he could still fight it. Sure doesn’t sound too bad until you realize that it’s literally only to make an example out of someine while ruining his entire life for a crime with no victim.

Yep, exactly my thoughts. Unfortunately very few developers really think (about related but not completely adjacent code) when they implement stuff (and that’s when they are even “allowed to” by the task requirements) and even fewer have true knowledge of security and common pitfalls and whatnot to avoid such issues.

And even when you have those you still need good practices and code reviews where the rest of the slip ups is caught.

Ehh their engineering simply seems to be subpar. I’ve read some of the CVEs and if they followed best practices the issues should’ve never happened. It doesn’t inspire confidence.

For the people who do find out about it and it hooks them enough sure, it’s not really forgotten or underrated. But I still think it’s kinda obscure / not well known?