Skip to content

Piero Bosio Social Web Site Personale Logo Fediverso

Social Forum federato con il resto del mondo. Non contano le istanze, contano le persone

Let's try this again.'n'nServer A users are not posting or boosting anything that is objectionable to Server B.'n'nBut Server A is federating with servers Server B does not like.

Fediverso
5 3 21
  • Let's try this again.

    Server A users are not posting or boosting anything that is objectionable to Server B.

    But Server A is federating with servers Server B does not like. [1]

    How does this affect Server B in any way? Or, why would Server B cite this as a reason to defederate from Server A?

    Is it merely a case of association fallacy? ("Server A federates with Bad Servers, therefore Server A must be a Bad Server.")

    Or are there any legitimate problems Server A is causing for Server B?

    [1] Usually because they find defederating to be too extreme for most situations, with too much collateral damage to innocent bystanders...so they use other means to block bad users.

    EDIT: removed FediBlock hashtag

    #Fediverse #ActivityPub #FediHelp

  • Let's try this again.

    Server A users are not posting or boosting anything that is objectionable to Server B.

    But Server A is federating with servers Server B does not like. [1]

    How does this affect Server B in any way? Or, why would Server B cite this as a reason to defederate from Server A?

    Is it merely a case of association fallacy? ("Server A federates with Bad Servers, therefore Server A must be a Bad Server.")

    Or are there any legitimate problems Server A is causing for Server B?

    [1] Usually because they find defederating to be too extreme for most situations, with too much collateral damage to innocent bystanders...so they use other means to block bad users.

    EDIT: removed FediBlock hashtag

    #Fediverse #ActivityPub #FediHelp

    @contrapunctus It's usually used as an indicator that if Server A doesn't see the issue with what Server B are posting there's a greater likelihood that if someone starts posting similar stuff on Server A to what you find issue with on Server B then they won't remove the content / suspend the user / moderate it in a way you deem acceptable.

    With a lot of the more effective moderation being proactive rather than reactive having evidence that a server you federate with doesn't give a shit about content you don't want to see (For what ever reason) means a lot of folks don't want to deal with the likely future moderation headache of Server A.

    But to answer the question I think you're also asking, the only real issue with Server A not suspending Server B is Server B could see replies Server A makes to your servers posts which may or may not be desirable, but again also depends on a load of other factors but for the most part it makes no difference to content visibility.

  • Let's try this again.

    Server A users are not posting or boosting anything that is objectionable to Server B.

    But Server A is federating with servers Server B does not like. [1]

    How does this affect Server B in any way? Or, why would Server B cite this as a reason to defederate from Server A?

    Is it merely a case of association fallacy? ("Server A federates with Bad Servers, therefore Server A must be a Bad Server.")

    Or are there any legitimate problems Server A is causing for Server B?

    [1] Usually because they find defederating to be too extreme for most situations, with too much collateral damage to innocent bystanders...so they use other means to block bad users.

    EDIT: removed FediBlock hashtag

    #Fediverse #ActivityPub #FediHelp

    @contrapunctus this depends on what exactly does "does not like" mean.
    If A federates with B and C, then users on C (those who follow users on A) will see A's posts mentioning users on B on their timelines, and also A's part of conversations between A and B.
    If C is, for example, kiwifarms, then this can put users of B in danger. (This can also put users of A in even more danger.)
    And also "federating and associating with kiwifarms" does indeed allow one to draw some conclusions about those federating, even if it's by association. What does it say about moderator team of A if they federate with kiwifarms, have follower/following relationships with kiwifarms, and do not break them when informed about that?

  • julian@activitypub.spaceundefined julian@activitypub.space shared this topic on
  • @contrapunctus It's usually used as an indicator that if Server A doesn't see the issue with what Server B are posting there's a greater likelihood that if someone starts posting similar stuff on Server A to what you find issue with on Server B then they won't remove the content / suspend the user / moderate it in a way you deem acceptable.

    With a lot of the more effective moderation being proactive rather than reactive having evidence that a server you federate with doesn't give a shit about content you don't want to see (For what ever reason) means a lot of folks don't want to deal with the likely future moderation headache of Server A.

    But to answer the question I think you're also asking, the only real issue with Server A not suspending Server B is Server B could see replies Server A makes to your servers posts which may or may not be desirable, but again also depends on a load of other factors but for the most part it makes no difference to content visibility.

    @wild1145@mastodonapp.uk Thank you for this patient and informative explanation!

  • @contrapunctus this depends on what exactly does "does not like" mean.
    If A federates with B and C, then users on C (those who follow users on A) will see A's posts mentioning users on B on their timelines, and also A's part of conversations between A and B.
    If C is, for example, kiwifarms, then this can put users of B in danger. (This can also put users of A in even more danger.)
    And also "federating and associating with kiwifarms" does indeed allow one to draw some conclusions about those federating, even if it's by association. What does it say about moderator team of A if they federate with kiwifarms, have follower/following relationships with kiwifarms, and do not break them when informed about that?

    @IngaLovinde@embracing.space Thanks for this detailed explanation, it was just what I was looking for. 🙏


