sunsetonsaturn

> 10 years

Moving from SHA-1 to SHA-2 took ~20 years - and that's the "happy path", because SHA-2 is a drop-in replacement.

The post-quantum transition is more complex: keys and signatures are larger; KEM is a cryptographic primitive with a different interface; stateful signature algorithms require special treatment for state handling. It can easily take more than 20 years.

Regulators require a transition to quantum-safe algorithms. In the EU, systems labeled as "highly important" must complete the transition by 2030; so you have to do it regardless of how quantum computers evolve.

The ambiguity goes away if you write them as "все" and "всё". Diacritics, accents, umlauts and cedillas are useful; if you omit them you do a disservice to the reader.

Could you elaborate more on the "a small VPS is free"? Except Oracle's free tier offer, I am not aware of others; I'd appreciate it if you could point me in the right direction.

If you're in the EU:

Leverage the GDPR and contact Google's DPO (Data Protection Officer) to inform them about the problem. If the problem is not solved or there is no reaction, lodge a complaint with the DPA (Data Protection Authority).

Can you provide some figures, in terms of profitability? How much did it cost to put together, what are the monthly costs to keep it afloat?

I write a book and give it away for free on https://book.railean.net, but it wouldn't hurt to turn it into a revenue stream.

Record, produce transcript, look for keywords, alert the puppeteer when something interesting is picked up - trade secrets, pre-shared keys, defense sector intelligence, etc.

I'd like to give it a try, but it is not compatible with my device. Is there a reason for it not to work on a Galaxy Note8?

Vielen Dank!

Excellent client, but Windows only.

How would you approach this problem https://github.com/pyasn1/pyasn1/issues/55?

There is a library called `pyasn1`, the author passed away and there are some challenges, such as intimidatingly long error messages that are not easy to interpret, or counter-intuitive behaviour of some of the functions in its API.

Do you have any tips for approaching this with the few resources that are available?

I take a similar approach in this children's book: https://github.com/ralienpp/book-two. In the end there is a section about the trees* that grow in the area, their leaves and fruits - so kids can learn to identify them. I'll incorporate some of these materials in the next iterations of the book.

The first link in the repo readme is for the on-screen PDF, you can look at the pictures.

* One of the characters in the story uses trees to figure out where they are and find their way back home.

I had a similar experience as a child. I cried every day morning before school. This continued until I was switched to another school.

Both schools were regular ones, and in both cases - there wasn't any bullying. I don't remember what the problem was, but the fact is that going to a different place had a great effect.

In your particular case, it could be the change itself that had an impact, rather than the "Montessorinness" of the new school. Also, consider the Hawthorne effect - it could also explain the situation.

Looking back at those times, 30 years ago, I really cannot tell why I didn't feel well in the environment managed by with my first primary school teacher. She was a decent lady, she treated her pupils with respect and never shouted at us, or anything of that sort.

> Many Germany have friendships with people from Ukraine. I myself have several in my wider social circle.

Not sure that's a good argument. Many in Germany also have friendships with people from Russia. Would that automatically mean that Germany has to support Russia? I doubt it.

Considering that both of you are who you are, I recommend "A miracle in the Andes".

Thanks for recommending "438 days" - I'm adding it to my list. And yes, I really enjoyed "Unbroken".

The GDPR is meant to address this problem, check out https://www.enforcementtracker.com/ to see what the most recent rulings are.

Your observations are correct, the regulation is able to deal with the damage after it was done, and apply some form of punishment after the fact. It takes whistleblowers and activists to reveal some of the wrongdoings, otherwise the violations remain unknown to us.

Therefore there has to be a greater push towards proactive measures - letting people vote with their wallet by making informed choices; the prerequisite for that is for the relevant information to be available to them.

Have a look at some of the research I've been involved in, we're trying to solve this exact problem: http://privacy-facts.eu/

There is a project for bringing relevant privacy facts closer to users, so they can make informed decisions before choosing to buy a specific product or service. Check out the second screenshot on this page: http://privacy-facts.eu/features/

The idea is to express everything in unambiguous terms, so there's no way to weasel out of it with "yeah, but not by default" or, "well, it depends", etc.

Diffing texts is not the way to go, because sometimes they can change the wording without changing the meaning - yet, the diff will give you a lot to sift through in order to answer the question "what has changed?"

A better approach is proposed in this paper: https://link.springer.com/chapter/10.1007/978-3-030-76663-4_...

It discusses a formal notation of privacy terms, which enables you to treat them like tuples and perform all sorts of set algebra operations with them, making it easy to answer questions such as "what has changed?", "what has been removed?" or "what was added?"

This would make it possible not only to compare a policy with another version of itself, but also compare it with policies of competing services and products.

Consumers would be better off if regulators mandated the storage of policies in a format like this one. An ecosystem of utilities could be built around them (change trackers, search engines, recommendation systems, etc.).

Thank you for the suggestion.

Concerning the contribution of code for adding Bluetooth support - if a company would want to allocate some time and a person for this cause, would there be someone who can guide them in the process? Perhaps the challenge could be broken down into smaller components?

Assume that you get a rational human being at the input, they know various programming languages (including C and C++), but have no experience with RIOT whatsoever - would this work out?

Would I be able to build something that leverages Bluetooth mesh functionality with RIOT and ESP32? Is this use-case supported well?