I have to ask: How actively maintained is #BookWyrm as a project these days?
General Discussion
1
Posts
1
Posters
9
Views
-
I have to ask: How actively maintained is #BookWyrm as a project these days?
Apparently, my own instance (bookrastinating.com, which is the second largest one) - recently lost its SSL certificates, and the admin account seems to be inactive.
And the archive/export function doesn't work, either, which makes me rather nervous.
Also, the Patreon Page for BookWyrm as a whole hasn't been updated since 2022.
Gli ultimi otto messaggi ricevuti dalla Federazione
-
Right, which ActivityPub.Space follows and auto categorizes, which ends up as a way for microblog content to make its way into the threadiverse. @strypey@mastodon.nzoss.nz
@silverpill@mitra.social sorry for interjecting 😁
-
-
> @strypey@mastodon.nzoss.nz said:
>
> We could instead try to agree on a separate place for all discussions about fediverse coordination (would it rub anyone up the wrong way if I described this as fediverse governance?). But it does makes sense to discuss a federated network in a federated network, rather than a separate, centralised forum.I keep harping on this one point because it just makes so much sense that it'd be silly not to. The new blood (new software devs implementing AP) always appear on fedi, not some third-party site, first.
To your main point, fedi on Mastodon is all just everybody talking in the same room. Certainly that's why it seems like there's so much meta-discussion about AP.
This isn't the case on the threadiverse, where discussions are segregated/categorized by community.
-
@mariusor awesome! ♥️
-
@pfefferle I added a PKCE task to my todo list:
-
@pfefferle if I'd come up with a scheme for them they would be related to pairs of activityType:objectType entries (instead of a global write), or maybe just the activityType
Ie, Create:Note, Create:Image, Undo, Delete.
-
@mariusor yea, I think the scopes and the PKCE part was the issue!
but finally... 😊
-
@pfefferle love it! 💗
GoActivityPub doesn't really do "scopes" because I couldn't think of a way store the permissions on the server side in a way that doesn't require custom logic to interact with vanilla ActivityPub objects.
