mirror of
https://github.com/awesome-selfhosted/awesome-selfhosted.git
synced 2026-03-09 11:43:52 -05:00
Hastebin has been abandoned. Please direct people to the updated fork #4388
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/awesome-selfhosted#4388
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @twiclo on GitHub (Sep 15, 2020).
seejohnrun/haste-server has been abandoned and it looks to me like https://github.com/zneix/haste-server is the best fork out there. Could we maybe update the list to direct people to this updated repo?
@nodiscc commented on GitHub (Sep 19, 2020):
The forks looks to have some recent maintenance yes, however the original has some long-standing issues (https://github.com/seejohnrun/haste-server/issues) and some (apparently) security-related ones. So the original has the advantage of making them visible to the prospective user...
seejohnrun/haste-server should definitely be removed in the current state. However I don't know about the fork... @twiclo @zneix what do you think about these solutions? Either:
@zneix commented on GitHub (Sep 19, 2020):
Hey @nodiscc, I started modifying haste just to resolve numerous dependency issues but I noticed I can upgrade its very old code and I still have some ideas in my mind to expand original repo by adding, for example deletion support or rewriting frontend to get rid of old jquery.
I don't have all the time in the world, but I intend to keep providing support to my fork and adding features I have in my mind.
I will try contacting seejohnrun, but I have a feeling I can't just take someone's repo and pin it under my name.
About copying issues, I can make one megathread of most/all relevant issues that might be useful to implement and start working on them.
@twiclo commented on GitHub (Sep 19, 2020):
https://twitter.com/ALazyMeme/status/1298257725143437320
@ALazyMeme commented on GitHub (Sep 20, 2020):
More than happy to help out moving all the issues over. Don't see why a deprecated repo should be promoted that has security vulnerabilities and people waiting to contribute to contribute that are being ignored.
Poor form imo - even if I don't hold a github employee to a higher standard.
I wouldn't give a toss about the original project. The original owner evidently doesn't care enough to respond - probably won't want to transfer the repo.
@twiclo commented on GitHub (Sep 20, 2020):
I believe @zneix fixed the security flaws already
@zneix commented on GitHub (Sep 20, 2020):
Yes I did, I believe alazymeme meant upstream repo, not my fork 😄
@nodiscc commented on GitHub (Oct 4, 2020):
No response from @seejohnrun? If so, you may send a PR to replace the original hastebin with your fork