-
Web3 for data preservation? (Or is it just another expensive P2P?)
Drew Austin raises an important question in Wired: How should we deal with our accumulated personal data? How can we get from randomly hoarding to selection and preservation? And why does his proposed solution of Web3 not work out? A few analytical thoughts.
-
Web3 is just expensive P2P
Web3 claims to be the only way to save us from commercial entities defining what we can see and what not. Yet, it does exactly this: It results in commercialized entities defining what we can see and what not.
-
Electronic Vaccination Certificate: Eureka! Eureka?
When I was reading the original “Spiegel” article on the German Electronic Vaccination Certificate, I was fascinated.
-
Using a user database backend for Apache authentication
Would you like to use an existing database for Apache authentication, e.g. instead of the htpasswd file in your small WebDAV server?
-
DDoS: What we can do to prevent it
Distributed Denial of Service, DDoS for short, is the shooting star in today’s Internet nightmare gallery. Here is a quick overview over what each and everyone of us can do to prevent his. And some hints at manufacturers and researchers.
-
Blockchain in a nutshell
People often try to claim blockchain use cases without much deliberation. Here is a condensed, quotable version of «Hitchhiker’s Guide to the Blockchain» and «Data lifecycle questions, not only for Blockchains».
-
Debugging NTS problems
Debugging is hard, debugging security protocols doubly so. And there are not many tools and how-to’s availabe for NTS yet. So, here’s a (short) list of NTS problems I have seen and some tricks for debugging them.
-
Solana Blockchain: Proof of History analogies
Here are some attempts to compare Proof of History (PoH), as used by the Solana blockchain, with Proof of Work (PoW). Comparisons to real-world activities, such as dice rolling or outer-space rubber-stamp throwing are also included.
-
How to create DNSsec DANE TLSA entries
Rationale One of the most promising features for DNSsec is the ability to tell a client which certificate to expect when connecting via Transport Layer Security (TLS). RFC 6698 specifies how TLS Authentication information can be put into DNSsec. So when you ask for the IP address of the server, you can simultaneously obtain the information which…