$ grep -ir "remove this after e3" | wc -l
402,429 karma · joined December 1, 2014
$ grep -ir "remove this after e3" | wc -l
40Following the whole banning-saga my impression was that Notes was a genuine extension of the Substack platform, but it being a frontend clone explains why such a tantrum was thrown by Musk.
The screenshots are produced by manually mounting a squashfs, locating a minio binary and running it. It's not a very clear (and completely convincing) demonstration, and IMO could better have been left out.
[1] https://www.idfa.nl/en/film/f2e29b37-216a-4899-ae67-c4367b8b...
[2] https://www.ahistoryoftheworldaccordingtogettyimages.com/ (which can't be downloaded)
The Register's article is a complete shitshow in emulating the confusing language from the lawsuit. Luckily the complaint itself [1] refers to an Ars Technica article from 2021 which finally explains a bit more [2].
[1] https://nclalegal.org/wp-content/uploads/2022/11/Complaint_W...
[2] https://arstechnica.com/gadgets/2021/06/even-creepier-covid-...
> "However, when I showed them the screen shots … they didn't seem to understand it. He said police returned to their cruiser, and when he spoke with them again, they told him they were researching Find My to learn how the app works."
Perhaps the misunderstanding is on the part of the complainant. Especially considering that the 'Find My' signal is potentially originating from <2m of their home, although Sudbury looks quite sparse.
"CCall testsuite doesn't test `signed` arguments and results. This would have helped catch [a previous ghc regression on aarch64]".
[1] https://blog.rmotr.com/the-best-time-to-post-on-hacker-news-...
It's really hard for anyone unfamiliar to the area to not read that in your article. To take three quotes out of the whole narrative: "But web5 takes it to the next level", "it's possible to keep the good parts of web3 while improving on its privacy properties (...) thats what web5 is all about", "In web5 (...) This is a radical departure from both web2 and web3".
I get that you wanted some nice story for your blogpost, but it's just not grounded in reality, and you're supporting the wrong actors here if you really want to claim that 'web5' is about privacy.
> I'm generally happy to support the hype
Happy to support privacy destroying technology by adopting their buzzwords while plenty of people – which you even reference at the end – do keep ethics in mind. Alrighty then.
In reality, many of the good projects and people referenced at the end of the article have been working for years without any notion that their projects are sprung out of some hyped but underspecified 'web3' technology.
Dorsey's 'web5' clamor is mostly about (barely [1]) implementing some existing technology and then writing a bit of slideware around it [2], which proposes to magically "allow individuals, organizations, and companies to publish credentials anyone can discover and independently verify" while not spending any thought on how such a PKI would be ("independently") governed without centralizing everything back again – an all too common failure mode of 'web3' [3].
Meanwhile, both Dorsey's slideware [4] and the actual specifications referenced [5][6] make bad technological choices with regard to privacy where users have stable identifiers (their public keys) which must be published, allowing them to be easily tracked across transactions.
While this can be used as a building block, no material on the 'web5' website or the TBD54566975 Github repository (I guess it's some other wordplay) indicates that they even recognize this as a problem, let alone that they propose how to solve it.
This is no new problem however: Sovrin – which many people referenced in the OP have worked on or with – has published a commentary on this back in 2018 [7]. There's also a great talk by Christopher Allen if you need to refresh your memory about what you need to consider when designing identity systems [8].
Otherwise the OP can be a great introduction to identity, but please don't feed the magical hypetrain.
[1] https://github.com/TBD54566975/ssi-service#whats-supported
[2] https://developer.tbd.website/docs/Decentralized%20Web%20Pla...
[3] https://moxie.org/2022/01/07/web3-first-impressions.html
[4] See the diagram on page 9 of [2]
[5] https://identity.foundation/decentralized-web-node/spec/
[6] https://identity.foundation/ion/
[7] https://sovrin.org/wp-content/uploads/2018/10/What-Goes-On-T...
The benchmark is not whether your existing computer breaks to pieces, but whether it can do that "1) Browsing 2) Coding 3) Video and photo editing 4) Graphic design" smoothly for the coming 5 years in the newest versions of popular applications, as they inevitably get more demanding for older hardware.
That being said, I don't think the SaaS-part of the value proposition is particularly convincing, and there barely is anything else.
Your argument doesn't take into consideration that build artifacts / software releases have culture and best practices behind them. Such releases are often considered, tested, cut, digested, signed and included in package managers delegating trust.
Many one-off installation shell scripts are not afforded that culture, especially when maintained from within (static) websites that update frequently. On the other hand, they are small enough for you to audit a bit. If you'd compare the script with one that someone else downloaded a month earlier (i.e. archive.org), that would help a lot to establish trust.
> If we ignore the idea of downloading and building every program from source
Your argument is equally valid when building every program from source. You will not be able to review the source code of moderately large programs. You will need to delegate your trust in that case as well.
[1] https://www.bloomberg.com/news/articles/2022-03-14/inside-ni...
In the context of the relation with gastric cancer, pickling is about fermentation, not acidity. The studies suggesting a relationship are all epidemiological and suggest a weak link at best [1].
The stomach is already very acidic; much more acidic than vinegar, which makes both gastric cancer and any potential benefits unlikely.
[1] https://www.spokesman.com/stories/2017/oct/05/ask-the-doctor...
[2] https://news.ycombinator.com/item?id=30167403
[3] https://leaningtech.com/webvm-server-less-x86-virtual-machin...
According to this comment three months ago [1] "they used 6%-20% CO2 mixtures with balance nitrogen and some water to try and approximate different exhausts including flue gas".
Yes, fine. So there is no (true Scotsman) domain expert. Grandparent's point is also just that actually building the application and seeing how users interact with it is a valid method of analysis either in a prototype phase or actual evolving production software.
"One such factor [of increasing ADHD prevalence] may be audiovisual media exposure during early childhood. Observational studies in humans have linked exposure to fast-paced television in the first 3 years of life with subsequent attentional deficits in later childhood." [1]
but also
"The diagnosis of attention-deficit/hyperactivity disorder (ADHD) among children and adolescents has increased considerably over the past decades. Scholars and health professionals alike have expressed concern about the role of screen media in the rise in ADHD diagnosis. However, the extent to which screen media use and ADHD are linked remains a point of debate. (...) The available evidence suggests a statistically small relationship between media and ADHD-related behaviors. " [2]
"Baidu maintains two strategies for its AV activities: Apollo open source AV software platform and its own AV products based on Apollo software technology. The internet giant has already built an impressive Apollo open source ecosystem, with more than 200 companies participating."
Which indeed [1] is Apache licensed.