ocassionallyaduck

For low res, no.

Hi res, sure. Make it optional, or let players download the region they like. Or just the airports with much lower res landscapes, etc etc.

Or just, let them have it all and make these choices. Memory is CHEAP nowadays. If you're a flight sim enthusiast, a few terabytes for the map data is the least expensive part of your setup by far.

They need to make sharing controller presets easier. Like MASSIVELY easier.

I cannot emphasize this enough. Let users send controller profiles and attach them to forum posts, etc.

This is needed desperately because navigating presets is straight up busted. Currently it just promotes whatever has the most users, which is whoever published first.

Doesn't matter if there is an objectively brilliant control scheme for Resident Evil 5 or something, nope, you're using the first layout published by GoonerMaster69 in 2014 or whatever.

Both these factors make using the steam controller a chore. It's incredibly powerful, but setup is a fucking CHORE. I love it, but making it work well is always me tweaking for way too long, or using g the suboptimal poorly named presets at the top of the list.

The RE5 example is real. RE5 is amazing with the steam controller if you have a trigger full pull mode shift to mouse input so you can have perfect accuracy with no acceleration. But try finding this in the preset list.

God I love having a future where my ability to play a fucking flight simulator depends on both internet access and server reliability.

Completely unnecessary to boot. Store a low res copy locally, offer the high res as regional packs. 0 reason to stream this data in.

Kadokawa is a massive publisher of books and media in Japan.

For that reason alone I hope this is blocked. It would make Sony too huge in Japan to reasonably compete with outside of Shueisha and directly incentivize brand exclusivity deals.

An online database is still a file ultimately. A SQL or other DB file stored in a webserver, accessed through a web interface.

Vaultwarden, etc, are the same, only the database file is less directly visible IMO. Keepass IMO is simple. The DB in a bespoke format, stored outside the application.

You could put the vault in system32 and name it "trustedinstaller.log", and if someone saw you had keepass they wouldn't even know where your vault is.

Given the number of well documented breaches of online password vaults, I would much rather do a private device to device sync via syncthing and keep it out of webservers.

Syncthing is encrypted transfers.

The database is encrypted.

And you can set it to not use relays for data, only matchmaking between your own devices.

So it's an encrypted file, encrypted again, and sent directly from an IP you own to an IP you own.

F-Droid syncthing-fork is still actively developed and had a patch in the last few weeks.

So hopefully this isn't the end.

F-Droid syncthing-fork is still actively developed and had a patch in the last few weeks.

Keepass vault synced over syncthing.

I keep not regretting it.

He defines that as wanting to be in control of the project so long as he has the passion to work on it solo. But it's somewhat implied that if he had to let it go, he may open source his work. I can understand that. DrO was one of the primary and most prolific Winamp plugin devs back in it's heyday as well. So if you ever used Winamp itself (closed source) you have already trusted his code on much more vulnerable OSes, imo.

I feel like he's earned the limited trust this requires.

Well, given the very unorthodox nature of it as it is today, I don't know that Dr0 can legally open source it until he's finished replacing literally all legacy functions with new code, even if they wanted to. But I can understand your position.

WACUP

https://getwacup.com/

Replacing native Winamp code with modern code with frequent updates by one of the most prolific classic Winamp developers.

It's fantastic.