Okay, yes. To me, open core is not open source, and a company dropping a free 'community version' but not taking patches for that one nor even providing a basic version of support might as well just do shareware instead.
I don't think the expectation of free support is valid. If someone asks for support on a public forum, I help them if and when I have time or let someone else handle it when not. If someone sends me private email, I send information on the public forum as well as a quote for paid private support.
Nobody should feel forced to do anything just because they happen to do open source.
Copying software costs nothing. Yes, writing software does. But to charge 100s of $CURRENCY for something you copy millions of times? Yuck.
I mean it's not a coincidence that most of today's billionaires made their money doing software.
@amin @rl_dane @ivanmarkov @clayton @orbitalmartian @kabel42
@rl_dane @ivanmarkov @pixx @clayton @orbitalmartian @kabel42
Hot take, "Rewrite in Rust" bros are to FOSS what a well-thrown bowling ball is to a game of Jenga.
Vaccines work *because* they don't kill you, and therefore make you stronger...?
I was recently reminded of this.
A couple decades ago, I wrote a short paper that described how the basic approaches of cryptography and computer security lead to an efficient and practical privilege escalation attack against master-keyed mechanical locks, which I published in IEEE Security and Privacy (a nerdy computing technical journal).
https://www.mattblaze.org/papers/mk.pdf
TL;dr: Master-keyed locks have fundamental, exploitable weaknesses.
But I wasn't ready for what happened next.
1/
It was pointed out to me that this post is now quoted on their website, and misinterpreted at that. Roy, since I know you're following this thread: No, I did not say that you deserve to be harassed. Nobody does. When I said "you deserved it", that referred to your continued false accusations in the face of evidence to the contrary.
Also, sorry to spoil your thunder, but quoting Daniel Pocock is not the flex you think it is.
You are not wrong. Part of this is because Keith Packard spent a few years at Intel teaching corporate structures how you upstream a driver for Linux into X11 (at the time) and Mesa:
https://keithp.com/keithp/resume/
@ariadne @agowa338
The internet was not a mistake
Social media was not a mistake
Allowing Corporations to dictate and control both of these things was the mistake.
(1/7) I suppose #Fediverse isn't the place people are discussing #RobReiner. But after 36 hours of deliberating whether to say anything, I feel compelled. This thread will be long,but I start w/ most important part:
It's an “open secret” in the #FOSS community that in March 2017 my brother murdered our mother. About 3k ppl/year in USA have this experience, so it's a statistical reality that someone else in FOSS experienced similar. If so, you're welcome in my PMs to discuss if you need support…
(It's called 'AIStor' these days, presumably to be buzzword compatible 🙄 but it's really an S3 thing, SDK at https://www.min.io/download/aistor-sdk
I mean yes if you're going to be serious about building a binary repository then higher-level tools like reprepro to track packages and their versions in different suites so that you get auto cleanup of old versions and easy metadata signatures are definitely useful, but they're absolutely not required.
@SRAZKVT @dalias @draeath @ska
A deb/rpm repository isn't much more than that. You dump packages in a directory and run a single command to extract the metadata into an index file. 'createrepo' or its C reimplementation for rpm, 'dpkg-scanpackages' for deb. That's all that's *required*. You then export said directory over http or mount it and you can install these packages with all the dependency tracking.
@dalias @draeath @ska @SRAZKVT