I really like the storj concept - distributed storage, local encryption.
Comes from tahoe-lafs I believe, except you don't need to find 10 buddies.
There is one main reason I don't use it besides web share:
Despite being OSS, uplink-cli is not available in linux distribution
packages, which
- makes me uneasy about stability/maturity of the platform (e.g. do you not provide packages because you don't have a stable API, and if so, should I really rely on you to keep my data?)
- it increases friction - either build from source or manually copy binaries; and you have need to do this on all your machines and servers; and it means no automatic updates
- binaries/packages without trusted update channels may be against corporate/personal policies, and you usually want your storage accessible on all/most of your computers
- if available in non-distribution package repositories (didn't see in quick-start) - it would still create trust issues
Have you considered getting your cli packages in distributions?
If I could just `apt install uplink-cli` or similar, I would already be using it.
Don't have experience, but I'd guess a buyer/renter won't see a difference between grades of paint quality, but a resistive vs. induction cooktop will be very noticeable and may raise the value far beyond the price difference.
Even in the four scriptures Jesus makes it pretty clear several times that the chosen people are first but they will refuse and salvation will be passed onto others. E.g. the address to Jews when he healed a (gentile) centurion's servant [Matthew 8:10-12]
I don't mind food sovereinty per se, but do we need to subsidize meat?
Lately, in the supermarket, there would usually be some meat at about 2€/kg, which I could not comprehend, as most other groceries have gone up. Pricewise it's competitive with carrots, potatoes and bananas.
How can meat end up cheaper than ordinary pastry? Measured per kg and yes, meat has a lot of water, but still..
The don't make into your cells and tissues, because they're not digestible.
Anything bigger than a "small molecule" doesn't make it through the membranes into your bloodstream. Even individual proteins are too big, let alone a chunk of your frying pan big enough to see.
When talking about a small polymer, I was mainly commenting on microscopic flakes and lakes laced with "chemically inert" molecules that have devastating physiological effects.
Either way, what you claim is simply not true by any reasoning [1], though I do agree eating teflon flakes in moderate amounts should not pose much concern.
Is it more precisely: don't use PFOA or PFOS anymore, switching to less-proven-guilty chemicals with different lengths?
Either way, my concerns are mostly: how much fluorinated waste they release from factories and what happens at the end of product lifetime. Solid fluorinated compounds don't seem atrocious, as they can be reduced to safe minerals if burned properly unlike the spray-on compounds and factory leakage.
I don't know about your experiences, but systemd is leaking preconceived notions and self-imposed limitations like a broken sieve where one is left to sift manually through documentation and bug-reports, collecting and evaluating rules, exceptions and idiosyncratic notions to determine whether systemd will do what one wants.
Latest example: I have a service I want running, so I set it to Restart=always. Read the long Restart= documentations - seems ok. Does it work?
Failure 1: Well.. you also need appropriate RestartSec/StartLimitInterval. Ok, I I set it up. Does it work?
Failure 2: Well.. restart doesn't actually apply to failed dependencies, so .. don't have dependencies that fail, ok? That's not a bug. [1][2]
Battery minerals are not an issue, as you say. I'm still worried about the electrolytes and stuff - not in scarcity, but eventual pollution. They don't typically advertise them and I have a hunch they are nasty stuff.
We will likely have sufficient battery storage where 1.5h would be acceptable though not quite ideal. It still requires quite a bit of storage, but its entirely doable for seasonal variations (the harder problem) and perhaps even daily cycles (the lesser problem).
There is one main reason I don't use it besides web share: Despite being OSS, uplink-cli is not available in linux distribution packages, which
- makes me uneasy about stability/maturity of the platform (e.g. do you not provide packages because you don't have a stable API, and if so, should I really rely on you to keep my data?)
- it increases friction - either build from source or manually copy binaries; and you have need to do this on all your machines and servers; and it means no automatic updates
- binaries/packages without trusted update channels may be against corporate/personal policies, and you usually want your storage accessible on all/most of your computers
- if available in non-distribution package repositories (didn't see in quick-start) - it would still create trust issues
Have you considered getting your cli packages in distributions?
If I could just `apt install uplink-cli` or similar, I would already be using it.