• 0 Posts
  • 5 Comments
Joined 3 years ago
cake
Cake day: July 2nd, 2023

help-circle
  • There is no clean room implementation of a discrete title that would not run afoul of Western copyright and trademark law. If you want to release Super Mario 64, as it was made, you will not have a free license to do so until it enters the public domain. You can release Supra Wario 63, with all it’s not quite the same assets, and argue that you can get away with it. The value of these projects is not the licensing.

    Now, worse? This scenario would actually be improved if the AI were to do the whole implementation? Because it would apply a FOSS license where a human could not? This is nonsensical.





  • Headscale, for one. This is probably implied as part of one of your above stacks, but let’s list it out loud. Tailscale is great and all, but it’s downright icky to offload routing of any variety to a third party.

    Immich. Turn off Apple or Google’s automatic scraping of all photos, keep usability. Even if you’re not a photo person, at least some of your users are.

    Syncthing is or Nextcloud, or something in the family. This may already be part of your NAS plans.

    One of the code forges like forgejo, gitea, gitlab. Even when not a developer. Self hosting involves configuration and if you can get that into text and into a history, it makes things so much easier. Add bells and whistles to your hearts content, but these are good suites for a lot of functionality. Forgejo does have federation on its road map, but it’s a while off still.

    These are ones I find pretty ubiquitous. There’s so many options once you have initial infrastructure. Email, for instance, isn’t as daunting as the horror stories make it sound, though not as simple as many hope. My suggestion is to take time and do it correctly. There’s a lot of backtracking involved as you learn more, but it’s usually worth it. Best of luck!