Ah. The link answers to this question under "Advanced Data Protection and iCloud.com web access"
> When a user first turns on Advanced Data Protection, web access to their data at iCloud.com is automatically turned off. This is because iCloud web servers no longer have access to the keys required to decrypt and display the user’s data. The user can choose to turn on web access again, and use the participation of their trusted device to access their encrypted iCloud data on the web.
Then they explain that if you turn it on again, your devices will send your keys to Apple's servers for the duration of the web session. Technically this leaks your keys to Apple forever, but they promise that they keep it for the duration of the session.
Flare | https://flare.systems | REMOTE or ONSITE but must be in Canada | Full Time | Full Stack Devs
Flare provides proactive external cyber threat detection. We help security teams visualize and manage external cyber risk. This mostly means open and dark web crawling, analysis and priorization.
Most of our stack is typed python running in k8s (AWS EKS) microservices. Frontend is VueJS with TypeScript.
A simple wrapper around pass might do the trick. Someone just needs to implement an agent that does this (tho I'm sure someone out there is working on it).
I don't remember enabling iNotify earlier than it was merged in master. Did I miss a build flag that enabled it earlier than I should have?
Anyways, I'll use this opportunity to say that it has always been great to work with the guys at Syncthing. They responded quickly to every issue that we have ran into. For example, the switch from FontAwesome to ForkAwesome was done for due to a Debian issue:
IIRC, the package description said something similar to "this is the iNotify version of the syncthing binary", or I may be completely wrong. I need to get previous versions and look to the descriptions of each :)
You might mix that up with syncthing-inotify, which was an external small inotify watcher that then pinged syncthing via its API. It was the recommended way to get inotify support till the functionality got merged.
Maybe, however all my Debian installations are very strict in their repository configuration, and I'm failing to see syncthing-inotify package in Debian snapshots server [0].
...or maybe I'm making all these up from all the things I read while researching syncthing, who knows :)
Regardless of all, it's working very well and it's dependable now, and it's the point I think :D
Addenda: Actually, forgetting all little details about it is a reliable sign of an application working well and just disappears to the background IMHO.
Mozilla are winding down their efforts to make Firefox competitive. They are not planning to make a full servo browser anytime soon and they are transfering resources to VR and other things. This is disapointing.
You can't blame them, their user base is in free fall.
I don't think you understood the parent's core point. The "masses" aren't going to find or buy an old server and install Debian and FreedomBox on it, and then set it up to run headless in a corner of their house. That's not in the area of technical expertise of most people. They might, however, buy a pre-built, pre-installed appliance that just needs to be plugged in and have a web browser pointed at it to get started.
Philosophically speaking, the more and more that products are sold with one purpose on a closed platform, the more and more of these products that are going to end up in the junk yards when they can't be extended or repurposed beyond what the manufacturer wanted (or ever thought) possible.
> They might, however, buy a pre-built, pre-installed appliance that just needs to be plugged in and have a web browser pointed at it to get started.
Don't forget about setting up the freaking wi-fi network. Apple, Google make it reasonably seamless to setup their devices from an app, say. Most third-party devices aren't as easy to setup. I have to manually enter my wi-fi password in my Tivo, eg.
> Philosophically speaking, the more and more that products are sold with one purpose on a closed platform, the more and more of these products that are going to end up in the junk yards when they can't be extended or repurposed beyond what the manufacturer wanted (or ever thought) possible.
This doesn't have to be the case, though. There's nothing stopping FreedomBox from selling a pre-made hardware solution that just has the software loaded on it that anyone can load onto a vanilla server of their choosing. (And it seems they actually do this, though it's not obvious from their website.)
Ring is comparable to Tox, but it has much less bugs.
Full disclosure: Ring dev here. I can answer questions.
Keep in mind that some of the platforms you have listed here are not decentralized. When using a fully decentralized system like ring, you must be willing to compromise on some functionality.
1. Who is developing Ring? Is there a company behind the software? Who are the people?
2. Is it really truly P2P? Does it require servers or known supernodes? If so, what guarantees that those are up? (E.g.: Skype used to be somewhat P2P until MS changed that, and banned old clients from logging in - is that scenario possible?)
3. What is the UI framework based on? (i.e. is it another Electron app?)
4. Bittorent Bleep looked promising, until it was suddenly no more. How are you going to keep Ring afloat? What's going to ensure it's there in 5, 10 years? (As much as I don't like Skype, everyone I need to (video)chat with has been there for 15 years)
Some situations require extra nodes:
- If ICE can't open a connection with: ip-to-ip, UPNP, udp hole punching, it will revert to using a TUN/STUN server hosted by Savoir-faire Linux. Note that you can configure your own TURN/STUN server in the Ring settings.
- The first time that Ring connects to the network, it needs a "bootstrap server". A bootstrap server isn't really a super node, it is just a "know active node". Every DHT-supporting bittorrent client supports this. Note that you can point ring to another bootstrap server in the settings.
- Ring uses an optional blockchain (ethereum) based service to register usernames. This isn't part of all ring nodes by default. It has to be installed separately and then you must point your ring client to it. You can chose not to use usernames if you want and call people with their full RingID instead.
3. We have several clients, all of them use native frameworks.
- GNU/Linux: GTK
- Android: native android libraries
- Mac: native mac libraries
- Windows UWP: native UWP libraries
- Windows win32: native win32 libraries
- IOS: native ios libraries
4. Ring (sflphone) was released in 2004. At first, it was a SIP softphone app. It only became decentralized a few years ago. However, the app still supports SIP.
The development has been generously funded by Savoir-faire Linux since 2004 and there is no plan to stop. Savoir-faire Linux has taken every step to ensure that Ring remains free. Joining the GNU project, (2016) was one of these steps:
- https://lists.gnu.org/archive/html/info-gnu/2016-11/msg00001...
