Nope, I use Mega
Nope, I use Mega
I backup stuff both on a MicroSD and on web storage with duplicity
. Hopefully that is enough!
passwords.txt
on a full-disk encryption HDD.
I don’t mind moderators having their ideas or even ranting or even blowing off some steam in the thread they make/parecipate in.
Their moderating job is to avoid the community being drowned in spam/scam etc. and as far as I can see there are few to no spam posts in !opensource@lemmy.ml. In that particular thread they went wild but as far as I can see did not abuse their mod powers.
tl;dr: judge the moderator as the moderator, and the user as a user. I didn’t particularly like that thread too, but from moderating POV, I haven’t yet seem something by haui I disagree with.
I am happier when I see copyleft but let’s be honest, I would contribute to an interesting, useful project regardless of their choice between MIT and GPL. Same for companies: some prefer MIT, but there is no way they are not going to contribute to the Linux Kernel just because of copyleft. So bottom line is: make something that people enjoy/find useful and see contributors flocking.
CLAs are a different matter: I do not contribute to projects which ask you to assign them copyright unless I 100% trust the organisation behind them.
If some code links to your GPL library, the whole project has to be licenced GPLv3, full stop. This does not “prevent people to use [it] at all”, it just stipulates that they have to make the source available and the source of improvements they make available. Each substantial library I write in my free time is GPLv3. I want to contribute to the ecosystem and I want everyone enjoying my work contributing back to the ecosystem.
A similar licence, called LGPL, allows dynamic linking without having to make the code of the whole project available, just the code of the specific library + improvements. If for some reason you need this, I invite you to check how dynamic linking works in Pharo and read this FAQ by the FSF (and all other FAQs, it is a very clear, informative document).
File an issue in their repos, sometimes people (understandably) do not understand licencing very well — or it might be they were granted an exception.
If that fails you can contact the library author and the repositories who host the code.
Great suggestions in this discussion! Rather than adding my favourites, I will add some resources that list more games.
I hope to come off as harsh, but documentation quality is an important factor for both discoverability and adoption.
At least there are instructions — which I haven’t tried yet — on how to build the app.
An excellent client and backgammon experience.
Thanks Trevor for documenting your path, it is quite useful to us all who might want in the future to write an open source multiplayer game.