291–300 of 354 posts
Earlier quoted context omitted.
With the aforementioned Taildrop you do not have to trust Tailscale with your data.
Don’t you need to have tailscale on the machine (and thus give full access to all your machines to the company) for taildrop to work?
Earlier quoted context omitted.
It is purely because of the lack of static addressing. Probably an entire country's GDP-worth of SaaS products are essentially nothing more than providing basically a proxy to other devices that have to have apps installed to speak their special language. If I knew your computer's address (and it didn't change) and you knew mine, we could route traffic through the infrastructure we already pay for.
IPv6.
It’s a crappy electron app, but LocalSend is a great open source alternative to airdrop that supports all major platforms with the same ease of use.
It's written in Flutter, btw https://github.com/localsend/localsend/tree/main/app/lib
I typically just run a python3 -m http.server command from a command line on whatever device I need to send from and then hit it on a webpage. You can run that on an iOS device even with something like Libterm
I use Whatsapp. Just create a new group, add one of your friends to it and then remove him/her. You can use it for notes as well.
Here's a thought: This article is exploring the wrong problem. The filesystem where my files reside should already be a fully-distributed filesystem covering all the devices I own, right from the moment I buy and enroll them. With that precondition, my file is already where I need, and any physical bit shuffling is just a detail managed by the OS, using whatever connectivity is already available (or prompting me to "…
Isn't that exactly the model of Gdrive/OneDrive/DropBox etc? Except they might not do any LAN transfer optimizations, but that is minor implementation detail edit: apparently at least Dropbox has had LAN sync for nearly a decade: https://dropbox.tech/infrastructure/inside-lan-sync
- They are a bolted-on "magical part" of your filesystem. If you manage your files anywhere outside of the magical field of synchronization, they're invisible (e.g if your file is in the "Downloads" folder, but that folder is not synchronized by Dropbox, then you won't find it from any other device.)
- They are not distributed filesystems. They are a central filesystem (on their premises, outside your reach) and a smart replication strategy. You don't get a say on data sovereignty, and your data lives on rented disk space.
- Trying to operate on your files is dependent on which device you're using. If you're on a computer, you get first-class local files in first-class directory trees, that you can manage with the usual semantics, provided you have enough free space in the physical disk of that device. If you're on a phone, you download copies of files (and pray they get uploaded if you change them in phone), and almost no way to manage the directory tree aside from the application itself.
Here's a thought: This article is exploring the wrong problem. The filesystem where my files reside should already be a fully-distributed filesystem covering all the devices I own, right from the moment I buy and enroll them. With that precondition, my file is already where I need, and any physical bit shuffling is just a detail managed by the OS, using whatever connectivity is already available (or prompting me to "…
>The filesystem where my files reside should already be a fully-distributed filesystem covering all the devices I own I'd rather not set up the possibility for a single software bug to destroy all my data at once. Even if you have good backups, there could be subtle data corruption that you don't notice until it's too late.
Have you found a solution yet?
Here's a thought: This article is exploring the wrong problem. The filesystem where my files reside should already be a fully-distributed filesystem covering all the devices I own, right from the moment I buy and enroll them. With that precondition, my file is already where I need, and any physical bit shuffling is just a detail managed by the OS, using whatever connectivity is already available (or prompting me to "…
What you describe is called Google Drive/OneDrive/iCloud.
Let's take a real life example: My Android GPS (OsmAnd) records GPX files on my phone storage when I'm out on a trek.
How should I configure Google Drive/OneDrive/iCloud to expose those files transparently in my computer (a linux box at home) as they get created?
And more importantly, why should I have to configure anything at all? The idea I'm advocating for is that those are my files, and so they should be in my (distributed) personal filesystem by default without me having to set anything up.
Earlier quoted context omitted.
OP would rule this out because of the third party cloud service thing, but I use signal in the same way. It feels quite ridiculous but it works. The best option I can think of is syncthing, but the ux for non technical users isn't great.
This is what I do now. I have a group chat with just me in it.