| ▲ | cookiengineer 4 hours ago |
| Instead of providing a mirrored repository, they decided to intentionally not fixing the correctly identified problem while simultaneously still living 30 years in the past. Setting up a git mirror that auto syncs takes less than 2mins of effort. And way less time than writing up this README that's just there to lecture people. If it's about disagreement with github, there's also better alternatives. You can still setup the mirror and be done with it, and put the original repo links at the top in the README. |
|
| ▲ | st_goliath 3 hours ago | parent | next [-] |
| The upstream has no public repository, neither on GitHub nor anywhere else. JWZ might not even use git in the first place, the source might be in a local SVN repo, or just a series of tarballs and patches, assuming it is version controlled at all. |
| |
| ▲ | cookiengineer an hour ago | parent [-] | | I didn't criticize the motivations to ditch GitHub. I applaud that. I criticized the intentional creation of a GitHub account just to write a README file wherein they say that there's no repository, instead of providing any useful information for people looking for a repository. If there's no repository and you go to such great lengths just to clarify that there isn't any, then maybe you can just push your code to codeberg or gitlab or a selfhosted gogs instance if you don't trust them? Nobody said that he MUST accept pull requests or MUST engage with any community at all. You can just disable all the features, I do that too since 4chan raided my repos in 2021 and GitHub didn't do shit about it. But this way at least there's no risk for people installing malware infiltrated forks of xscreensaver on their machines. And that's what is the important part that wasn't actually solved/avoided/prevented with that README file. | | |
| ▲ | fg137 an hour ago | parent | next [-] | | Having spent (way too much) time on HN, I have come to realize that there are people in this industry -- in fact quite a few of them -- who cares nothing about being nice/cooperative/helpful/pragmatic and getting things done, but just want to show off their ego/opinion and make a statement. Many names come to mind but I am too scared to post that list. | |
| ▲ | amiga386 an hour ago | parent | prev [-] | | The page provides useful information. It tells you where you can download the XScreenSaver source code (from https://www.jwz.org/xscreensaver/), and how you can send patches (via email) It doesn't need to provide anything else. Nobody is required to sign up to your preferred platform, or make their work available in a way you prefer to consume it. Get over yourself. If you want to contribute, contribute as requested. Or don't, the license allows you to host your own version, just be clear it's your version. JWZ went to great lengths on github.com, solely because some other shitheel registered the "xscreensaver" organisation and went out of their way to make it seem like it's official, and github.com's google juice means it outranks the real site. Hence the need for the effort to solve that problem (reputation management and SEO after a copycat misrepresents themselves as you) Putting a repo on Github, versus putting a notice on Github that there's no repo, does not change the risk of people installing malware. While someone else still has the top ranked page for your software, they remain the most likely place a moron in a hurry[0] will download from. You adding a repo doesn't help, you getting their repo removed, and salting it to prevent recreation, does help. [0]: https://en.wikipedia.org/wiki/A_moron_in_a_hurry |
|
|
|
| ▲ | pil0u 4 hours ago | parent | prev | next [-] |
| It's obvious that the author wants to make a statement, and has their own reason to not expose their work on GitHub. Setting up a mirror would probably contradict these reasons. |
| |
|
| ▲ | cxr 3 hours ago | parent | prev | next [-] |
| > You can still setup the mirror and be done with it, and put the original repo links at the top in the README There is no original repo to link to. That's why the README says that there isn't one. > Setting up a git mirror that auto syncs takes less than 2mins Prove it. |
| |
| ▲ | cookiengineer an hour ago | parent [-] | | > Prove it. There's enough demo videos on how to use gogs, github or forgejo on YouTube. I have faith in your ability to use the YouTube search. |
|
|
| ▲ | mykhamill 3 hours ago | parent | prev | next [-] |
| Right now, I would love to live 30 years in the past. |
| |
|
| ▲ | bcvvvy 2 hours ago | parent | prev | next [-] |
| Using a public source code hosting product is a choice. Also centralising everything in one place is a seriously bad idea. |
| |
| ▲ | fg137 an hour ago | parent [-] | | A link to a .tar.gz file published on someone's personal website serving as the only way to access source code also seems a centralized solution. |
|
|
| ▲ | 3 hours ago | parent | prev | next [-] |
| [deleted] |
|
| ▲ | messe 4 hours ago | parent | prev | next [-] |
| > Maybe someone should fork xscreensaver as xscreensaver-ng as a community project? Feel free. |
|
| ▲ | antiloper 3 hours ago | parent | prev | next [-] |
| > they decided to intentionally not fixing the correctly identified problem Which problem? |
|
| ▲ | sick_of_slop 3 hours ago | parent | prev [-] |
| Or they could not. It’s their project they can do what they want you are not entitled to their labour. |
