I’m the administrator of kbin.life, a general purpose/tech orientated kbin instance.

  • 0 Posts
  • 26 Comments
Joined 1 year ago
cake
Cake day: June 29th, 2023

help-circle



  • You CAN do the full list of things to get accepted there. But you only need to fail a SINGLE test to get sent to junk mail jail.

    To not be put to junk you need all of the following (oh and this can and will change one day and you’ll go straight to junk)

    • SPF configured
    • DKIM configured with valid keys applied to DNS
    • DNS secured with DNSSEC, with validated keys passing all minimum requirements
    • DMARC configured for domain
    • Your mail server NOR the entire network on a DNSRBL. For example right now my mail server is hosted on OVH (moving soon) and it will go to junk, and in the hotmail/outlook headers it makes clear this is the only failure (-0.2 points, enough to go straight to junk mail jail)

    Not sure if I missed any there. It’s been a while since I set all this crap up.



  • I mean I could have used the GDPR (still a thing in the UK, at least for now). But didn’t see it as worth it. It really wouldn’t be worth the risk selling data that was deleted from a GDPR request.

    I don’t know that they’ll risk using the data from deleted posts/comments though anyway. Most comments and posts will be deleted for a reason (moderation, or otherwise mistakes) and as such, likely isn’t going to make the best training data really.

    It’s far easier to just sell the live data and be done with it.


  • I think there were historically interoperability issues, and there used to be (my version of mbin is quite old), and maybe still are issues federating dislikes (which stems from the way they were seen in kbin, which straddles both thread based and mastadonesque sides of the fediverse). But overall there’s aren’t the larger federation issues there used to be.

    Right now, the choice mainly comes down to the interface you prefer, and if you perhaps want a limited ability to work with mastadon type posts. Since you can follow mastadon users and see their posts within the mbin interface.






  • But then what is a relay? See if a relay doesn’t hold an account and cannot ban/moderate directly content they serve then what’s exactly happening?

    I also wonder if it’s a bit of a legal minefield. See I’m running mbin here. I get content from many other mbin/kbin/lemmy instances. Usually they have pretty good moderation and content is removed on my instance too. But, if someone raises a legal complaint with me directly, I’m required to act on that and moderate on my own instance. Which I can do. It seems like you’re suggesting that’s not directly possible with nostr? So if the main instance chooses to allow it, then it’s tough luck for me, I am required to host it?






  • I think in terms of gdpr, if you notify a site that is providing service (allows users to register from I guess) to EU countries you want something deleted, they need to comply.

    But I think in terms of federated content, you cannot be expected to do more than send information about the deletion out. If other instances don’t respect it, it’s not the originating instance’s job to police it.

    Now the user could go to these other instances and chase it up. But I wonder if a third party instance doesn’t allow users from EU countries, if they’d be required to comply? Federated content opens up a an interesting set of scenarios that will surely test privacy laws.

    I also wonder what the EU powers are to sites in non EU countries that allow EU users but don’t respect GDPR. what can they even do? Companies like twitter, Facebook, reddit etc have presences in EU countries that can be pursued, but John Smith running a lemmy instance on a $5 vps might be out of reach.



  • Pretty much wanted to say similar. Ip address isn’t known beyond your local instance (and any retention time and purposes should be stated in their privacy policy).

    The rest is standard data any federation app will collect upon seeing content from a user.

    It’s also worth noting that in general the user URL (which provides this user data) is generally also public. So if you know the user url you can get this too.

    Having said that, I do wonder how much they can monetize third party data about people that have not agreed to their privacy policy that grants such uses. It’ll be interesting to see.