Fair play x775, I'm currently moving lots of EU and UK projects away from US-owned and/or sited infrastructure. There is a huge marketing push from the EU cloud providers to display their sovereign wares. Maybe us Europeans need to make them more aware of how futile it is to move to EU companies if there are laws equal-to or more pernicious than the US CLOUD Act? A dozen large EU tech companies will sadly exert more pressure on EU lawmakers than trying to explain to 500 million normal people how a law that looks like it will protect children is a smokescreen and terrible for civil liberties.
I've tinkered with nostr and there's plenty to agree with here, but it's not specific to nostr. Nostr is in its very early days where people who tinker now are also pretty good at protecting that private key (dorks like us). For mass adoption we're probably going to see WebAuthn develop and solve the problems you're mentioning for most non-technical people. The early dorks will flinch at Apple/Google syncing people's e2ee keys, but techies will always be able to just dial in their private key to the client of their choosing. So it will be a bit messy, but hopefully the best of both worlds. And a giant improvement from current paradigm.
I don't use it, but Minds is an example of an app that is using delegated keys to sign people's messages using nostr protocol, allowing a user's data a route out of Minds' infrastructure in the future. Again, seems a healthy improvement.
One possibility for WebAuthn over email/password is the easy retrieval of local, strong and domain-unique encryption key material via the prf extension. Support for this is currently limited to Chrome Canary + hardware key, but MasterKale thinks it will be coming to other browsers, and biometric:
Thanks for this. Related to it, does anybody have any resources showing the state of the art for non-tech audience to remember client generated private keys?
What are options? Password manager (most people I know don't use one), Browser keychain (no guarantee of sync between user devices), WebAuthn (same problem), IndexedDB or localstorage, (both can be purged, again, no sync).
Unless I'm missing something, I feel this is problem worthwhile solving as a community, it would unlock a lot of utility/privacy for the average web user.
Would love to hear any more qualified takes on this.
IMO the recent announcement of synced WebAuthn platform authenticators that’ll be supported by major platforms is probably the closest thing, at this point.
Thanks for this, I looked up recent Google I/O announcement, it had passed me by. iOS/MacOS has it in beta too, so you're right, we're getting close to half the problem improved.
1. The most beautiful and innovative things being done in the Web3 space are much more beautiful and innovative than anything you will do in your life.
2. The most dastardly things being done in the Web3 space are much more dastardly than anything you will do in your life.
Now for the two broad camps of people I see here:
a. People who think 2. is not relevant to pursuing 1.
b. People who think 2. can never justify pursuing 1. – or even finding out about it.
Look at the kids: the day is better spent curious.
Both 1 and 2 are nonsense. I am very curious about blockchains (Etherium primarily), but so far have not seen any web3 projects that are more “beautiful” than Electric Counterpoint by Reich or more “dastardly” than the holocaust.
If you mean that both of these are achievable on an individual level, then I fail to see how coding an idea has any more potential to achieve these extremes than using a paintbrush.
Look at the kids: they get far more excited by video games than DeFi.
Depth of field, quite literally here! Here are some rules of thumb: If you increase depth of scene, you can use depth of field in two ways. In portraits, you can create greater subject separation because the closer focal point of chicken will be in focus, but the horizon line will be very blurred. Taken at human eye-level, most of the background of a chicken will be grass that's close-by, and therefore a similar blurriness (or 'bokeh'). That makes it harder to discern subject.
Secondly, if you open up the depth of field with a very deep scene, you create more possibilities for composition, framing or storytelling. Again, all you have at human eye level is chicken/grass. At chicken eye level, with a very deep focal range, you might also be able to tell the story of the chicken in 'the great outdoors', you may see mountains and forests on the horizon etc.
For mental health, I've found it a great relief from Gmail. If you feel your mental health is affected not only by noise, but also privacy violations, supporting monopolies etc.
From a designers/UX perspective, there are some thoughtful touches. "The feed" is not just a bucket/folder, but the UI changes for all those newsletters, and I've found that calming. I actually read the curated list of newsletters I've signed up to now, once a week or so in a magazine-like stream without the dozen buttons required for a letter-like email.
The 'reply later' feature allows me to put aside a few emails over a couple of days, then click the 'focus and reply' button and those emails come up in a clean list with a stripped-back interface which moves on to the next email in the stack.
Despite the on-trend aesthetics, this is a thoughtful piece of design, which I moved to for the above reasons and is delivering on.
The support has also been excellent. I submitted a feature request, they got back personally quickly, and then a couple of months followed a personable (possibly automated) email saying the feature I'd requested was now live. (Notion is also in the habit of attending to its users like this).
All email clients are garbage-out if we keep putting garbage in, but as a person looking for a more calming space to manage the deluge, I would say the above review is limited in scope in understanding what Hey is designed for. Why build another email client if it doesn't make some opinionated moves contrary to the state of the art?
This looks lovely. I'm new to P2P applications beyond file sharing and would like to raise awareness about the new resilient web being built. Not just in terms of protocols and applications, but also energy resilience and air-gapped encrypted inputs. Would love to have a chat about Beaker and its place in a wider movement.
I guess this is science communication stuff, rather than talking through the technicals, my background is design.
pfraze, is there a recommended resource for communicating the players and ideas on the resilient web, placing Beaker in its respective place and laying out the benefits in a friendly way for laypeople?
You can reach me at #dat or #beakerbrowser in freenode, in the Beaker mailing list [1], and on Twitter [2]. We're going to be writing about the concepts and architectures over the next couple months, and there are links to blogposts on the rightnav of the docs [3]. We'll announce new posts on the mailing list.
