aksdb

joined 9 months ago
[–] aksdb@lemmy.world 2 points 1 hour ago

You could look into prose. The interface of slack/discord/mattermost, built on XMPP, with E2EE.

[–] aksdb@lemmy.world 1 points 2 hours ago

What's wrong with that? Do you expect their backend to run off a single server with a little PHP script? The components seem pretty reasonable (with the actual business logic being just a small part).

[–] aksdb@lemmy.world 6 points 1 month ago

Bitwardens local cache does not include attachments, though. If you rely on them, you have to rely on the server being available.

[–] aksdb@lemmy.world 8 points 1 month ago (2 children)

While I like and appreciate the campaign, the issue IMO is bigger. IoT devices for example even have environmental impact when services behind them get discontinued.

I would therefore like a more general rule: whenever a product is discontinued for whatever reason, all necessary documents, sources, etc need to be released to allow third parties to take over maintenance (that also includes schematics for hardware repairs).

[–] aksdb@lemmy.world 22 points 2 months ago (3 children)

I don't understand how that hybrid is supposed to work. Monospace is a binary attribute; either all chars have the same width or not. So what is the font now?

[–] aksdb@lemmy.world 1 points 2 months ago

Why? What did Zenimax do to you?

[–] aksdb@lemmy.world 20 points 2 months ago (3 children)

Unreal Tournament

[–] aksdb@lemmy.world 5 points 2 months ago

Most people in my company use OSX, followed by a few dozen Linux users (various distros; whatever each one prefers), followed by a few Windows users (whyever they want that). So essentially: we can choose what we want to use.

[–] aksdb@lemmy.world 30 points 2 months ago

They also fuck over their own OS. I don't think they deliberately broke dual boot installs, they simply don't put enough effort in QA. (See their recent problems with BitLocker after an update. Or that one update that fails because some internal partition is too small. And so on.)

[–] aksdb@lemmy.world 5 points 2 months ago

Fli4l is still around?! Crazy. I used that back in 2002 or so to turn an old i386 with 3 ISA HP 100Mbit network cards into a router + fileserver combo. Good times.

[–] aksdb@lemmy.world 7 points 2 months ago

glibc's malloc increases the stacksize of threads depending on the number of cpu cores you have. The JVM might spawn a shitload of threads. That can increase the memory usage outside of the JVMs heap considerably. You could try to run the jvm with tcmalloc (which will replace malloc calls for the spawned process). Also different JVMs bundle different memory allocators. I think Zulu could also improve the situation out of the box. tcmalloc might still help additionally.

[–] aksdb@lemmy.world 13 points 2 months ago

I wonder if that would be a genuine use case for "AI". If the voice actor consents to have his voice represented in such a scene but doesn't want to play it out in a studio, the computer model could take over that part.

 

Each time I try AMD graphics, something is fucked for me. Back with fglrx, fglrx just sucked, so I used Nvidia. Then I had an AMD right around when they finally had opensource drivers, but it was still buggy as hell. So I went with Nvidia again (first a GTX 790, then a GTX 1060). In the meantime I had a new work notebook where I also went with an AMD APU, and had driver crashes for a long time when I was in video calls and it had to decode multiple streams. That thankfully stabilized with Linux 6.4.

Since sooo many people in the community swear by AMD, I thought "dammit, let's try it again for my new desktop" and got an 7800rx ... and I have to reboot ~5 times until I finally make it to a running xserver or wayland session. Apparently I am hit by this problem (at least I hope so). But that doesn't even read nice ... the fix seems to be to revert another fix for powermanagement. So I either have a mostly non-booting card or suboptimal power management.

I start to regret having chosen AMD .... again :-/ I seem to be cursed.

view more: next ›