As a kid I was intrigued by telephones. I got hands on two old rotary phones and I wanted them to talk together. I wired them in series with a battery. Despite my dad telling me it never gonna work - it kinda worked. You could hear the other side just well! It just did not ring.
I've made a great effort in making the phones ring. At that time I did not know it needs 90V (fortunately - I'd probably hurt myself). I figured out it needs AC, but how do you produce AC with only a battery? I even made a hack to rapidly reverse polarity using a relay in self-oscillating mode, only to get shocked by the induced voltage by the relay coil and no ring.
(Now I see that maybe if I used the coil voltage it would actually ring!)
This great article brought back nice memories of tinkering with the phones.
How does SQLite handle HA setups? The minimum I want is reliable automatic failover in reasonable time for user-facing service. Ideally an active-active setup.
Is it just a minimal set of unmodified files and Windows will gracefully degradate to this? Or did he need to patch everything to be able to strip it down?
No, the author is presenting an idea that $25 a month can buy you a node. That fits adding a new node to the network, not taking over an existing node.
The assumption is the adversary controls x of N nodes. When x=N the probability of discovering the onion service IP is 1. But the adversary can not achieve this situation as he only controls the additional nodes. The existing nodes still stay in the network, they do not disappear. The ratio is not x/N but x/(x+N).
Ohh, that's probably why our integration suddenly stopped working for single-tenant app registrations right before release. We were using the /common endpoint for everyone. That is disallowed now.
I think it is a tradeoff between "everybody can request age verification" and "only state-licensed parties can request age verification". I don't think everybody's ID card should tell anyone if the holder is adult or not, especially wirelessly
Our state-issued eID cards are supposed to have a function that allows anonymous age verification to a trusted party. It should work like this: a requesting party sends a request signed by state-issued certificate to the ID card, the card verifies the request authenticity and responds with a signed confirmation of legal age and that signature then can be verified by the requester.
No personal information is shared.
While I do not aggree with pervasive age restrictions, this is a nice technical solution to privacy preserving age verification
How that works when you need to distinguish between "no value provided" and "a value that is not in the list" - in some applications they have different semantics.
Yet, Google is a lot more specific im what, how and why you license the content to Google. And it is not for anything that Firefox does.
Plus:
> Some of our services are designed to let you upload, submit, store, send, receive, or share your content. You have no obligation to provide any content to our services and you’re free to choose the content that you want to provide.
> We need a license to allow us to make some of the basic functionality of Firefox possible. Without it, we couldn’t use information typed into Firefox, for example.
Like - what basic functionality? Does not sound like "browsing" is that functionality and I am not interested in any other functionality. I do not want you (Mozilla organization) to use any of that information.
Moreover, what if I do not have the right to sublicense the content I enter to FF? Am I legally not allowed to use Firefox?