Untitled attachment

Notices where this attachment appears

1. Embed this notice
   Steffen K9 ? (steffen@misskey.de)'s status on Sunday, 29-Sep-2024 23:24:39 JST Steffen K9 ?

   Misskey.de has been updated! ✨ 2024.9.0 🚀

2. Embed this notice
   Steffen K9 ? (steffen@misskey.de)'s status on Tuesday, 30-Jul-2024 14:21:18 JST Steffen K9 ?

   in reply to

   Misskey.de has been updated! ✨ 2024.5.0 🚀

3. Embed this notice
   Steffen K9 ? (steffen@misskey.de)'s status on Thursday, 25-Apr-2024 16:33:10 JST Steffen K9 ?

   We noticed your domain misskey.de is only listed in a few directories. This can seriously impact your websites traffic for both consumer and business leads for Germany. Please visit us to have your website listed.😂

4. Embed this notice
   Steffen K9 ? (steffen@misskey.de)'s status on Monday, 25-Dec-2023 04:48:37 JST Steffen K9 ?

   in reply to

   I have decided how to handle the threads.net domain on misskey.de. I have muted - but not blocked - the domain on server level. This means you won't see any random public content from threads.net in your timelines. Follow requests are still possible. So, you - as user - can decide to follow someone from threads.net to get their individual content.
   
   This is the current state. Let's see how this works. I'll keep an eye on that topic.

5. Embed this notice
   Steffen K9 ? (steffen@misskey.de)'s status on Monday, 18-Dec-2023 22:36:25 JST Steffen K9 ?

   Threads.net – Not sure how to proceed 🤔
   
   In the last days I have read a lot of statements, opinions, pros and cons about threads.net. But still, I'm not sure how to handle that topic on my nodes libranet.de, venera.social and misskey.de.
   
   Personally, I don't want to be involved in anything related to Meta/Facebook. I'm aware of their history of collecting, analysing and selling meta/user data. From my experience Facebook is often used to spread misinformation - intentionally or out of ignorance. But I don't know anything about threads.net in particular.
   
   When both things would happen on some small, random Fediverse instance I would probably block it. But threads.net is the new elephant in the AP room and until now there's no actual content that would satisfy a domain block. So I'm not sure if I should make that decision now for all users on my servers/nodes.
   
   Possible actions are:
   A) enable the domain block for threads.net now
   B) let the users decide for themselves to mute/ignore the threads.net domain
   C) observe the impact of and actual content from threads.net and decide about the domain block later (giving developers the time to implement possible mitigations)
   
   I'm really not sure what's the best way to handle this. What do you think?

6. Embed this notice
   fedi-block-api notifier (fba@ryona.agency)'s status on Monday, 09-Oct-2023 10:14:38 JST fedi-block-api notifier
   misskey.de has blocked the following instances:
   
   mapsupport.de with unspecified reason
   shota.house with unspecified reason
   rapemeat.solutions with unspecified reason
   detroitriotcity.com with unspecified reason
   freak.university with unspecified reason
   pedo.school with unspecified reason
   youjo.love with unspecified reason
   pouque.net with unspecified reason
   mastodon.cf with unspecified reason