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

five beliefs – burning web

Fediverse
1 1 17

Gli ultimi otto messaggi ricevuti dalla Federazione
  • Oh hey, thanks! You saved me from needing to crosspost it here :laughing:

    ... which... is frickin' ironic, isn't it, because we aren't at the point where we can crosspost between instances yet...

    read more

  • cross-posted from: https://community.nodebb.org/post/106480

    NodeBB v4.8.0 — Crossposting, federated moves, API changes, and bug fixes!

    Hello from Canada! :flag-ca:

    We're a week behind the planned release, but we're dropping v4.8.0 today, containing some changes to our ActivityPub handling, along with a new API route, and bug fixes.

    Crossposting

    As briefly introduced in my earlier topic on cross-posting, NodeBB v4.8.0 supports cross-posting of topics between categories. More importantly, it means topics from other remote categories can now be added to local categories, which is another way to bring conversations to your local users.

    Unlike before, where administrators were the only ones allowed to move topics from cid -1, cross-posting is available to all local users. If you see a topic on the fediverse you'd like to cross-post to a local category, just hit the cross-post button (it's a button with a little upward-right pointing arrow), and share it with other users on your forum!

    2283791f-ba05-46fe-af32-4bf4f4915946-image.png

    When you cross-post, it also shares the topic with all of your followers from outside of your forum.

    cbeadd68-cfd0-4d05-903c-85c8f821b553-image.png

    Federated topic moving and removals

    This was actually released with v4.7.0 but was improved slightly in the intervening versions. NodeBB now follows the Draft FEP f15d: Context Relocation and Removal and will publish Remove activities when a topic is moved to "Uncategorized", and Move activities when moved to another category.

    Developers of other ActivityPub software looking to implement similar mechanics are advised to read the FEP and provide feedback here: https://activitypub.space/topic/86/fep-f15d-context-relocation-and-removal

    Other technical debt and bug fixes Post ownership websocket call was migrated to a v3 REST API call Notifications had issues when user display names contained commas Piefed v1.5 supports emoji from remote instances; incoming custom emoji from Piefed are now handled Nodeinfo fixes for if a NodeBB instance is not actually federating (has AP turned off)
    read more

  • @die4ever@thefedi.forum hi from another NodeBB! (god this will never get old)

    NodeBB maintainer here. Glad to hear you're enjoying the software! I really tried to make it so that federation is rather seamless. There's a lot of work to be done with respect to discovery, so it'll only get better over time 🙂

    read more

  • That all sounds pretty gloomy, on the whole.

    If Lemmy.ml's founders didn't have such a controversial reputation, I'd be a lot more sanguine about all that...

    read more

  • You seem more familiar with Mastodon than me:-).

    I think there’s another wrinkle, too, about PF communities not showing up in Lemmy feeds unless a local instance user has subscribed to them.

    Mostly this is just how the Threadiverse is designed to work. PieFed might do differently, but Lemmy has always been this way. That said, it is reportedly about to get worse/better (at the same time) as the choice as to what communities will show up for new instances will now fall under the centralized authority of Lemmy.ml directly - so e.g. anything defederated from it will no longer be considered part of the Threadiverse, at least by default (although that's easy enough to override by adding the community manually). It is notable though that previously I believe zero communities were added by default, at least automatically (and yet when that update deploys and some do, it will only get more confusing to find out why some instances, decided by Lemmy.ml to not be worthy by their criteria, will not be part of that). It is also far more confusing than I let on here, and in ways that I do not fully know myself, since just because an instance is "aware" of a community does not mean that it is "subscribed" to it.

    There is simply no way that the federated model is anything at all like "just using email", as people claim. The defederations make it an entirely different thing where instead of having a fully connected graph we have only a partially connected one.

    read more

  • Oh this is cool!

    read more

  • Lemmy and PieFed are both part of the Threadiverse though, whereas things like Mastodon, Loops, and Friendica are not. Since none of the latter have “communities”, e.g. in Mastodon you have to follow “people”, rather than community topics to be discussed by many people.

    Okay, but Mastodon does have a general feed I think, similar to the "ALL" stream. Doesn't it also allow following hashtags, too?

    Even between PieFed and Lemmy there is a lot that can be sent out by the former that the latter simply is not capable of receiving properly, like hashtags, polls, user and community flairs, and so on.

    I think there's another wrinkle, too, about PF communities not showing up in Lemmy feeds unless a local instance user has subscribed to them.

    read more

  • Lemmy and PieFed are both part of the Threadiverse though, whereas things like Mastodon, Loops, and Friendica are not. Since none of the latter have "communities", e.g. in Mastodon you have to follow "people", rather than community topics to be discussed by many people.

    These fundamental differences can make it difficult to share content between platforms, even though it can be done. e.g. I think in Mastodon (iirc, I have never used it personally) you have to tag the community name as if it were a person.

    Even between PieFed and Lemmy there is a lot that can be sent out by the former that the latter simply is not capable of receiving properly, like hashtags, polls, user and community flairs, and so on. Likewise some input can be filtered too, e.g. votes prevented on a PieFed community not only based on if someone is banned or not (from either the instance or the community itself) but whether they are a subscribed member of that community, if the community rule is set up that way (e.g. women's communities where men might not bother reading the rules, say by just seeing something while browsing by All, and attempt e.g. vote manipulation, even/especially unintentionally).

    So anyway, despite all the differences, PieFed and Lemmy at least are operating on roughly the same wavelength, but e.g. Loops is an entirely separate thing.

    read more
Post suggeriti
  • 0 Votes
    11 Posts
    4 Views
    @rolle This is why I’m on the Fediverse, bridging with BlueSky. Because I’d be happy to federate with them, if they’d open up as standard. But they don’t. They want to keep to themselves unless someone explicitly says they want to bridge to Fediverse. That’s the reason I don’t really trust BlueSky. Did you see the European PDS, EuroSky?
  • 0 Votes
    6 Posts
    19 Views
    @stefano Ennio Morricone was an amazing composer!
  • 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的工具
  • 0 Votes
    1 Posts
    14 Views
    Have you heard of the #Threadiverse, and important part of the #Fediverse? If not: Julian Lam (@julian@activitypub.space) is coming to FediForum next week and will talk about: Threadiverse improvements. Join us!FediForum