In 2014, MS-DOS 1.25 and 2.0 were released under a Microsoft shared-source license (Microsoft Research License) which forbids redistribution
In 2018, both versions were published to GitHub and relicensed as MIT, making them properly open-source
Today, MS-DOS 4.00 was added to that repo, also under MIT.
A ground-up overhaul of the copyright system would make things so much worse, not better, considering the current climate of power. In the US for example, MPA, RIAA, Entertainment Software Association, Association of American Publishers, and others wouldn’t want public libraries or the used market to exist at all; they would push for making every single transfer of “ownership” on any media involve a payment to the rights holder. Lawmakers are far more likely to accommodate those groups’ desires than the public good.
The worst parts of the current copyright system are the most recent. Both the DMCA and the extension of US copyright term to 95 years took effect in 1998, and the early 2000s saw many other countries passing laws to make their copyright system closer to US’s in various ways such as the WIPO Copyright Treaty which took effect in 2002 and EU’s 2006 Copyright Directive. Just about the only positive news we’ve seen in US copyright law since then is in temporary exemptions to DMCA’s anti-circumvention rules (Section 1201) which change every year. Copyright law was far less hostile to consumers and the public before the 90s than it is now, and up until 1976 it used to be expected that most media someone consumes would enter public domain within their lifetime.
The digital era makes market relevance far more ephemeral than ever and yet the laws written for the digital era moved copyright in the opposite direction. Movie studios simultaneously judge whether a film succeeded almost exclusively based on its first week of ticket sales and also claim that depriving public domain for 95 years is necessary. Nothing should be able to justify more than 20 years of copyright. Media formats don’t even last as long as copyright; CDs and DVDs rot, game cartridges die, servers shut down, and even books printed on today’s low-quality paper will fall apart.
Some of it is absurd to me, like the way something can be online but geographically restricted.
This is a consequence of contract terms moreso than copyright. One issue in copyright law that this does connect to, though, is the fact that the question of whether the rightsholder keeps a work reasonably available on the market does not impact whether the work retains copyright protections. If copyright law did hypothetically include that limitation, providers would become far more likely to make sure that all content is available in all countries, but even then things could still vary in terms of which content is on which platform.
For years I’ve been using KeepassXC on desktop and Keepass2Android on mobile. Rather than sync the kdbx file between my devices, I have each device access it through the network. Either via sftp, smb, or nfs, but regardless I need to connect to my home’s VPN to access it when away from home since I don’t directly expose those things to the outside world.
I used to also keep a second copy of the website-tied passwords in Firefox Sync, but recently tried migrating that to Proton Pass because I thought the PIN feature might help, then ultimately decided to move away from that too and start using the KeepassXC-Browser plugin instead. I considered Bitwarden too but haven’t tried it out yet, was somewhat deterred by seeing people say its UI seems very outdated.
Yes.
My home server has dropbear-initramfs installed so that after reboot I can access the LUKS decryption prompt over SSH. The one LUKS partition contains a btrfs filesystem with both rootfs and home as subvolumes. For all the other drives attached to that system, I use ZFS native encryption with a dataset that decrypts with a keyfile from that rootfs and I have backups of an encrypted copy of that keyfile.
I don’t think there’s a substantial performance impact but I’ve never bothered benchmarking.
Thanks for the recommendation. I’ll give it a try sometime.
Stylus/handwriting oriented note taking. Stuff like Samsung Notes or Goodnotes (or OneNote, though it does a lot more) in the Android space, or e-ink options like Remarkable’s stock software.
If I just want to use a keyboard for everything I have great FOSS options like Joplin and Standard Notes, but when I want to use a pen instead it feels like no other freedom-respecting option seem to even remotely approach the usability of just sticking with real ink and moleskine-like paper notebooks.
Even someone willing to pay an upfront fee for proprietary apps will struggle to find good options that allow syncing and reading (let alone editing) your notes on other devices/platforms without resorting to a monthly subscription.
Something I’ve noticed that is somewhat related but tangential to your problem: The result I’ve always gotten from using compose files is that container names and volume names get assigned names that contain a shared prefix by default. I don’t use docker and instead prefer podman but I would expect both to behave the same on this front. For example, when I have a file at nextcloud/compose.yml that looks like this:
volumes:
nextcloud:
db:
services:
db:
image: docker.io/mariadb:10.6
...
app:
image: docker.io/nextcloud
...
I end up with volumes named nextcloud_nextcloud and nextcloud_db, with containers named nextcloud_db and nextcloud_app, as long as neither of those services overrides this behavior by specifying a container_name. I believe this prefix probably comes from the file-level name: if there is one and the parent directory’s name otherwise.
The reasons I adjust my own compose files to be different from the image maintainer’s recommendation include: to accommodate the differences between podman and docker, avoiding conflicts between the exported listen ports, any host filesystem paths I want to mount in the container, and my own preferences. The only conflict I’ve had with other containers there is the exported port. zigbee2mqtt, nextcloud, and freshrss all suggest using port 8080 so I had to change at least two of them in order to run all three.
On Switch, no game cards support writing of save data or anything else. It’s a departure from 3DS and all previous Nintendo cart formats for as long as games have supported saving at all.
That change is probably done to help tie saves to user accounts, enable cloud saves even when the card is not inserted, accommodate variable-size user data features like level creation, and mitigate the risk of game save based exploits like Twilight Hack spreading from user to user.
Unfortunately that (plus inability to put saves on SD card) means that backing up your own save data requires either being able to run homebrew on the system that has the save or having another Switch that can and relying on Nintendo servers to perform the transfer. Either way, having a Switch that runs homebrew means you don’t need this dumper.
The readme file, gitmodules file, and other links within that repo all still reference the now-dead gitlab links. The builds don’t seem to be present at all.
That will all probably be fixed soon enough but right now that mirror which seems to have just been pushed as-is isn’t entirely usable.
That’s actually a choice you’re offered during Debian’s interactive install. When you’re offered the option to set a root password, if you leave it empty the system will disable direct root login and instead give your first normal user sudo access.
Debian. I was in a similar boat to OP and just a couple weeks ago migrated my almost 8-year-old home server setup from Ubuntu LTS to Debian Stable. Decided to finally move away from Ubuntu because I never cared for snap (had to keep removing it with every upgrade) and gradually gained a few smaller issues with Ubuntu. Seems good to me so far.
I considered RHEL/Rocky but decided against them largely because I wanted btrfs for my rootfs, which their stock kernel doesn’t have, though I use a few Red Hat developed tools like podman and cockpit. Fedora Server and the like have too fast a release lifecycle for my liking, though I use Fedora for my desktop. That left Debian as the one remaining obvious choice.
I also briefly considered throwing a Debian VM into TrueNAS Scale, since I also use this system as a ZFS NAS, but setting that up felt like I was fighting against the “appliance” nature of what TrueNAS tries to be.
The main reason people use Fandom in the first place is the free hosting. Whether you use MediaWiki or any other wiki software, paying for the server resources to host your own instance and taking the time to manage it is still a tall hurdle for many communities. There already are plenty of MediaWiki instances for specific interests that aren’t affected by Fandom’s problems.
Even so, federation tends to foster a culture of more self-hosting and less centralization, encouraging more people who have the means to host to do so, though I’m not sure how applicable that effect would be to wikis.
There’s one more repo worth archiving that isn’t included in this, was taken down at the same time as the others, is needed to build yuzu, and is a submodule in yuzu, yuzu-android, and yuzu-mainline: https://github.com/merryhime/dynarmic.git
I found one copy of it at https://github.com/ihaveamac/dynarmic
Most other submodules are from huge projects with no real risk of vanishing (mozilla, khronos, libusb, etc.), but a few others that might be worth noting (all still online in github) include: merryhime/oaknut, bylaws/libadrenotools, and lat9nq/tzdb_to_nx
I just uploaded a mirror of the wiki to https://codeberg.org/zarenki/yuzu-wiki/src/branch/master/Building-for-Linux.md
Downloaded it a week ago, so might not be the most recent change.
Not OP, but the one thing that bugs me most is that Firefox Android does not have a tablet UI. Other browsers like Chrome have a tab bar and other desktop-like UI features when run on Android tablets.
But on phone I’ve never run into a case of wanting a feature that it lacks.
Ethically, I agree with you. More than that, using a lockpick on a lock you bought shouldn’t make you a thief. Unfortunately, DMCA has abysmal anti-circumvention measures that make the legality of using a device you own in ways you should be able to become questionable under US law, in the digital equivalent of Master Lock suing you for picking a lock you bought from them.
instructing users how to extract the prod.keys from their own switch
Yuzu’s quick start guide links to the old download link for Lockpick RCM from the same repo that is still inaccessible ever since Nintendo’s DMCA takedown last year (source: arstechnica). They never updated the page to link to any mirrors of Lockpick RCM or any other options to extract the keys; the guide doesn’t even work right now. You can see in Yuzu site’s changelog on github that the only changes made to that page in the last year are to minimum/recommended hardware requirements.
It seems even more absurd to argue that instructions are somehow infringing when the allegedly infringing part of them has already been broken for almost a year. Even the standing for taking down Lockpick RCM in the first place seems questionable, and telling users to use it with a broken link seems several layers further detached from that.
If you’re assuming “as long as the hardware will function” in the first place: even digital copies, DLC, and updates installed on the system before the servers shutdown will continue working even without hacks. There’s no check-in requirement except for the subscription-locked things like SNES games.
However, the result of a nonrepairable hardware failure when you have no hacks nor official servers is rather bad no matter how your games are obtained: OFW does not allow you to transfer save data from one system to another without going through Nintendo servers and a vast majority of cartridge games are incomplete without updates or DLC.
I never liked to play DS games on 3DS because of the blurry screen: DS games run at a 256x192 resolution while the 3DS screens stretch that out to 320x240. Non integer factor scaling at such low resolutions is incredibly noticeable.
DSi (and XL) similarly can be softmodded with nothing but an SD card, though using a DS Lite instead with a flashcart can enable GBA-Slot features in certain DS games including Pokemon.
There actually is a silent and very subtle revision they made to the dpad less than a year after Switch launched (iirc around the time of the Xenoblade 2 controller). The protrusion out the middle of the underside was made slightly longer, which makes you less able to push down all four directions at the same time. The chance of undesired diagonals is very high either way but just slightly lower for the newer one.
Even the improved version is one of Nintendo’s worst dpads ever (including handhelds) imo, with only the GameCube’s coming remotely close. A huge step back from Wii U Pro’s dpad.