I think because Syncthing isn’t really for “sharing” files. It can move large files across the internet but it’s not designed for “hey send me a copy of that blu-ray your ripped” sharing.
As @Caboose12000 already said, I’d recommend drop.lol (can be selfhosted). Filetransfers are direct between peers (unless you’re behind some hardcore NAS where UDP hole-punching via STUN is not possible).
I mean how I transfer a file depends on the situation. If it’s to someone on XMPP I’d just establish a direct transfer there. Sometimes I share a directory over HTTP, FTP, SFTP and so on. The easiest way for most people, because it only requires a WebRTC capable browser, is with one of the many peer to peer filesharing platforms like drop.lol.
I never see toffeeshare mentioned. P2P, encrypted, no size limit. Only problem is you can’t send folders, only files, but that’s easily solved with tarballs or RARs.
Why are everyone suddenly aware that Neochat is unmaintained. I mean, the last commit was 3 years ago and the last release alsmost 4 years ago. Just because the git repository got archived on a date does not mean that it was maintained up to that point.
Most people aren’t going around checking the commit history on every piece of software they use. The git repository being archived made the Linux news rounds, so now a bunch of people are newly aware. It’s not complicated.
I don’t get people being worried about an offline application designed to run one shot as the current user not receiving updates. I do get maintainers dropping the package from package repos now that it is officially archived though…
Yeah, but if it hasn’t reached that point then is it really dead?
Edit: Instead of downvoting me, consider this. What if the only update this program receives in years is one to make sure its still compatible with the libraries and APIs you refer to? Would that make it alive, or dead?
It seems like you guys are advocating for updating just for the sake of updating, also bandwagoning a bit.
Neofetch is literally a bash script. There aren’t any libraries or APIs it depends on, and there is basically no chance of it not working in the future. Some people just like to try and sound smart.
The actual problem with Neofetch is that it’s not being updated with new ASCII art for new distros, and not adding new options to show things like a line for display server or other things some people might be interested in. It’s just getting out of date in regular boring ways.
Uh huh. You think that some cloud computing processor just randomly can’t run a bash script? What, does the uname command not work on their processors or something? That would cause problems a lot worse than just Neofetch not working. I obviously don’t have one laying around to check, but I find that highly unlikely.
itsfoss.com
Active