Hacker News Reader

Comment by djha-skin | Hacker News Reader

Requiring six months of reasonable activity before handing over the reins is a neat and novel way to ensure the new maintainer doesn't have crypto mining bot nets in mind :)

View on HN

Yes, definitely reasonable.

However, I wondered about how much activity there still is on this. Isn't this considered mostly finished at some point?

I can understand that there might be some more development on libfuse but that is independent anyway. As far as I remember, the MacOS state of libfuse was somewhat unclear?

There’s no need to use libfuse on macOS. You can use https://mountainduck.io/ instead or write a FileProvider for Finder (macOS) / Files (iOS / iPadOS) https://developer.apple.com/videos/play/wwdc2021/10182/

A really good example of File Provider API is the Secure ShellFish app on iOS / iPadOS - https://secureshellfish.app .

> Isn't this considered mostly finished at some point?

I consider it buggy and unusable. At least on Mac. Definitely not finished.

I gave up on it and switched to using VSCode's remote development extension.

Has been working fine for me for years on Linux. I wish it had some convenience features like automatic reconnect, but other than that it's fine. Just don't expect any performance miracles compared to NFS or cifs.

It has automatic reconnect: "-o reconnect". You'll need to use key-based authentication with an SSH agent, since it won't be able to prompt you for the password while running in the background.

Hey that's awesome thaks! Seems to have been there for decades. How could I miss this?

That might mean it needs better surfacing in the docs, if you have the time it may be worth having a quick look at the docs - it's possible a PR could help aid discoverability.

That seems impossible until a new maintainer is found. The current issue tracker however contains an issue that suggests making automatic reconnects the default. I hope I remember this when eventually (hopefully) this project is picked up by someone else.

Similar results for me too, also on a Mac. I've had it basically work a few times in trial runs, and it's pretty convenient (the concept is excellent), but it has been horrifically slow and flaky basically every time (e.g. takes upwards of a minute to list a directory with like 100 items in it, sometimes just silently gives up and doesn't list anything, etc). I'm not really sure why.

Weird, I've been using it for like 10 years maybe? No issue on Linux and OSX, aside from the occasional disconnect, which is actually my ISP's fault.

Yeah, I saw that as well, and I was immediately struck by how reasonable and responsible that seemed.

Not ideal if you're a Linux distribution trying to figure out which fork to pick up, but ideal if you're an upstream maintainer trying to find someone responsible.

I hope that works out, more often than not, if there's no official new maintainer, distros keep doing what they do best: not talk to each other and over the years start to collect different patches for the same issues that might pop up eventually. :-(

Reply on news.ycombinator.com