Nextcloud VS Samba

While considering alternatives, I thought about DokuWiki, which looks like an unlikely solution, and Nextcloud, which I've already used in the past. Both seem a good option in their own right, though I favor Nextcloud because it's a more direct approach. However, I'm inclined towards a solution that's leaner and less bloated. Nevertheless, if any of those is the one that is most likely to solve my dilemma, I'm open towards using any of those two. I'm also investigating Anytype.io, which seems like the best option, but it seems it works with an invitation.

I can suggest 3 options. * Photoview - It is like a gallery with recursive folder structure (folders inside folders) support. You can create shareable links for the folders, with password protection. The UI is great. And your clients will be able to download the complete folder, also individual images at either full resolution or reduced. The issue is you cannot use the UI to add or delete photos, but it can be a great thing for security and stability. * Chevereto - It is more like imgur. You upload all the files using the UI and create albums and their sharable links. I do not think if it supports videos at all. * Nextcloud - Another great option if you want to give your clients a Google Drive or a Dropbox like experience. You can create custom links, like example .com/client-name, which can look more professional. For better videos experience you'll need hardware acceleration.

Nextcloud Dev (version 20230505): Synchronization client

The core package is offered as pre-compiled binary through Ports packages system. In addition, important softwares such as extensions, Composer and PECL libraries are available. So are frameworks such as NextCloud and Zabbix.

NextCloud > Google Drive

I think something like Nextcloud might suit your use case.

Thanks to this article I learned about Nextcloud[0], which at first glance looks like a really nice self-hostable alternative to the Google Suite.

[0]https://nextcloud.com

Nextcloud Dev (version 20230427): Synchronization client

I have tried A LOT of solutions and I finally stopped after using Nextcloud and Photoview. I synchronise files from my computer to Nextcloud using rclone and view them on Photoview whenever I need. You can sync to you nextcloud using their official app on phone. I use Photoview because I have not found a single self-hosted solution that keeps the folder structure and lets me view them as both, in folder structures as well as in a chronological timeline.

You could try to use samba via cgo.

> First, the article doesn't say that "Linux is not ready for the desktop" - or concern itself with this as an abstract question.

Well, it does, but in a sarcastic manner:

"Yeah, let's consider Linux an OS ready for the desktop :-)."

> Also, I find the "GNU/Linux is already ready for the desktop; I and others use it" argument tired. I've used GNU/Linux for the desktop in 1998, but it sure as hell wasn't ready then.

Conversely, that it doesn't work for certain people does not mean that "it is not ready", which the post does state (sarcastically) as I pointed out above.

> Many use cases aside...

I'm not sure how the browsing, docs and email is miserable, maybe you can expand on that. The video editing is indeed a bit limited from my experience too. However, I don't think "limited proprietary options" is a problem. The community largely and specifically avoids proprietary software. Proprietary incursions into the community are generally seen as a negative thing. And for the lack of codecs, software patents for the most part are to blame.

And then it just comes to my original statement; many things stated in the article are non-issues to most Linux users or just falsehoods:

- Neither Mozilla Firefox nor Google Chrome use video decoding and output acceleration in Linux.

Firefox does.

- NVIDIA Optimus technology is a pain

NVIDIA is a pain.

- You don't play games, do you?

I do.

- Linux still has very few native AAA games.

So "it's not ready" because it doesn't have AAA games? What a pitty.

- To be fair you can now run thousands of Windows games through DirectX to Vulkan/OpenGL translation (Wine, Proton, Steam for Linux) but this incurs translation costs and decreases performance sometimes significantly.

No, not 'significantly' for dxvk.

- Also, anti-cheat protection usually doesn't work in Linux.

For good reason. Blame the dev, and don't make it work on Linux.

- Microsoft Office is not available for Linux

Thankfull.

- LibreOffice often has major troubles properly opening, rendering or saving documents created in Microsoft Office.

And whose fault is this? Use ODT.

- Several crucial Windows applications are not available under Linux.

Thankfully. Also, 'crucial' is subjective.

- In 2022 there's still no alternative to Windows Network File Sharing.

It's available since 1992: https://www.samba.org/

- Linux doesn't have a reliably working hassle-free fast native (directly mountable via the kernel; FUSE doesn't cut it) MTP implementation.

I can transfer files to my phone just fine.

- Too many things in Linux require manual configuration using text files.

No.

etc.

brew info samba samba: stable 4.16.0 (bottled) SMB/CIFS file, print, and login server for UNIX https://www.samba.org/ Not installed From: https://github.com/Homebrew/homebrew-core/blob/HEAD/Formula/samba.rb License: GPL-3.0-or-later ==> Dependencies Build: [email protected] ✔ Required: gnutls ✘, krb5 ✔ ==> Caveats To avoid conflicting with macOS system binaries, some files were installed with non-standard name: - smbd: /usr/local/sbin/samba-dot-org-smbd - profiles: /usr/local/bin/samba-dot-org-profiles ==> Analytics install: 1,477 (30 days), 3,287 (90 days), 6,917 (365 days) install-on-request: 1,459 (30 days), 3,246 (90 days), 6,863 (365 days) build-error: 5 (30 days)

The best thing about net send is, it's entirely unauthenticated -- or at least it was, back in the day. It says "User X on Machine Y" sent this message, and Windows will indeed make sure to tell the other machine who sent the message. But if someone were to reverse-engineer the Windows filesharing and related protocols and turn these into a nice suite of open source tools, nothing would force those tools to tell the truth about which user or machine was net-sending.

You need to deploy AD. Even Samba can do it.

Samba Official

I wanted a solution that was relatively easy to access on a local network and elsewhere. Preferably the same solution used the same way in both cases. This requirement ruled out Samba shares, as it's not designed for sharing across the internet. I looked at NFS, but encountered speed and reliability issues, and recent macOS support is poor with documented workaround to enable version 4 seemingly not working anymore.