SuitedUpDev

What makes you say that ?

Hello 😁

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.

Luckily I don't fly to the US 😉

I am currently rocking a Shanling M2X which I bought secondhand for €75,- from the local classified ad websites.

Officially supports up the 512Gb but according some reviews it can do up to 2Tb microSD cards ( https://headfonics.com/shanling-m2x-review/ ). I currently have a music collection of about the same size. The Shanling M2X can drive all the IEMs I throw at it, has enough file system support to read just about anything and has WiFi and Bluetooth. Although the WiFi can only be used to wirelessly sync files (which can be a pro but also a con, depending on how you look at it).

However if you don't feel like going secondhand, Shanling offers a whole bunch of devices meant for offline playback of local files.

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.

Het idee was ooit van de privatisering dat het "goedkoper en beter" zou zijn dan het door de overheid het laten organiseren.

Vervolgens proberen we voor een dubbeltje op de eerste rij te zitten en hebben we geprobeerd met de markt te reguleren, door de vervoersbedrijven te dwingen tot een bepaalde minimale standaard. En dan vinden we het collectief raar dat er geen commerciële partij is, die het wil uitvoeren.

Dit soort basisvoorzieningen moeten gewoon niet in handen van commerciële partijen komen. In steden zoals Amsterdam, Rotterdam, Den Haag, Utrecht, Groningen etc etc, zou het THEORETISCH kunnen werken maar in landelijke gebieden werkt dat gewoon niet. Voor een commerciële partij is de "winst" gewoon te laag, voor het risico dat ze lopen.

That will work as long as EF lenses are still available.... But Canon already took some lenses out of production.

So basically, that's gonna be a dead end path.

As a current Canon photographer (700D owner) going mirrorless is definitely the future. Canon and Nikon have basically given up on DSLRs. (https://www.engadget.com/why-nikon-and-canon-have-given-up-on-dsl-rs-133042286.html).

However, I want to highly stress out to avoid Canon for mirrorless. The reason behind it is that Canon has been "defending" their mirrorless mount relentlessly. Meaning, that no other 3rd parties without Canon's blessing can make lenses for the RF mount. (Source: https://petapixel.com/2022/09/06/canon-confirms-its-going-after-lens-makers-for-patent-infringement/)

So unless you wanna spend big bucks on Canon approved lenses, I'd go with either Nikon, Sony or one of the other mirrorless brands.

Fun fact, Sony is actually quite permissive in the licensing of their E mount. So they will basically let everyone make lenses for the E-mount.

Debian Woody > Red Hat 7.0 > Slackware 9.0 > Slackware 10 > Debian > Ubuntu > Mac OS > Ubuntu > Arch.

At least for desktops and laptops.

For servers I'm still primarily running Debian (and one instance I'm running Arch).

The reason why I settled on Arch is primarily because the combination of bleeding edge and being stable enough for daily driving it. The AUR also adds sooo much, that there is nothing I really don't need to manually install anymore.

For servers, I basically want a rock stable system. Hence why I've chosen Debian Stable.

Als je van beleggen interessant vindt, "Jong Beleggen, De Podcast".

Daarnaast;

• Voordat De Bom Valt (Podcast over de oorlog in Oekraine)
• De Dienst (podcast van de AIVD)
• Tata's ijzeren greep (Over Tata Steel in IJmond en alles wat daar bijhoort).