SuperFola

I wanted to design a funny keyboard with an alternative to TRRS, so I made this floppy disk sized keyboard! (Perfect replica, under 10cm x 10cm)

I made a build guide for it too: https://lexp.lt/posts/floppy_keyboard/

I tried accessing https://programming.dev/c/programming_languages but it tells me that the community can not be found. Is that a lemmy bug?

TLDR: perfctl is a crypto mining and proxy jacking malware that exploits about 20’000 common missconfigurations to install itself on Linux servers. Mostly using a 10/10 CVE on Apache RocketMQ.

It is very persistent and can reinstall itself even when you have deleted all the perfctl and perfcc files. It hides itself by removing logs, network packets, and stopping all activity once you login to the machine.

Monitoring cpu usage using tools (I use net data on my server) can help identify infections (100% cpu usage when « idle »).

I’ve started putting the (long) forum posts I make about ArkScript on my blog, so that more people can follow the development. I must say I like the look of it, that’s also helping me getting back into blogging!

cross-posted from: https://programming.dev/post/18859576

This past few weeks, Python 3.13 and the possibility to disable the GIL has seen a lot of coverage and that pushed me to dig into my own language, to see how different our approaches are.

So if you’re curious about the rambling of a pldev, that might be for you!

I just wanted to have a handy description of computed goto that I could refer to, to reuse this concept without having to read thousands of line trying to make sense out of it.

This past few weeks, Python 3.13 and the possibility to disable the GIL has seen a lot of coverage and that pushed me to dig into my own language, to see how different our approaches are.

So if you’re curious about the rambling of a pldev, that might be for you!

I thought you guys might enjoy it: I have a website that I push to frequently on GitHub, and some GitHub actions that update it periodically by pulling code and generating docs from it. I needed to connect to my vps often and update the website which was cumbersome.

Well a solution is to use webhooks on push events and have a server listening to those events to then update said websites for me.

I had some fun trying to check if a hash (more like a transformation really) was collision free, so I wrote a quick piece code and then iterated on it so that it was usable.

I might add a quick bench and graphs and try to push it even further just for fun, to explore std::future a bit more (though the shared bit set might be a problem unless you put a shared condition variable on it to allow concurrent read but block concurrent writes?)