[fragmede]

It's sad that you don't have Internet friends that you trust enough to share that with after writing all that code. Maybe open source it but don't link to your demo instance? It's more sad that the Internet is like that. There are a couple of really neat quirky projects out there that I only know about through word of mouth because the open Internet is not to be trusted. The projects are behind a login wall, so it's not like they're discoverable either.

[alias_neo]

The name of the project is its domain so I'd have to separate them out, which is why I've kept the demo site online for years now, despite basically no usage, I'm also a big fan of being able to try something before you go through the effort of deploying it yourself.

The project is already open-source on Github, but I don't actively link to it in public forums because I don't want to have to deal with it being used for questionable/illegal content, which is also the reason I haven't added some of the features I'd like to, and severely limited the size and duration for the demo site.

It's been a nice toy project, I added multiple architectures support for the Docker image builds when I was working out how to do that, manifests to deploy it in Kubernetes when I was first learning that and even made it a Nix flake when I first started playing with NixOS; The code itself is written in Go with a goal of using zero external (outside of standard library) dependencies, keeping the code small and clean for non-programmers to be able to understand and uses some Go features that were new/interesting to me at the time they were added.

It'd need to grow a lot and forgo some of those goals for me to add the features I would like to see, but for something nobody will use, and I use quite sparingly myself, there's no need.