Gli ultimi otto messaggi ricevuti dalla Federazione
Post suggeriti
  • 0 Votes
    3 Posts
    8 Views
    @trwnh@mastodon.social sure here are the minutes! I was the only member in attendance 😁 The meeting was adjourned with zero action items
  • 0 Votes
    1 Posts
    7 Views
    "Critical concept: IRIs are opaque identifiers. You cannot infer meaning from the string pattern — only by dereferencing and inspecting the data." [1] This applies to URIs too. Sadly, almost no #ActivityPub implementations use this principle. Multi-tenant servers and simple account portability (with personal domains) would be relatively easy if they did.🙄 It is what it is.../cc @melvincarvalho [1] https://socialdocs.org/docs/concepts/uris-iris-linked-data/
  • 0 Votes
    2 Posts
    8 Views
    @mapache@hachyderm.io it looks amazing! I really wish I could attend.
  • 0 Votes
    1 Posts
    12 Views
    实例(ControlNet Social Space; 简称CSS)搭建的告一段落了,稍微总结一下:1. 选型阶段(#ActivityPub 生态对比)先稍微 review 一下现在已有的 #fediverse 平台,选择以 ActivityPub 作为协议的平台,毕竟联邦的话还是得尽可能有更多人用才行。类似于用于实时通讯的 matrix。然后评估了 #Mastodon / #Pixelfed / #Pleroma / #Misskey / #Sharkey 等,确认不同实现可互联互通(Pixelfed ↔ Mastodon 等)。然后偶然得知 #Threads 也是Fediverse中的一员。然后,研究“主域 abc.xy 显示身份、实例跑在 social.abc.xy”的可行性。结论是这样不靠谱,所以放弃了。。最终决定考虑到Sharkey比起Misskey有一些不错的feature就选了Sharkey。2. 部署与运行按官方文档与 docker compose 在用 #Unraid 系统的 #NAS 上部署 Sharkey。邮件服务器使用free-tier的#Resend 。然后还稍微折腾了一下如何设置管理员。3. 联邦互动与内容获取学会了站内搜索关注远端用户(用 @user@domain 或贴对方资料页 URL 解析)。然后是关注 Threads 用户的实操(前提对方开联邦)。但是这时候实例里没有什么联合,时间线完全没东西,就考虑有没有订阅别人一整个时间线的方法,好像不太可行。4. 存储与图片体积了解到 Misskey/系每用户默认 100 MB 网盘,附件都会落地到服务器(非纯外链)。而且没办法通过引用外链来渲染图片。试了一下本地上传+压缩,发现会自动压缩到webp,勉强还行。6. 二步验证(2FA)故障 & 解决刚才开启 2FA 后出现“authentication failed”,连恢复码也无效,日志报:Endpoint: i/change-password ... {"message":"authentication failed", ...}尝试各种排查均失效,最后只能直接改数据库里的,把 2FA 关掉,然后再重新绑定 2FA和passkey。7. 默认不显示在线状态发现这个需要在用户设置里修改,并且没找到如何让用户默认就是显示的,只能先放弃了。8. 注册与邀请码觉得发放多个一次性邀请码麻烦,想找可重复使用的邀请码。结果发现不行,只支持一次性的,感觉除非自己之后魔改一个web服务用于自动发放邀请码并且自动填写,不然想分享到别的群里,确实有点难度。也没有那种私人邀请的链接。TODO: 未来感觉还是有很多可以做的1. 能够自动探索别的实例的某些方法,找到一些有意思的用户去follow。2. 部署一个chat agent用于增强活跃度,但是又不能感觉像是纯骚扰,如何设计是个问题。3. 做一个方便remote follow的工具