cordless VS filemanager

There’s a lot of instances, for example the developer of one of the alternative clients https://github.com/Bios-Marcel/cordless

The cordless project https://github.com/Bios-Marcel/cordless is now abandoned and archived, and the maintainer has been banned for a ToS violation.

People who have been caught using third-party clients have been banned before.

The developer of the cordless Discord client got banned, presumably for using a third-party client.

The only blocking issue is that their success (and subsequent spam/abuse issues) is greater than their focus on open access, to the extent that they formally disallow 3rd party client access.

So at the one end of the spectrum with have IMAP/SMTP, in the middle we have things like Telegram (everything's GPL3! The protocol is terrible and here are all the details! Go nuts!)... and at the other end we have Discord: One Protocol, One Allowed Client™®©.

Do I use Discord? No.

Would I like to use Discord? Yes.

Why can't I use Discord? The client is too much for my older laptop.

Would I like to use Discord? Yes there are a pile of people on there I'm missing out

Can I do anything about it? Yes, I have two options:

1) use https://cancel.fm/ripcord/ until it suffers the same fate as https://github.com/Bios-Marcel/cordless

2) throw the whole thing to the wind until I have better hardware

Hmm. You know come to think about it the chances are people with similar interests are probably also stuck on older hardware too and probably won't be using Discord either...

> There are alternate Discord clients, and — unlike Slack — Discord doesn't try to actively prevent people from writing alternate clients against their API.

Yes, they do.

https://github.com/Bios-Marcel/cordless:

> Hey, so I know this is somewhat of a bummer, but I got banned because of ToS violation today. This seemed to be connected to creating a new PM channel via the /users/@me endpoint. As that's basically a confirmation for what we've believed would never be enforced, I decided to not work on the cordless project anymore. I'll be taking down cordless in package managers in hope that no new users will install it anymore without knowing the risks. I believe that if you manage to build it yourself, you've probably read the README and are aware of the risks. I'll keep the repository up, but might archive it at some point. And yes, you'll still be able to use existing binaries for as long as discord doesn't introduce any more breaking changes. However, be aware that the risk of getting a ban will only get higher with time!

https://github.com/atlx/discord-term:

> Disclaimer: So-called "self-bots" are against Discord's Terms of Service and therefore discouraged. I am not responsible for any loss or restriction whatsoever caused by using self-bots or this software. That being said, there's no one stopping you from risking using an account, so go head!

Worth noting the developer of another third party client, Cordless, recently had their account disabled, which ended with the project sadly being abandoned.

To be honest, I am a fan of the excellent cordless application. Unfortunately, the creator was banned from the service for violating the terms of service. So it is not recommended anymore.

File Browser

Thanks for sharing. I wasn't aware of dufs and it looks very solid. Fileserver[0] is another popular choice, though it's more GUI-oriented for file operations.

[0]: https://filebrowser.org/

The OnlyOfffice desktop app is a pretty good and free alternative to Microsoft Office Suite. You can simply install it on your local machine for offline access.

OnlyOfffice is also self-hostable as a web app for a cloud alternative to Google Sheets.

Filebrowser is a self-hostable alternative to Google Drive.

There's a pull request open to integrate OnlyOffice with Filebrowser for self-hosted google-drive + google docs.

https://github.com/filebrowser/filebrowser/pull/1420

For strictly local use, Google's Nearby share is technically FOSS but the documentation is basically non-existent and a proper Linux implementation is not here yet. Alternatives aren't hard to find though, with Mint's Warpinator or KDE Connect having worked well for me.

For non-local use (everything out of Bluetooth range), you almost have to trust a third party and it really depends on your use case. Want to send your friend a file or host pictures of your birthday for multiple people to download? For the former magic wormhole works great, for the later you could almost spin up a nextcloud or similar (personally I like https://github.com/filebrowser/filebrowser ). Want to regularly send files from device 1 to device 2? Now classic sync solutions like syncthing become really viable.

If everything else fails, FTP always has your back

I have been looking for a file browser which can run in game mode and is reasonably user friendly for simple file operations (copy/delete/rename, etc). Most people recommend Dolphin. it does work but there are issues: the color scheme looks really weird in game mode. context menu does not like game mode, either. Got file browser working (https://github.com/filebrowser/filebrowser) in game mode, which essentially an Edge app accessing a web server on localhost (running as user service). It took some time to set up but the end result is exactly what I would like to have.

File Browser - For access to the files on my NAS

filebrowser has user management plus sharing capabilities

Filebrowser suppports multiple shares with different expiration dates. It also offers file previews and generates QR Codes for the shares.

NextCloud is great for this, but if we're talking sharing files from your sync'd project collection, I'd probably instead recommend Filebrowser. You can point it to the same data store that syncthing is using and it'll make it easy to share the projects. Note that in order to do this you'll need to open up and expose filebrowser publicly. The simplest way to do this would probably be a cloudflare tunnel and for sharing files like this ad-hoc I don't see any issues with their TOS. For things like SyncThing though you'll still wanna do conventional port forwarding. the DIY approach instead of CloudFlare tunnel would be to port forward, set up a dynamic dns record, and set up letsencrypt certs