OneDrive shenanigans, Windows Defender preventing access, the list of
issues goes on.
Existing setups with a DuckStation directory in Documents will continue
to use Documents. New installs will use AppData\Local.
Been paying hundreds of dollars for hosting for the last few years, and
with no immediate plans to push a new Android release, it does not make
sense for me to keep paying for it, especially since I make $0 off
DuckStation.
(it's been non-functional for a few weeks, apparently it took until now
for someone else to notice, which kinda shows how little use it was
getting)
If there's significant demand, then I may re-consider.
Qt's minimum is 13, and I don't particularly feel like debugging issues
created if I work around it for an OS that hasn't been supported in over
a year.
Now they're getting random timeouts updating the SDKs, just tired of it.
The workflow to publish is still in the tree, but I haven't updated
Flathub in months, and it's arguably kinda pointless since the Flatpak
is literally just a wrapper of the AppImage now...
So, still undecided what to do about that. If you are using it, please
let me know, because in the months that it's been deprecated only a
couple of people mentioned that they were using it. Therefore, as best I
can tell there's basically no userbase.
Apparently I forgot to do this when I created it back in Feb...
I can't be bothered to rearchitecture the automatic updater so it
doesn't have the silly 30 tag limit that GitHub imposes on its API
requests by default.
And split it into warnings/messages. Warnings are always displayed
regardless of the "Show OSD Messages" setting, because they're critical
and users forget they disable messages.
Connor McLaughlin