lemm.ee refugee here. I was considering piefed, but photon didn't support it.

Now that the API is there, hopefully it will in the future

been on .zip 2 years-- its been great, and @Demigodrick@lemmy.zip is incredible as admin

That's very kind of you ️

Can you recommend an instance with a federation policy as wide as lemm.ee? Lemmy.zip, for instance, does not federate with hexbear, right?

Feddit.uk is pretty good for this. I think our defed list is pretty minimal.

Both list of blocked instances are in the body of this post

Lemm.ee federates HB, and lemmy.zip does too.

Im currently usong boost with .ee, but i think support for that stopped too? Im going to have to change clients and instances

I still can't take anyone running a .zip TLD seriously. It was bad idea to create it and it's a bad idea to use it.

Is there any PoC of attacks on Lemmy using .zip TLD ? The instance has been up for 2 years, I never heard anything

Can you explain why, for me? Genuinely curious, I don't understand.

The problem is that .zip conflicts with the very commonly used zip archive format which has caused user confusion - a user might click on what appears to be a URL to www.fakewebsite.zip and instead end up downloading a malicious .zip file. This creates an unnecessary and entirely avoidable security risk.

Google opened registration for the .zip and .mov top-level domains to the general public on May 3, 2023. Its release was immediately met with condemnation from cyber security experts as a result of its similarity with the file format of the same name. Malwarebytes warned against the use of already recognizable filenames and their confusion with top-level domains, as "plenty of users already have a clear idea that .zip means something completely different". Experts cautioned against their use, and noted that the use of .zip filetypes in cybercrime had had "an explosion" in recent years. Cisco warned against the potential for leaks for personal identifying information. Researchers also registered similar concern about Google's .mov domain.

Surveys by security researchers immediately following public release of domain registration found numerous examples of links and domains registered under .zip being used in phishing attempts, and the ICSS recommended disabling access to .zip domains until "the dust settles and risks can be assessed".

.zip (top-level domain) - Wikipedia

(en.wikipedia.org)

Choosing to use this TLD basically just screams ignorance, and should be causing users to question the competence of the person who made that choice.

Targeting Lemmy specifically? probably not, but that's not really the issue. It's not that being a .zip address makes the server vulnerable, it's that the existence of the .zip TLD makes everyone vulnerable:

Surveys by security researchers immediately following public release of domain registration found numerous examples of links and domains registered under .zip being used in phishing attempts, and the ICSS recommended disabling access to .zip domains until "the dust settles and risks can be assessed".

.zip (top-level domain) - Wikipedia

(en.wikipedia.org)

lemmy.zip doesn't allow users from the UK.

You guys are making me feel left out

Our findings show that the abuse rate for the .zip TLD is 0.20% which is close to the average compared to all other TLDs. This rate indicates that .zip domain names are not being used to attack users more than the average TLDs - at least for now. However, if attackers find they have better success using .zip than other TLDs, the rates of abuse might change.

Given new TLDs, such as .zip, tend to have a higher abuse rate than legacy and ccTLDs we suggest that the security research community should continue the healthy debate about the potential risks of the .zip TLD and that internet users continue to be weary of downloading and opening files with a .zip extension or TLD from sources or individuals they may not know.

The .zip TLD: Ripe for abuse, but so far so good

DNS Research Federation (dnsrf.org)

Choosing to use this TLD basically just screams ignorance, and should be causing users to question the competence of the person who made that choice.

Not sure if that tone is the best for a healthy debate.

Our findings show that the abuse rate for the .zip TLD is 0.20% which is close to the average compared to all other TLDs. This rate indicates that .zip domain names are not being used to attack users more than the average TLDs - at least for now. However, if attackers find they have better success using .zip than other TLDs, the rates of abuse might change.

Given new TLDs, such as .zip, tend to have a higher abuse rate than legacy and ccTLDs we suggest that the security research community should continue the healthy debate about the potential risks of the .zip TLD and that internet users continue to be weary of downloading and opening files with a .zip extension or TLD from sources or individuals they may not know.

The .zip TLD: Ripe for abuse, but so far so good

DNS Research Federation (dnsrf.org)

Choosing to use this TLD basically just screams ignorance, and should be causing users to question the competence of the person who made that choice.

Not sure if that tone is the best for a healthy debate.

Those users are probably going to go to feddit.uk?

Right, ok, so the problem with having a debate on this subject is that there's no reason for this risk to exist at all. There's no good reason to have a .zip TLD, there was no need for it, it should not have been created and no one should use it.

If you're weighing pros and cons, there are exactly 0 pros. Therefore no matter how minor you think the cons are, they outweigh 0 pros by 100%.

Also, "nothing bad has happened yet" is not a valid argument and is a terrible basis for making risk decisions.