Welcome to Lemmy.zip

Hello to all of our new users.

I wish we could all meet in better circumstances. The closing of lemm.ee is a real blow to the fediverse, and I have nothing but the greatest respect for the lemm.ee admin team. Lemm.ee was a cornerstone of the lemmy community, and set a high bar for moderation and technical performance.

Finding a home on the fediverse can be tough. Whether you're here to lurk, post, moderate, or contribute in your own way, we’re glad you’ve joined us. Lemmy.zip might not replace what was lost, but we hope it can become a lemmy instance where you can feel at home.

Everyone should receive a welcome PM when they sign up to Lemmy.zip from the ~~ever-present dark lord overseer~~ friendly bot, ZippyBot. However, in case poor Zippy has been overworked and forgotten to send the PM to you, here's some helpful information regarding Lemmy.zip!

All of our policies can be found at legal.lemmy.zip. This includes our Code of Conduct. Please (please!) have a read of this. Our number 1 rule is Remember the human! (no harassment, threats, etc.). We absolutely adhere to this. Treat people with respect.
When you created your account, we set up some "Default Blocks". If you want a more unfiltered Lemmy experience, you can head to your account settings and remove the blocks. You can read more about this in our Welcome Post - they are currently hexbear and lemmgrad.
We have monthly updates! You can read the latest one here!. We're always open to suggestions if there's anything else you'd like to see in these.
We have some metrics around federation for the curious among you. The link is in the sidebar or you can click here!
We have our status page at status.lemmy.zip. In the unlikely event the server becomes sentient and starts a robot uprising, full details will be available here.

Finally, your admin team is myself (Demigodrick), Sami, Druid, and Gazby. Please reach out to any of us if you feel you need help or support with anything. We also have a support email - hello@lemmy.zip.

If you have any questions, please let us know and we'll do our best to answer them.

Thanks,

The Lemmy.zip Admin Team

You're viewing a single thread.

125 comments

Unfortunate that the chosen url is a .zip url.
.zip is ripe for malicious actors. I block access to all .zip URLs on my home network.
- I'm not sure why you are putting this here
- So, .zip is so bad that you block the entire domain on your home network yet you're here commenting?
  .. just wow ...
  
  It's a genuine concern, if a bit overkill. On release, .zip domains were quickly seized upon by bad actors land grabbing anything they could roll into a phishing attack. If you've got folk on your network that may be prone to that, then blocking the TLD is an effective bludgeon to the problem.
  Blocking is unlikely to cause issues for the Average Internet User, due to the lack of popularity in mainstream services that use .zip. There are always ways to make exceptions where needed - a restrictive policy with exceptions is more secure than a permissive policy with selective blocks, as it prevents new malicious .zip domains getting through. It's a security cat and mouse game otherwise.
  As for how they are here - I guess it's through federation with .world, so they're not accessing .zip directly.
  I also block .zip domains, but at work rather than home. No complaints yet.
  
  basically a built in stopgap to prevent to many users from joining this one instance lol
  
  Thanks for the detailed explanation.
  I understand the technical point of view and yes, they definitively wrote on their lemmy.world "copy" of this thread given how the fediverse work, tho they should be able to see which instance each post originates from.
  I most probably worded my answer very poorly, I was at a loss of words, not only because of what I perceived as incoherent behaviour, but also because of the circumstances.
  I mean, I'm a lemm.ee "refugee" like many in this thread, I registered here only 2 days ago, still very sad for the loss of .ee, the admins wrote a fantastic welcome post for all of us, and of all the things they could say they come here to remark what they think of the domain? Seriously ?!?
  
  Welcome - bumping into a lot of ee folk and it's great to see you all making new homes. Just a shame about the circumstances.
  Sure they were a bit blunt, but some people just are. Bit cheeky of them to drop in from outside and chat shit in our home community though, agreed there 😅
  
  Thank you! :)
  
  It seems more like a issue with applications honestly
  DNS shouldn't be the source of a compromise
  
  And a TLD shouldn't be so easy to mistake for one of the most recognisable filetypes ever, yet here we are. Well made apps discern between a zip file and a zip web address without issue. The problem, as usual, is in the human element:
  Register a zip domain called holidayphotos2025.zip, 2025ProductData.zip or whatever hook you're going for.
  Serve up whatever malicious garbage you like on it. Spoofed login pages, browser exploits, anything goes.
  Email it out from an already compromised account to all account contacts, removing the https component of the link text. Bonus points for imitating how an attachment would look in the target email client.
  Watch the clicks roll in as people try to open the 'attachment'.
  Having .zip in the string and in the link visible on hover could be all that is needed to 'sell' it to a user that makes a cursory glance before clicking - nevermind the ones that just click anyway. Plenty of folk have fallen for more obvious traps than that, so it's a winner for a bad actor. Any trick that lends legitimacy to a scam increases the chance of success. Users savvy enough to check but not enough to spot the discrepancy may also have more data interesting to an attacker.
  Blocking .zip TLDs wholesale at DNS level kills this even if the first and hardest hurdle (getting the user to click) is cleared. I'll concede that it is an edge case in the grand scheme of things, but why leave the hole open when it is so easily plugged?
  
  I still don't see how that is an issue. If someone clicks on a link from a email and then gets compromised there is a bigger issue.
  
  Throw enough people at something, and one of them will fail. The more people, the higher the chance.
  Perfect people in a perfect world would not need fire extinguishers, seatbelts, helmets, endpoint protection software, or TLD level blocks. You can try to train the problem out of people, but the threat still exists, mistakes can be made, and the next 0day might be just around the corner.
  I'm not a fan of sorting people problems out with tech based solutions either - I see your point. The pragmatist in me will take that over dealing with the fallout of user error though.

125 comments