Avatar
DataNostrum
4aa4d22440770429fa745b674fab7e46ed267f36a1abae6ff4e8d26eb65b7f52
Stumbling around

Purpose as far as I gather: 1) fun, 2) motivation for setting up zapping capabilities (both sending and receiving) in order to participate.

Outcome: more zappers = more taps = more excited newcomers to #nostr #grownostr

Can Midjourney or another AI generate realistic eyeballs that we can feed into the orbs?

I'm interested, what do you mean by it does not apply to earth alone? That humans civilizations did not hide from each other out of risk aversion?

Replying to Avatar nym

Perhaps there is a market to create a GDPR compliant Nostr relay?

1. Data Controller and Processor Responsibilities:

- Under GDPR, the roles of data controllers and processors are clearly defined. If a relay operator is storing or processing personal data, they may be classified as a data controller or processor, depending on their specific activities and control over the data.

- This classification would impose certain obligations, such as maintaining records of processing activities, implementing appropriate security measures, and complying with data subject rights.

2. Right to Erasure (Right to Be Forgotten):

- GDPR grants individuals the right to request the deletion of their personal data under certain circumstances. If a relay stores notes containing personal data, and if an author requests deletion, the relay operator may be obligated to comply.

- However, the decentralized and censorship-resistant nature of the Nostr protocol might complicate this. If data is replicated across multiple relays, deleting it from one may not remove it from others. The protocol's design and the relay's specific implementation would need to be carefully considered.

3. Third-Party Personal Data:

- If a note contains personal data about a third party, and that data is processed within the EU, GDPR obligations may apply.

- The relay operator would need to ensure that there is a lawful basis for processing this data, such as consent, a legitimate interest, or compliance with a legal obligation.

- If the third party requests access to, correction of, or deletion of their personal data, the relay operator may have to comply, depending on the specific circumstances.

4. Data Minimization and Purpose Limitation:

- GDPR requires that personal data be collected for specified, explicit, and legitimate purposes and that it be adequate, relevant, and limited to what is necessary for those purposes.

- Relay operators would need to consider what personal data they are processing and ensure that it aligns with these principles.

5. Cross-Border Data Transfers:

- If a relay in the EU is transmitting personal data to relays outside the EU/EEA, it may need to ensure that appropriate safeguards are in place to comply with GDPR's requirements for cross-border data transfers.

6. Legal Consultation:

- Given the complexity of GDPR and the unique characteristics of the Nostr protocol, it would be advisable for anyone considering running a relay in the EU to consult with legal professionals specializing in data protection law.

- A detailed legal analysis would take into account the specific implementation of the relay, the nature of the data being processed, and the applicable legal obligations under GDPR and other relevant laws.

Wow, that sounds like some significant headaches for EU-based relay operators. Btw, do you know what counts as personal data? For example, if someone posts under a 'nym for a period of time, and then their identity is revealed, do all of the notes authored under that 'nym become personally identifiable personal data?

and they literally rugged the Dude

I am curious, what are the GDPR implications for running a relay in the EU? Does it need to allow for deletion of notes if requested by the author? What if a note contains personal data about a third party? #asknostr

When nostr organized fun interferes with marital organized fun

True - that would be an adversary that is already insanely rich & powerful, and does not wish to see Bitcoin grow

If they remained under the radar. But the existence of such a method would also enable its wielder to 51% attack the network at will. It would invalidate Bitcoin's Proof-of-Work and effectively break the protocol

Unpopular opinion: #Bitcoin is NOT backed by math.

There is no proven theorem that SHA-256 is a one-way function (i.e. hard to invert/collide). In fact, no single function has been proven hard in this sense.

Bitcoin is backed by *evidence* that nobody has published a weakness of SHA-256, and by the "proof-of-Lindy" that nobody appears to have cracked this half-trillion USD honeypot in 14 years' time.

However, if someone *had* figured out a way to invert SHA-256, how would we know? A highly profitable way to monetize this knowledge would be to join the mining game in a low-key manner, slowly increasing your "hashrate" over time (so as to be indistinguishable from regular miners), while not incurring electricity costs. Someone could already be doing this, and we wouldn't be able to tell.

Change my mind ๐Ÿ‘‡

What is the last thing that blew your mind? #asknostr

So like a French food critic