fossham

@sync_in@mastodon.social How is this different from Nextcloud?

@grimmware@chaos.social No idea. I don't use the internet for childish popularity contests. I use it instead to build resources, gather information, and make decisions for the projects and communities I support. I use the methods of science, the best practices within development and cybersecurity industries, and philosophies of FOSS to arrive at working solutions. I leave the popularity metrics up to those who can't join me in more practical conversation.

@grimmware@chaos.social Your logical fallacy is "straw man argument." I just said that I use the methods of science, the best practices within development and cybersecurity industries, and philosophies of FOSS to arrive at working solutions. Those working solutions include building teams of people who share *those* values, not those who air their emotional fragility in public. If you think all disagreement is "confrontational," you're likely to end up wasting time talking about tone instead of content.

@red@woof.tech Was there a value-add to duplicating all of Debian's installer/packagerepo/rapid cybersecurity response efforts to create a forked distribution, rather than simply using Debian's existing infrastructure and contributing the latest ham software to Debian? I think a lot of Linux users would rather *not* trust yet-another hobbyist-level distribution, and would prefer simply to see well-maintained and cutting-edge packages for JS8Call, FreeDV, CHIRP, QDMR, etc. in Debian proper instead.

@red@woof.tech I'm afraid this communication doesn't answer the question, "why fork?" Why not simply use Debian + custom repo (or even just Sid/Testing repos), to ensure we're benefiting directly from Debian's time-proven infrastructure and processes? Debian users already have flatpak and appimages for cutting edge, but it would be better to incorporate ham software quickly into Debian while complying with Debian review and security processes. So give it another try: "Why fork?" What's the benefit?

@red@woof.tech In the 21st century, Linux users know that security response is priority: distros like Debian and Fedora have huge communities so there are always developer eyeballs and capability, despite national holidays, vacations, illnesses. 0-days are more likely to be fixed in such a large team. One-off forks have proven to be single points of failure. If you'd like to be the exception to that rule, be more clear about the 95% Debian / 5% you, and what your cybersecurity plan is for that 5%. 2/2

@red@woof.tech One thing that would make that process easier would be if you were to provide a list of which packages comprise the 95% that is available in Debian already, and which 5% are unique to your fork. Debian kindly provides such lists on https://www.debian.org/blends/ , so we can check which versions are available, which are lagging behind, and see what's missing. I would have enjoyed seeing something like its "hamradio" and "metapackages" links on your website.