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.
The speculation is wrong.
If your hobby is making Paper Maché Owls, and one day Hobby Lobby calls you and threatens to sue you in criminal court for millions, or you can silently stop your hobby?
Unless you have millions to burn, you give up your hobby, because it’s not worth ruining your life over.
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
Replacing native Winamp code with modern code with frequent updates by one of the most prolific classic Winamp developers.
It’s fantastic.
High speed rail.
It’s insane Amtrak is the best we got. You should be able to go from Orlando to New York in hours, cheaply.
Google has also made unwelcome moves recently indicating they might crack down on sodeloaded app stores. So I’m glad this ruling happened.
Well they have structured the Remaster as a DLC upgrade that requires the base game license.
So they would have to delist their new listing and create an entirely new release.
Honestly 99% chance they did it this way to preserve the review history of the original game on the Remaster.
But it is, as a bundle.
They’re having one HZD listing, for both copies If you buy it in 6 months you can still play the original release with no PSN and no remake changes, they just package the remake with it now on the store.
This is not true in the literal sense.
You cannot redeem HZD keys, and buy it as part of a bundle with both versions. They stopped selling it standalone.
So you can get the upgrade for $10 if you already have it, or wait for a sale on the bundle.
But in either case you can still play the original release without the PSN requirement even if bought after the remaster release.
If you start the project intending to be untracable, yes.
Most software devs aren’t thinking of that. These things with emulators often start as a hobby.
In this age with PIs and lawyers, it can often be found, and emudevs probably don’t start thinking they will be facing down a giant corpo over a hobby project.
Oh well then it’s good then that the software doesn’t have keyfiles in it, and plays unsigned and self-signed homebrew and switch software just fine.
See: Kaizo Mario directly inspiring Mario Maker.
See: LttP Randomizer, along with literally any other randomizer.
See: speedrunning streams literally making the market that Nintendo then sold the Nintendo World Championships cart into.
Nintendo absolutely benefits from this. They just want to crack the whip and take over. Fuck them.
Also, still can’t buy Mother 3. Double fuck them. Tons of titles play better on emulation. I shouldn’t have to justify it.
They gave out keyfiles? Is that what you are saying?
Ryujinx does not include DRM circumvention.
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.