クライアント、いろいろ試してみてるのだが、SocialHubがだいぶ使いやすいな
以下こんなのがあるといいなリスト
・スクリーンネーム領域の表示拡張
⇒なるべく全文表示されるように。
アカウントと表示名の組み合わせでどなたか
判別してるところがあるので。
・フォント指定
・投稿の言語設定
⇒設定がないとBluesky上でフィードに
乗らないことがあるので。
・fedibirdリアクション対応
⇒fedibird民としては是非…
#SocialHub
🫧 Social coding commons
@smallcircles@social.coop
Welcome social coder, To this self benefit center, Where we earn #socialweb. Concept is simple.. Bring something of value, Others make it grow, You self-benefit, Our synergies flow.. Commons 💕 unite! Participate in our channels, Reach out, embrace others, Follow passions and dreams, #Dreamwalk bright future, To realize them.. Invest in #SX now! Gift one 🪙 of #humanity, Earn 🪙🪙 cts of #freedom.. 💃🕺 #peopleverse shall rise! CC BY-NC-SA, Humane tech community.
social.coop
Replying to
on social.technoetic.com
@steve@social.technoetic.com
You might be interested to check out my posts around the concept "Community has no boundary" I talked about 5 years ago, e.g. in this topic: https://socialhub.activitypub.rocks/t/standardizing-on-a-common-community-domain-as-ap-extension/1353
When I was still facilitator of #SocialHub I claimed that it wasn't a community in any really sense, with mostly people driving by on self-interested motives. It was just a discussion forum, where a poor commons janitor (me) had to do the unthankful volunteer upkeep.
"Expectation mismatch" plays an important role when anyone mentions "community". A "community-driven #FOSS project" is partly the formal governance that is in place, but mostly implicit cultural aspects. Knowing what you can expect is important, to not get disappointed.
A #fediverse instance to me isn't community. I only use the Home timeline.
As we navigate fedi we 'weave' in and out of community seamlessly, without realizing it. A rich concept of inter-community social networking is possible, I think, but it should be carefully designed.
🫧 Social coding commons
@smallcircles@social.coop
Welcome social coder, To this self benefit center, Where we earn #socialweb. Concept is simple.. Bring something of value, Others make it grow, You self-benefit, Our synergies flow.. Commons 💕 unite! Participate in our channels, Reach out, embrace others, Follow passions and dreams, #Dreamwalk bright future, To realize them.. Invest in #SX now! Gift one 🪙 of #humanity, Earn 🪙🪙 cts of #freedom.. 💃🕺 #peopleverse shall rise! CC BY-NC-SA, Humane tech community.
social.coop
Replying to
@dmathieu@fosstodon.org
@dmathieu@fosstodon.org
NodeInfo isn't part of #ActivityPub and neither is it required to be implemented by fedi software.
What #fediverse is and isn't is an interesting question. Does following between actors make the software on both ends part of the fediverse? Should a fediverse app support #microblogging? Be compatible with Mastodon?
Perhaps being part of fediverse means if 2 independent 3rd-parties are able to interoperate with each other? Does that require sending Follow msgs?
If someone has a federated Product catalogue that federates with itself and a 3rd-party Order delivery service, is it part of the fediverse? Even when no Follow is sent?
It is undefined what being part of the fediverse means. There used to be a Federated Network Association (Feneas) as a major dev community besides #SocialHub, which defined fediverse as any software that implemented AP, #XMPP, or #Matrix protocol.
@steve@social.technoetic.com even wrote that nothing even truly implements AP, and I tend to agree.
https://www.stevebate.net/nothin-implements-activitypub/
🫧 Social coding commons
@smallcircles@social.coop
Welcome social coder, To this self benefit center, Where we earn #socialweb. Concept is simple.. Bring something of value, Others make it grow, You self-benefit, Our synergies flow.. Commons 💕 unite! Participate in our channels, Reach out, embrace others, Follow passions and dreams, #Dreamwalk bright future, To realize them.. Invest in #SX now! Gift one 🪙 of #humanity, Earn 🪙🪙 cts of #freedom.. 💃🕺 #peopleverse shall rise! CC BY-NC-SA, Humane tech community.
social.coop
Replying to
on social.coop
@silverpill@mitra.social @raphael@mastodon.communick.com @julian @mariusor@metalhead.club
Btw, damn we should've caused this entire discussion thread to somehow flow to #SocialHub to have it in the archives. Instead of on "now you see me, now you don't" channel. Peekaboo. 🫣
https://social.coop/@smallcircles/116141469199837056
Here today, gone tomorrow, who made notes? The post-facto interoperability leaders did. Those who happened to be around at the right time to hear things being said on the grapevine.
We need a proper Grassroots standardization process, and a Grassroots open standard that is able to healthily evolve. The good organization of this is just as important as the technical robustness of the protocol, which is the solution artifact at the end of the open standards cocreation pipeline.
🫧 Social coding commons
@smallcircles@social.coop
Welcome social coder, To this self benefit center, Where we earn #socialweb. Concept is simple.. Bring something of value, Others make it grow, You self-benefit, Our synergies flow.. Commons 💕 unite! Participate in our channels, Reach out, embrace others, Follow passions and dreams, #Dreamwalk bright future, To realize them.. Invest in #SX now! Gift one 🪙 of #humanity, Earn 🪙🪙 cts of #freedom.. 💃🕺 #peopleverse shall rise! CC BY-NC-SA, Humane tech community.
social.coop
Replying to
on mastodon.social
@reiver@mastodon.social @thisismissem @mfru@mastodon.social
I made a diagram yesterday that contrasts #ActivityPub and #SolidProject that is I think interesting to consider.
In the past I've been very active on the Solid forum, and tried to get a collab going with #SocialHub community. A number of points that existed then, are still issues today I think.
Like, though anyone could participate in the standards process via chat, the Solid team and Inrupt were not really interested in their community, hardly giving attention while people were building interesting stuff there.
Also at the time basically all available code was Javascript, making Solid uninteresting or hard to access for other language devs.
But I think biggest issue was that Solid didn't know what it was. It was positioned as 'personal data vault' on the landing page then (but not using this term), but was 'secretly' TBL's desire to reboot the #SemanticWeb. The new web would be all 'Solid apps'. But the adoption strategy for that didn't exist.
You've seen all posts