zaphod

joined 2 years ago
[–] [email protected] 4 points 2 years ago* (last edited 2 years ago) (13 children)

I just can't afford it.

I'm poor and I listen to a lot of things. Buying all that isn't possible for me.

So basically: you can't afford the volume of product you want to consume at a price that's sustainable for artists, but want the product anyway and you see that as some unsolvable dilemma? Have I got that right?

Look, it sucks that you're in that financial situation. Not here to downplay that struggle. I've lived like that and it fuckin sucks.

But maybe the answer is to value the effort of musicians and either pay them for their work or consume less?

[–] [email protected] 1 points 2 years ago (1 children)

Not if you use a Hurricane Electric tunnel for ipv6 transit. My ISP hands out V6 addresses and I still use HE so I get a stable, globally routable /48 that moves with me (I had to switch ISPs recently and I just had to update my tunnel and everything just worked).

[–] [email protected] 3 points 2 years ago (1 children)

Lol, they're not? THIS WOULD BE YELLING AT YOU. This is me calmly explaining that "running for profit" and "running at a profit" isn't the same thing.

[–] [email protected] 2 points 2 years ago* (last edited 2 years ago)

No it doesn't.

Syncthing only needs to remember the current state of the files/folders it's syncing. Not everything it's every sync'd.

It does that by either periodically scanning the filesystem to look for changes since it last scanned (based on the file creation and modification dates that are stored in the filesystem), or it registers with the operating system to receive events when files are created, modified, or deleted.

When Syncthing notices a create, update, or delete, it pushes those changes to the receiver and then updates it's record of the filesystem state accordingly.

It also pushes whole files, not deltas. So it doesn't care how the files changed, only that they did.

Even with hundreds of thousands of files to sync this is a relatively small amount of state as it's just file paths and their create/modify dates.

[–] [email protected] 2 points 2 years ago* (last edited 2 years ago) (3 children)

The client on the sender side (the phone) knows it sent the file. It doesn't care if the receiver side changed or deleted it. It sent the file. Its job is done. That's why the mode is called "Send Only".

Meanwhile the client on the receiver side (my NAS) never pushes changes back. It only responds to received sync instructions. That why the mode is called "Receive Only".

It's... all pretty simple. Not sure where the confusion lies?

[–] [email protected] 2 points 2 years ago (5 children)

Again, Syncthing supports one-way sync so allowing paperless to delete them and having that delete sync back to the phone is entirely optional.

[–] [email protected] 2 points 2 years ago (7 children)

That'd exactly what you want! When the file initially lands in the sync folder, Syncthing sends it to paperless. Paperless ingests it, deletes it, and it disappears from my phone, now stored in paperless. Exactly what I need.

If I wanted the files to stay on the phone I'd set up the phone as Send Only and the paperless side as Recieved Only.

[–] [email protected] 3 points 2 years ago (1 children)

Yup you're right. Meanwhile Newsweek (as reliable as they are...) reported on it but their dates are even less coherent.

[–] [email protected] 1 points 2 years ago (5 children)

The article was published today so: no?

[–] [email protected] 1 points 2 years ago* (last edited 2 years ago)

If those are deal breakers for you, that's fine. Most of the apps on my phone aren't open source and I already accept my phone is a device I don't control. I focus on running open infra and controlling my data, and don't worry as much about the phone save for a few key items (e.g. password management).

And, frankly, as far as user experience and featureset goes, Symfonium is second to few or none, at least IMO.

view more: ‹ prev next ›