![](https://popplesburger.hilciferous.nl/pictrs/image/c1ad0046-f2ee-4988-aa2d-533aca036635.jpeg)
![](https://sopuli.xyz/pictrs/image/8167d883-d9f5-4066-8ae7-80e8b3506722.webp)
deleted by creator
Giver of skulls
deleted by creator
You can keep the trademark with FOSS. That’s why Debian had Iceweasel rather than Firefox.
I mean, you can just run Winamp in Wine already.
Linux support will depend on how tightly integrated the application is with the Windows API. It may very well be easier to just keep running in Wine, maybe after patching out some Wine related bugs.
It also depends on the llicense. If they don’t license Winamp and just show off the code, nobody is actually allowed to do anything with it. The title of their announcement uses"source available" so I assume the license is quite restrictive.
Gitlab and a few others are actually working on using ActivityPub for this use case. There’s still a lot of work to do, though, so give it time.
Mint is based on Ubuntu, so the Ubuntu steps should work. I’m not sure what version of Ubuntu the latest version of Mint is based on, though. You can probably find that info somewhere on the Mint website.
The project has build instructions for building your own copy. These are terminal commands.
You may need to install additional software if you get “command not found” errors. If you Google the exact error messages + the name of your distro, you should find out how to install that. The instructions seem comprehensive, though.
deleted by creator
deleted by creator
deleted by creator
deleted by creator
I see, I should’ve been more specific. Apologies for the confusion!
I hate C as much as most programmers, but there are very few low-level networking tools that make me think “I wish this was written in Java”. At least Tor is being rewritten into Rust, so the point will be moot soon enough.
The Java 8 + ant instructions on Github also make me suspect that they’re not using a particularly recent version of Java either. There are even components that seem to be written for Java 6, and Java 7 runtimes seem to be the default target for most operating systems.
I was sort of hoping to see I2P be an early adopter of Project Loom for high performance, but I guess they’re focused more on keeping old and outdated computers compatible.
A lot of those advantages seem very… subjective. Peer-to-peer in itself doesn’t have any advantage, but the comparison seems to be written by someone who thinks it does.
Purely because of the larger user base I would pick Tor over I2P in this scenario but for piracy in general I2P does seem like a much better fit. I do wonder how the situation will change if Veilid ever takes off, though.
I don’t really see the advantage in the context of hosting a Gitlab server for developing pirating tools.
What’s the advantage of I2P over Tor? It’s been a while since I used I2P, but it always seemed like “Tor with more open ports and higher CPU usage” to me.
It’s important to note that if you set up Gitlab over any kind of hidden service, you disable CI/CD systems, because a CI/CD pipeline doing a HTTP call will easily de-anonimyse the server. Set up appropriate firewalls and disable any features you may not want, or you’ll easily find yourself de-anonymised!
deleted by creator
deleted by creator