6 ms·
First of all, sorry to hear that WiringPi is deprecated, and I would like to thank the author for all the effort he put into this project. When I read his blog
by guardiangod 7y ago
First of all, sorry to hear that WiringPi is deprecated, and I would like to thank the author for all the effort he put into this project.
When I read his blog post on his reasoning, I can't help but be reminded of the feud between xscreensaver's author and Debian maintainers. Debian maintainers refused to upgrade the app's version and refused to remove the 'For support contact the author's email' notice. The author's fed up with all the support emails he gets from Debian (outdated) installations' users and put in a message prompt blasting Debian. It was very ugly for both sides.
I think that there can be an extension on GPL that says, if you bundle this library and is not using the latest official version from the author, you are not allowed to include the author's contact information. If you insist on bundling the author's email with your outdated software, then you are in violation of GPL.
As for people stealing his code. Sorry to hear this. I got nothing except to try to contact EFF.
- dogecoinbase 7y agoI can't help but be reminded of the feud between xscreensaver's author and Debian maintainers. For the curious, the post: https://www.jwz.org/blog/2016/04/i-would-like-debian-to-stop-shipping-xscreensaver/ https://www.jwz.org/blog/2016/04/i-would-like-debian-to-stop... And the instigatory thread: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=819703 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=819703
- CDSlice 7y agoCareful, that first link redirects you to a NSFW image coming from HN
- steve19 7y agoBecause jwz appears to have a very short fuse and at one point in time one or a group of users on HN didn't agree with him (as best as I can remember), referrals from HN are redirected to an image of a testicle. Here is a wayback machine link to avoid the image: http://web.archive.org/web/20190810115358/https://www.jwz.org/blog/2016/04/i-would-like-debian-to-stop-shipping-xscreensaver/ http://web.archive.org/web/20190810115358/https://www.jwz.or...
- jandrese 7y agoJWZ has always been opinionated. I remember his epic rants on email client backends and other technical details.
- Chlorus 7y agolol he's escalated; before he just had text complaining about brogrammers at HN. I've wondered for years what the original beef was.
- NikkiA 7y ago> an image of a testical. It's a 'hairy egg', if you see a testicle that's on you.
- Dylan16807 7y agoWhat compels you to blatantly lie here?
- IntelMiner 7y agoThe intent is pretty blatant
- dtech 7y agoWow, if you pull shit like that that immediately is 1 point for the other team in whatever beef he had
- DanBC 7y agoLinks on HN were generating huge amounts of negative traffic. I don't blame him for having a redirect.
- aidenn0 7y agoI never understood what the big deal is about the warning on the lockscreen. I've seen that before and it didn't bother me.
- stjohnswarts 7y agoYeah but this guy handled it respectfully. He's even releasing a final version. So people can fork it and do what they will. You can't really blame him. 10 years is a long time to maintain something anyway.
- zucker42 7y agoThe FSF might also be able and willing to assist with LGPL violations. Unfortunately though this may be a case with circumstantial evidence but no proof. It also often seems that the people who most willing to disregard the (L)GPL are the ones most militantly protective of their proprietary code. It's quite sad that many developers seem to think that way. Adding an extension like that to the GPL may be problematic because it has a clause that allows users to ignore restrictive extensions (as opposed to permissive extensions).
- m463 7y agoI can't help but think maybe: author-project-v3@example.com author-project-2017@example.com