@unofficial_kbin_guide for the most part we can actually copy and paste this guide to the official wiki page we have. 😉
I’m a #OpenSource #Software #DevOps #Engineer 👋.
Software Developer & DevOps Engineer. Also a /kbin developer. nobot
♥ #Opensource
♥ #Decentralizing the Internet (https://Libreweb.org)
♥ Kbin (https://kbin.melroy.org)
♥ Crypto #cardano, #bitcoincash (BCH)
♥ Inline-skating, nature, photography, the stars
♥ My two kittens cats and of course @Dennis 😘🏳️🌈
I follow back (most likely)!
bitcoincash:qzqmakefvntudp0fv7sunt5fjxdswlxv2yhezq7pdl
@unofficial_kbin_guide for the most part we can actually copy and paste this guide to the official wiki page we have. 😉
@ernest @20gramsWrench outside isn’t gentle at all. It’s cold, windy and rainy.
@Hairyblue not advising Lemmy. And here is why: https://mstdn.social/@feditips/106835057054633379
@cnk so. That is a long story. They want to be legal under the term of ‘fair use’. And want to protect history of books, software, web and alike. They lost lawsuits over ebooks. It’s a big problem I think. Sure copyright is to protect the writer or producer. But at the same time we can’t just lose all the data from the past if we aren’t allowed to archive it?!?
I’m no expert in the law, but I hope we can archive old software and digitalize other content in a legal manner.
@cnk I upload my collection to archive.org
@ernest @unofficial_kbin_guide I think a dedicated website like this kbin guide is indeed the way to go. Codeberg wiki is limited in several ways. Making this guide somehow part of an official project / documentation would be great. @unofficial_kbin_guide You agree?