Woah. That is a lot sooner than I had anticipated.

Yeah, I still see the line now. I am not sure if this was a one-off, maybe the edit occurred when I rebooted the instance for a moment and the edit fell through the cracks… Or there might be an actual issue federating edits.

I think you left this line behind by accident:

l = Lemmy(INSTANCE_URL)

You can create a one-person instance and hold your identity there.

If you what you want is for every server to hold your identity, you have to trust all servers. I think that an evil admin would be able to impersonate any user from any instance if that were the case. How do you delete your account? Can an any admin delete your account everywhere? Which one is the real “you”?

Thank you! I will look into cloudfare, what people say about it, and what resources are necessary to avoid DDoS attacks without it!

Better delivery and avoids exposing your IP via emails, although it’s best to setup a some sort of tunnel to avoid having that problem altogether.

Is it possible to have a public-facing instance without exposing your IP? I am not sure I understand that part, and I am very interested in understanding how to achieve that.

consider using an email delivery service like jetmail instead of sending mail directly from the instance

Why is this better? To overcome spam filters, or is there some security risk associated with e-mails?

A few years ago the plain text passwords would show up in the logs. That has been changed since then, but a malicious instance admin can easily revert this change and keep a log of plaintext passwords.

A developer explained to me that adding client-side hashing would be problematic because different clients might do the hashing in different ways, and that the desired solution is to add OAuth at some point. There is also a bit more discussion about this in that thread: https://lemmy.ml/comment/97830

I lack the technical knowledge in client-side hashing to explain why this is the case, but as far as I can tell client-side hashing is not common at all. The standard is to hash the passwords server-side.

I do think that it is important to be aware of what a malicious instance admin can potentially do: they can log your plain-text password, see your e-mail and correlate it to your IP, look at what posts you like/dislike, and read your non-encrypted private messages. But these are not “Lemmy” problems, as these are general issues when it comes to trusting the servers of the sites that you create an account in.

An important benefit of Lemmy is that you can actually set up your own server or use the server of someone who you really trust, and you can use it to interact with the rest of the instances. It is also possible to create an account without providing an e-mail, a phone number is not required, and you can usually access instances via a VPN or Tor. These are not a common luxuries when it comes to other sites.

Using unsafe passwords is dangerous in a lemmy instance, but it is dangerous anywhere.

That NKnews site is also American. I thought that something like this would be easy to verify, so I have tried to find a bit more information, and according to this site:

https://www.38north.org/2021/11/north-korea-intensifies-war-against-foreign-influence/

While the text of the law was not made public outside of the North, anecdotal reports since indicate that this has prompted a widespread crackdown on foreign content and influence in the country.

So, perhaps it is not as simple.

From reading the articles I would conclude the following:

• RFA, a US-funded asian ‘news broadcaster’, very likely has created this piece of propaganda as an attempt to use the popularity of the Squid Games to disseminate mis-information about North Korea

and

• North Korea did pass a law that specifies death as a possible penalty for distributing South Korean content

So… everyone sucks.