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

It’s not finished.

General Discussion
11 9 37

Gli ultimi otto messaggi ricevuti dalla Federazione
  • mobileatom@flipboard.com You've touched on a very interesting point. By the way, I've never figured out whether your Flipboard account will ever be able to see my reply, and to be honest, I'd be very curious to know what a Flipboard user sees when they receive a reply from the free Fediverse...

    Returning to your observation, I see the Fediverse as an integrated ecosystem, but integration doesn't always have to be symmetrical.

    31741512-04f3-4c0f-99f0-8314a4498402-image.png

    To put it simply, Bookwyrm users and Peertube users aren't interested in viewing content from other social networks!
    In the Fediverse, there are programs that focus on one of the three areas in the image above, and programs that occupy two or more reference areas.

    For example, I find the fact that Mobilizon users can't see Friendica events much more problematic than the shortcoming you noted on Pixelfed...

    Pixelfed certainly "looks" like a social network, but it's primarily a place where users share their "personal art galleries."

    While I'm not a fan of dansup@mastodon.social, I recognize that he's making great strides to increase the interoperability of his creation, and Pixelfed has grown better than any other software in the Fediverse on three key levels:

    improving interoperability creating a beautiful and ergonomic app brand identity

    I'm sure he'll find a way to make text content visible in the future, but honestly, right now, it doesn't seem like a priority for Pixelfed's development and success.

    That said, your observations are a very interesting starting point for the development of software and interfaces in the Fediverse.

    read more

  • Agreed that Mastodon 2022 / Bluesky 2025 is far from a precise correspondence! But while fedi's ecosystem is very diverse in some ways (and I agree that's a fundamental asset), it's much less diverse in others. Similarly the ATmosphere ecosystem is very diverse in some ways.but much less diverse in others. So my guess is that most fedi projects have an analogue in the ATmosphere -- not as far along because it's newer, and we'll see how many continue and how many wind up as dead ends.

    Of course there are plenty of exceptions. Off the top of my head, I can't think of ATmosphere analogies of Bonfire, Frequency, or the friendica/Hubzilla/(streams)/Forte family. Then again there are also ATmosphere projects where I can't think of any fedi analogy: Blacksky, Gerrm, XBlock labeler, Anisota, Semble (a sense-making app). And some of the ways the ecosystems aren't diverse mirror each other; for example both are very Europe/US/Canada-centric.

    @informapirata

    read more

  • Is Pixelfed sawing off the branch that the Fediverse is sitting on?

    https://ploum.net/2025-12-04-pixelfed-against-fediverse.html?utm_source=flipboard&utm_medium=activitypub

    Posted into THE FEDIVERSE VS. CORPORATE SOCIAL MEDIA @the-fediverse-vs-corporate-social-media-mobileatom

    read more

  • I've just updated my instance, to version 2.85 👍 🎉
    You don't know Snac? But you should: https://codeberg.org/grunfink/snac2
    A simple, minimalistic and well documented instance server written in C, no database needed, totally JavaScript-free, no cookies either, not much bullshit.
    Do you see this post? It comes from a Snac server.
    The Fediverse is larger than you assume 😉


    read more

  • @AdamStuartSmith thanks!

    happy for every feedback and/or improvement requests.

    read more

  • @pfefferle Thanks, looks good, I'll work through it and let you know how it goes! 🙏

    read more

  • Bot accounts on should be able to be flagged as "do not cache".

    Having to hit F5 to reload the page every 30 minutes like as if it was still the early 2000s or something to play @fediplayssnake

    read more

  • „Is Pixelfed sawing off the branch that the Fediverse is sitting on?“

    Interesting article but I disagree with the premise:
    The protocol does not demand to display all messages.
    Actually, it doesn’t make any sense even.

    When I use , I do that to see pictures only. That’s the whole point.
    If I want to see more, I have to use a more generic platform, like .

    https://ploum.net/2025-12-04-pixelfed-against-fediverse.html

    read more
Post suggeriti
  • 0 Votes
    10 Posts
    24 Views
    @juergen @nick @crossgolf_rebel @roblen wir hatten vor ein paar monaten mal ein problem mit vereinzelten posts die nicht veröffenticht wurden und haben das an den umlauten in den tags fest gemacht... vielleicht ist es zeit das nochmal zu verifizieren...
  • 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
    15 Posts
    41 Views
    trwnh@mastodon.social Yes, you're right. There are nuances and situations where you would explicitly not want to inherit the root object's context. I am dealing with the typical day-to-day use case of replying to an object with the expectation that is be part of the same existing context. However I am more than happy to make this clear in the FEP and spell out alternative situations where context inheritance would not apply. The situation I found myself in was one where anybody can (and does) include whatever context they want. In that case, it's difficult to determine whether disparate contexts are actually referring to a common set of the same objects, or whether they were disparate on purpose (i.e. a fork.) To that end, it meant that as a receiver there was no guarantee that any contexts I'd be sent would map to any contexts I know. Strict root-level inheritance for the common use-case would at least disambiguate a lot of this.
  • Man I'm going to miss #TikTok

    Uncategorized tiktok
    4
    0 Votes
    4 Posts
    21 Views
    @Gina ouch. That hurt so much I had to immediately rinse it away with a Weird Al cover.https://www.youtube.com/watch?v=C-CG5w4YwOI