I mainly write JS and not having a backtick on my keyboard annoys the fuck out of me. Other than that the Italian keyboard is alright, never had any other problems with it.

That guy has no idea of what’s going on but appears to be having the time of his life.

To add to the approved reply:

The GDPR has some other requirements to it, such as an EU-based representative being necessary for operating in the EU, allowing users to request data updates, and getting consent for data collected

You could make the argument that the mall Santas aren’t authorized representatives of real Santa, as they are hired by malls with no supervision from the North Pole administration. Thankfully this doesn’t matter, because Santa himself is a resident of Finland, an EU country, which is also where his business is located. Chistmas is saved, everyone.

Axios for requests - easier than working with the Fetch API in some cases

May I ask what cases? I used to use Axios on Node, before they implemented the fetch API over there but I haven’t touched it since. And defintiely never used it on the client. Could you make an example of some case where it’d be easier to work with Axios than with fetch?

Interesting idea. I’m currently working on a Lemmy-ui fork for my instance and including a feature of this kind in the frontend would be kinda nice.

I’ll bookmark this and come back if I ever get to it.

That wasn’t really what I was paying attention to the last time I looked at the logs but going off memory no, you can’t.

The Lemmy logs are very privacy friendly which is good most of the times but a tragedy when someone posts illegal stuff to your instance and you have no way of tracking them down.

Then I guess this is what you get for talking about something without knowing what it is lol.

As another user pointed out, TypeScript is a different language (.ts extension) that extends JavaScript, meaning JS code is valid TS code, but TS adds various language features for type checking. Your editor is then able to interpret your code according to these type structures and warn you if you are making any stupid type errors like this one:

The problem many people have with TS (such as the “big projects” mentioned by Fireship) is that sometimes you end up having code that works but still have to do some weird type gymnastics to please the TS compiler and have it remove any errors and warnings.

That being said, frameworks that “create really weird undecipherable minified JS” do have their place, as they allow you to seamlessy do things that would be either very inelegant and verbose or significantly more complex in vanilla JS, but I won’t bore you with an excessively long wall of text.

PS: I love your Czech flag website. Had me jump on my chair when the music started blasting through my headphones.

How is that related to TS? Aside from the fact that your comment might have just started a civil war (no, vanilla JS is not “good enough”, they created libraries for a reason) this isn’t about using libraries / frameworks. It’s about needing some system to handle type annotations to avoid falling in the bottomless pit of:

Uncaught TypeError: Cannot read property of undefined

The backend is quite alright. The Rust backend makes it indimidating to approach, but I know it has many advantages.

The frontend could use LOTS of changes. I don’t like Inferno, it’s messy and confusing to work with. Instead, I would have opted for a Svelte+Tailwind stack for the UI.

There’s plenty of applications that aren’t critical enough to require precise memory management and where a GC is a worthy tradeoff for the simplicity that Go brings to the table, but sure, if you are interested in going super low level that’s what you are left to work with.

And it’s probably fine. If I had to pick between C++ and Rust I would choose the latter any day of the week but thankfully not every developer has to go that low.

I was under the impression that the Go compiler was written in C/C++, though don’t quote me on this one. My browser however is Firefox, so touché on that one.

Hot take:
Fuck TS, marry Go, kill Rust.

Interesting. That would be a nice extension, I think most small admins are using the filesystem (I know I am lol).

No. Unfortunately it only works with storages on object storages like S3 buckets, not with filesystem storages. Meaning it access the files remotely one at a time from the bucket, downloading them over the internet (I assume, I didn’t make this).

But the more important thing is that, as it states in the readme, no files get saved to your disk, they only stay in your RAM while they are being processed and everything is deleted right after. This is relevant because even having had CSAM on your disk at some point can put you in trouble in some countries, with this tool it never happens.

Which btw is the same reason why mounting the pict-rs folder to your local computer is probably not a good idea.

Yeah I know. It’s supposed to be ran from your computer, not the VPS.

Same, it’s the reason why I can’t stand working with python.

Thank you for doing this, btw. Once you have something working on your hands you could consider spreading the word, maybe to db0 himself. I sure would love a convenient way to run that script, and many other admins probably would too.

I see. I considered the dependency problem but only thought of using a venv to fix that, however you are right, the python version is also often the cause of compatibility issues.

Sorry I haven’t ran this myself yet nor have any experience with that kind of issues. But may I ask why you were concerned with running it inside of a container? Seems rather unnecessary to me.

That is also very true. I think better tooling for that might come with the next pict-rs version, which will move the storage to a database (right now it’s in an internal ky-value storage). Hopefully that will make it easier to identify orphaned images.

I’m an instance administrator, what the fuck do I do?

There’s one more option. The awesome @db0@lemmy.dbzer0.com has made this tool to detect and automatically remove CSAM content from a pict-rs object storage.

https://github.com/db0/lemmy-safety