They were used by TSA to profile people, due to the fact that Al-Qiada used them to detonate bombs with.

See the Wikipedia article for the F-91W. https://en.wikipedia.org/wiki/Casio_F-91W

Edit: autocorrect.

I whole-heartedly agree with this one and I am genuinely not surprised about the behaviour of Vaxry.

To give some context around this, ThatOneCalculator (aka Kainoa, the person behind Firefish) and I maintained the AUR package for hyprland-git back in 2022. When I initially made the AUR package file, it wasn't great (and there were a lot of points to improve these packages) but it worked mostly. Of course there were edge cases where building broke, especially this was my first bigger AUR package to maintain. With it being a -git package in the AUR, breakage is to be expected.

Fast forward about a month, a month and a half. Hyprland rolled out some big changes which caused some build errors. But because my personal life got in the way, Kainoa got sick (IIRC) and I had troubles getting the build scripts working again, so it took a few days to get this resolved.

Vaxry came complaining to comment section of the AUR package "when are you gonna get of your lazy ass and fix this shit" (or something similar to that meaning, I can't find the original comment anymore). After that, I promptly disowned the package and let Vaxry handle it himself.

Because fuck that shit, as package maintainer, I refused to be treated like this. If you think it takes too long, sure, fine, ask if I need help, offer support, anything. But just don't be an asshole towards people, that offer your software to a wider audience.

Yes you can, it won't be great though.

I used to maintain a Linux distribution called "OpenWM8650" (back in 2011 / 2012) which was specially aimed at the WM8650 and WM8505. It would run off the SD card. Which wasn't great, but the flash onboard support was horrible at best.

Maybe you can find some old information on it, on XDA because the website for the initial distribution is long gone.

datab

Theoretically, support for that could be coming... Emby (where Jellyfin is based on) always used their own layer for interacting with a SQLite database. All that custom made logic is currently being swapped out for EF Core. EF Core is a DotNet library for interacting with databases and EFCore that also supports MySQL, PostgreSQL, SQL Server besides SQLite.

So my guess is that, once all that work is completed, support of other database can be added.

For a little bit of context. I am currently running Jellyfin on Btrfs and there is quite a performance impact due to CoW. If 2 clients decide to browse the libraries, both clients grind to a near standstill with regards to being able to see things. So I am following this work with quite some interest.

For all the oldies in the room, Lindows / Linspire (me included)

Trying to merge Wine with Linux into one ""convenient"" package was overselling it at best and worst a lie. Back in '08 / '09 I tried to run it, just to see how good (or bad) it was. It was basically Debian with KDE and their special sauce on top to ""easily"" run Windows binaries. Especially in those day, WINE wasn't as good as it is today. I think you can fill in the rest ;-)

One of the first things I did when I learned about Lemmy and joined an instance is see if I could contribute in some way, shape or form.

But unfortunately it's written in Rust, a language in which I have 0 experience and 0 knowledge. :(

OMG.... We zijn net met zijn allen fris en verenigd begonnen aan een nieuw platform en dan wil je nu alweer ons allemaal verdelen in kampen ?

Also, het is patat 👀

Oh sweet, sweet irony.

Just out of curiosity, where can I find those stats?

If I'd had to guess, woodworker or watermelon farmer.

Fun fact, kbin and lemmy should be able interact with each other without any issues.

I can totally understand that the main dev behind RedReader isn't particularly happy about, especially because he "was graced" by an exception.

In hindsight, this whole situation reminds me of Tweetbot. Being completely dependent on 1 provider for your app. Not sure, if that was a smart move. But hindsight is always 20/20.