Lemmy.zip admin
Contact me via hello@lemmy.zip


  • Elsewhere: me.lemmy.zip - See my accounts across the internet
  • 327 Posts
  • 621 Comments
Joined 2 years ago
cake
Cake day: June 10th, 2023

help-circle












  • My response wasn’t regarding the geoblock, but to the above poster saying we block VPNs (which isn’t true)

    But just so you’re aware, we dont geoblock federation traffic and all our posts, comments etc are federated without issue.

    The only thing geoblocked is the UIs, so UK visitors can’t access the UI.

    If your client tries to direct you to lemmy.zip rather than the crossposted article, then that client isn’t working properly and you should log a bug. Like any crosspost, the content federates fine.

    Hope that clears it up for you.


  • Sorry but your posts are FUD. You’re trying to equate people misusing tlds (which happens across many other tlds) as somehow lemmy.zip is “bad” instance that should be avoided.

    Not only is that not true, you are also purposely misunderstanding how federation works as if youre somehow safer not interacting with lemmy.zip. Again, not remotely true.

    If you want to block .zip TLDs you go for it, no one is stopping you, but you may as well block .com TLDs while you’re at it as that’s where most scams take place.


  • Just to clear up, you aren’t interacting with lemmy.zip communities directly from your instance. You never directly interface with lemmy.zip, instead the servers send copies of posts and comments between eachother.

    There is no risk from lemmy.zip (obviously) - its a lemmy instance that’s been around over 2 years and is perfectly legitimate. There’s just as much risk from every other tld where people intentionally misspell company names or try to insert similar looking characters. Practice basic Internet security (i.e. dont click on links you aren’t expecting) and you’re pretty much covered.





  • The site is up (as you can see by using a vpn!) - if its timing out and youre not seeing anything from cloudflare then its likely something else in your connection preventing you from accessing the site. ISP related maybe?

    Might also be worth clearing cache or using a private browser tab to check its not something in the browser