前澤さんのことは「宇宙からお金をばらまく金持ち(ちがう)」というくらいの印象しかないんだけど、#Facebook #Meta の日本での詐欺広告への対応はたしかにひどいかったし、そこに対する問題意識には共感する。
#mixi2 も #タイッツー も自分は全然アクティブじゃないけど、それが生まれた根底には #Mastodon
のそれと重なる部分もあるような気がしているので、 #ActivityPub
という標準規格が存在する今ならもういっそのこと全部 #Fediverse
⁂ になっちゃえば良いのにと自分は思っていて、だからこそ、この
の森(⁂)の中の #VivaldiSocial
という木にとまってピーチクパーチク言っているわけだけど、まあそんなに都合よく
の森が広がるほど世の中あまくないなあというのはこの2年〜3年であらためて感じてもいる。
まあでも森の大きさを気にするより、雑木林くらいの規模でも近くの良さげな木の様子を見に行くだけでも楽しいし、それがちょっとずつでも広がっていってる実感もあるので、他の独自規格の SNS がどうなろうとあまり気にならなくなっている(多少マーケティングにも関わる仕事をしている身としてそれはどうなのという気持ちは多少あるにせよ) ![]()
#ActivityPub
に対応するなら、心のなかで応援してあげてもいい
⁂
前澤友作氏「一緒に国産SNS作りませんか?」とXで呼びかけ 掲げた「理想」は5つ、動機は詐欺広告か(要約) - ITmedia Mobile
https://www.itmedia.co.jp/mobile/articles/2508/11/news021.html
The delightful #ActivityPub development list has been renamed. Now the 3 fedi-related lists are:
- delightful-fediverse-experience
- delightful-fediverse-clients
- delightful-fediverse-development
The #fediverse development list has largely been stripped of non-developer resources, which moved to fediverse experience.
The fediverse development list should now be reorganized to be most useful to the dev crowds who wanna join the fedi adventure.
Resources missing? File an issue or PR.
A cool thing I discovered yesterday with the #activitypub plugin for #wordpress: you can change the blog username without losing your followers nor your post history.
For my blog I initially chose @blog@ikacode.com, but later realized that only the first part of the handle would show in posts ("blog").
I changed it to "ikacode", to have @ikacode.
After 2 minutes I searched the new handle in Mastodon, and opened the profile.
Everything was there.
The former handle then disappeared.
NOTE: Previous references to the initial profile in posts (like in this one) don't link to the new one but it's fine.
Thanks @pfefferle and all the contributors for this great plugin!
Content warning:<p> <p>For some reason I was sending an invalid value with the <code>alg</code> property, and, uhhh, Matthew, you really should have paid attention to Section 3.3 under each algorithm where it states the possible acceptable values:</p><ul><li><code>rsa-pss-sha512</code></li><li><code>rsa-v1_5-sha256</code> </li><li><code>hmac-sha256</code></li><li><code>ecdsa-p256-sha256</code></li><li><code>ecdsa-p384-sha384</code></li><li><code>ed25519</code></li></ul><p>I only have support for <code>rsa-v1_5-sha256</code> (incoming or outgoing) at the moment (as does Mastodon), but finally I have my first successful signed RFC 9421 POST requests to both a Mastodon instance and Wordpress ActivityPub Plugin instance. Those plugins are handling the covered components that I chose to use...</p></p>
For some reason I was sending an invalid value with the alg property, and, uhhh, Matthew, you really should have paid attention to Section 3.3 under each algorithm where it states the possible acceptable values:
rsa-pss-sha512rsa-v1_5-sha256 hmac-sha256ecdsa-p256-sha256ecdsa-p384-sha384ed25519I only have support for rsa-v1_5-sha256 (incoming or outgoing) at the moment (as does Mastodon), but finally I have my first successful signed RFC 9421 POST requests to both a Mastodon instance and Wordpress ActivityPub Plugin instance. Those plugins are handling the covered components that I chose to use fine.
Improved the setup steps for a new #ONI instance.
Initially it wasn't possible to operate everything without manually editing some json files, but now everything works with vanilla client to server #ActivityPub activities triggered from a CLI helper.
Now I just need to put it all into a document.
@oldrup @oldrup.dk I did the same mistake and named my blog @blog before noticing the handle wouldn't show. Since I have some followers, I don't want to change it anymore now, but I'll remember for next time I install the #activitypub plugin!
I also wondered about what happens when you publish a test post and delete it afterwards. It looks like it remains visible on the #Fediverse.
@oldrup.dk - Test posts are federated right away. That is fine, but something to keep in mind if there are already followers. Especially as it is not obvious to me, if it is possible to delete already federated posts.
- Using identical tags in WordPress and in the instance bio, makes the tags (on mastodon) link to the tag archive on the website. Handy.
If you follow @oldrup.dk, with have some patience, it's very helpful to me. Feedback welcome.
A short(ish) guide to , applicable to basically any website (including static ones . . . sort of).
I admit I got most of the way through this for alisfranklin.com, before scrapping it and going with a more straightforward crossposting script (with the ability to implement something along these lines for importing comments). Mostly because as soon as you start getting into anything involving following, receiving interactions, etc., you start having to mess around with digital signing and a bunch of other stuff I couldn’t be arsed with. Might I go back and have another crack at it at some point? Maybe! But . . . not for now.
There's Babylonian confusion of speech in all #ActivityPub related discussions that occur across the #fediverse. We have the #SocialWeb protocol specification itself, then the reality-on-the-wire where gaps and optional technology choices are implemented. And where protocol decay and post-facto #interoperability (follow-the-Mastodon) murky the waters. Leading to misunderstandings, wrong expectations, etc.
An example is in how we talk on Nomadic Identity:
https://socialhub.activitypub.rocks/t/nomadic-identity-for-the-fediverse/2101/96?u=aschrijver
In the 2nd topic above I describe the conceptual architecture as:
> "a distributed network of addressible actors for the exchange of social activities”
There is a full domain model there, and this conceptual architecture conveys the full promise and potential for #ActivityPub based social networking. All the various gears and mechanics that make the protocol tick have a place in it.
It is a bit of a meta-model, as it is not directly basis for impl in code, but input for specs.
As an example, a recent related topic by @lax on #SocialHub mentions clearer layering of the protocol stack..
https://socialhub.activitypub.rocks/t/layered-activitypub/5449
In another recent topic on #ActivityPub C2S I mention a need to discern between conceptual architecture and implementation. "Server" and "client" aren't part of the conceptual architecture, and likely need a different place in the domain model on that basis. They are different kind of abstractions than e.g. an "actor".