@shoq when it comes to groups, there are two parallel implementations in @nodebb:
"user groups" which — true to name — is a group of users. They can be mentioned in posts and will be notified thusly.
Group chats, which function almost exactly like "mentioned-only" visibility in #mastodon. Users are added to the group and messages exchanged only show up to the users in said group.
Is there a third use case you'd like to see, or is it covered in the above?
Had a shower thought / question about #ActivityPub. Would it be possible to develop a federated server without a media cache? I believe that it should be as long as the server is configured to proxy media requests back to the original source. This would, of course, greatly increase latency and decrease reliability (media is lost if the remote instance goes poof). But in exchange, it dramatically reduces the storage space needed to run an instance. That would reduce the cost of operating an instance on cheap VPS services. I can also think of a couple use cases around the current push to simplify instance hosting.
I've been musing passively about how I can develop locally while still making #ActivityPub requests in order to test with real HTTP requests, and was pretty close to just deploying my code on a test subdomain (and then making the call to my #Mastodon server — crag.social), but then realized I could just stand up two #NodeBB instances on my machine and have them gab to each other instead
As more and more instances are providing multiple services under the same management, we need a term to talk about this type of arrangement. A Fediverse Galaxy is a collection of federated software that is provided by the same admin or collective.
https://github.com/LemmyNet/lemmy/issues/2937 the Lemmy devs' response to someone asking for machine-readable HTTP API docs is even worse than Website Boy's 😒 guess they don't want anyone writing clients for it
Hi Fediverse admins / devs! I've got a question about instance software.
Up until now, I've been running a fork of glitch-soc that has served me well. Unfortunately, however, I'm starting to run up against some of Mastodon's limitations and the effort to maintain my own fork is just too much. (seriously, fuck Rails and especially Webpacker :blobfoxangry:) I'd like to switch instance software to something with more features out-of-the-box. I'm considering Calckey, but I don't have any experience with it or any other Misskey derivative. The feature set looks great on paper but I'd like to hear from someone who has actually run it (or at least seriously evaluated the software). I'd greatly appreciate any and all input! I'm especially curious about these questions:
The "Fediverse Software Comparison" table has a few mistakes in the Mastodon and glitch-soc columns. They're minor, but it makes me wonder if that table is really trustworthy? The table is based on personal knowledge
just ran across notes from the #FediDev meeting that happened in April. Glad to see initiatives like this happening throughout the edges! https://fedidevs.org/notes/20230410 thanks to @gabek for making this available
The decision to use Ruby for Mastodon was a poor choice, to put it mildly.
The diagram below shows relative energy consumption, with values normalized to the most efficient one. So C, as the most energy efficient, has the value 1.
Initial federated contact made! My local dev instance has just made its first calls to a remote #Mastodon instance (via #WebFinger discovery) to retrieve a remote user account!
One small step for #NodeBB, ah... also one small step for the #Fediverse I guess.
My first #fediverseBot is finally live! @LaDiaria posts news from the 🇺🇾 newspaper @ladiaria directly from their RSS feed. As bots go, it's really simple but the reason I'm so happy is that's running from my own implementation of an #ActivityPub compatible server made with #Laravel and #PHP. There's still plenty of work to do, but for now, the basics are there and I wanted to test it in the wild.
Why is every mastodon server out there flooding me with Delete Activities about users my server has never heard of?? And on a technical note, who is signing those activities? Is it the private key of the deleted user?
Yesterday night I added proper hashtag support and autolinking to my #ActivityPub server. I'm still thinking about the best way to handle mentions since the twitter-text-php package supports the @\username format but I need to support @\username@\server