I was also infuriated by this, so much so that I switched to TIDAL. Migrating was easy— I used their recommended webapp ti migrate all my playlists. Have been using TIDAL happily ever since. Never any popups or ads.
Amazon and its Delivery Service Partners (DSPs) employ thousands of drivers. These drivers are overworked and are owed thousands in wages a year, sacrificing their safety for speed and efficiency.
Our report focuses on this workplace surveillance technology, and how it makes these jobs worse for drivers and our communities.
To better wrap my head around how FOKS facilitates team collaboration, I'd like to see two comparisons:
1) compare to a team-shared Linux machine with SSH daemon. Each team member has a user account, and they can manage their SSH authorized keys, including keys stored on Yubikey. The team can share files and git repositories on the Linux machine's own storage. Some differences I see with this approach are the federated aspect and "append-only data structures that allow clients to catch dishonest server behavior".
2) compare to Radicle, a decentralized git service. Identities are keypairs.
With FOKS, how coupled is storage of git and secrets to the FOKS server?
I'm not familiar with Radicle, but I'll check it out. For (1), consider the case of that server being hosted on AWS. Even though only members are authorized to SSH into it, the plaintext is still known to the cloud hardware, and can be exfiltrated that way. In FOKS, the server sees encrypted data only, so that attack is greatly mitigated. I would say that if the SSH server was hosted on one of the workstations of one of the team members, then the security advantages of FOKS would be much less.
The KV-Store and Git server are implemented as "applications" on top of the FOKS infrastructure, so they aren't coupled. They see a sequence of Per-Team-Keys (PTKs); they use the older ones for decryption and the newest for encryption. I'd really love to see all sorts of other applications built on top of FOKS but we might need to do some work as to nailing the right plugin architecture.
Everyone now has fondness for these and for thin clients in general, but I don’t see this concept used in modern times. Is there any modern equivalent, in particular with the power of a workstation rather than a kiosk? Amazon’s WorkSpaces is anemic— low memory and high price, with their own marketing proposing it for contact centers and front desks. What modern thin client solution can truly replace full computers, especially with local / on-prem processing?
minor nitpick, but it's not ownership so much as location. Sometimes the ISP will own the equipment, but it will be located on the customer premises rather than the ISP premises. It's an important distinction as you can't just rock up and do stuff to it.
Estimating entropy is challenging because it's a reverse process from how it ought to work. I created https://phrase.shop, which generates passphrases with a known quantity of entropy. Hover over any of the three action buttons to see exactly how many bits of entropy will be used to generate the passphrase.
Not sure how much I like this. With this algorithm, the user would never see 100% displayed, because at that point the UI would change to remove the progress bar entirely. Whereas seeing 100% feels oddly satisfying, even if inaccurate.
Many TUIs (text user interface) with multiple operations will show one bar reach 100% and move onto the next process (or show multiple in parallel).
If the UI automatically transitions to a totally new screen after completion, I'm never going to see 100% anyways, unless the app does the exact infuriating thing in TFA, which is render 100% (at 99.whatever) and then do some fsync/cleanup and actually be frozen showing 100% which is the contrapositive of oddly satisfying, it's unsurprisingly unsatisfying.
