The shocking part was less about Maven’s methods or lack of ethics, and more along the lines of “How the fuck did they do that?!”

Bonfire Classic probably does just do microblogging, but the modularity of the platform would allow someone to build in support for that.

Given that one of the Flavors is Group-centric, it might already be possible.

Woah, thanks for sharing!

We actually already have some interviews recorded, it’s just that some of the unedited talks are two hours long. But yes, this is something we’re actively working on!

I loved the voice of the friend who emphasizes the "sh"s :)

I assume you mean Laurens from the Fediverse Report. He’s from the Netherlands, and has a wonderful accent and demeanor.

Getting major NPR vibes from this one!

This one is S-tier!

Thanks for the feedback, I added a big quote from Radio Free Fedi to call more attention to that effort.

Fair point, I should probably clear that up. Static site generators typically work through a process that builds pages for you on the fly, based on what’s in the folder. However, for it to be available on the Internet, you’d still need a server to run the program, so that you can generate those pages.

You’d probably want to host it on an actual server, if you want people to be able to access it when your laptop isn’t on. The documentation seems pretty good, though, it should walk you through the steps: https://simonrepp.com/faircamp/manual/installation.html

Architecturally speaking, Nostr is really cool, and has some great ideas. I think their approach is way better than what we have with instances, but discovery seems to be a fair bit worse, and most of the landscape seems to just be right-wing crypto bros. I’ve also heard from some people developing for Nostr that it’s “easy to learn, but messy”, in terms that you’re basically always trying to figure out compliance with various NIPs, rather than just following a particular protocol standard.

I think the Fediverse would absolutely benefit from a system that didn’t tie user accounts to instances, and made use of a similar relay system.

The main thing is that their frontend was built for whatever APIs their own platform supported. You can theoretically adjust the code to use the Mastodon API instead, but it can actually be kind of a tedious process to change everything over.

It’s probably easier to mod an existing frontend to look and act the way they want, or write a new one from scratch.

The other thing is, it’s still a really new instance, and kind of started as a community experiment. While it looks like it could be a big next step for Pebble, they’re probably more interested in testing the waters before doing any serious committed development on it.

The one that really irks me now is that Nautilus in Ubuntu doesn’t show thumbnails for PNG images in the file selection dialog. It’s such an ass-backwards change that I’m legitimately shocked.

Yeah, I get that it’s not that new, especially since it’s a rebranded fork. But, as a fediverse project with its own brand and design sensibilities, it’s relatively new, especially compared to Mastodon.

Unfortunately, I’ve used the Antennas for like two months, and they’re janky. The “non-retroactive data fill” point that you make is only partially true, and seems to mostly apply to filters pertaining to a collection of users, or a collection of servers as a data source. It’s a confusing UX papercut. Worse yet, my Fediverse Devs antenna example has been around for two months, and barely produces anything most of the time.

I don’t believe that an “official branded app” is strictly necessary. What I meant was more in line with “Firefish could really use apps developed for its features specifically.” Sadly, Misskey compatible apps continues to be a wasteland compared to the plethora of Mastodon ones.

The whole “the flagship instance is a sandbox test instance” is kind of a sometimes-true sometimes-not situation. It’s definitely less stable now than it was two months ago, but that kind of messaging and expectations management didn’t seem to really happen until sometime after the CalcKey migration.

And yeah, proper group / community federation with Lemmy is a huge deal! I’m looking forward to what Pixelfed is doing with Groups, as they look somewhat similar, and aim to maximize compatibility while providing good management tools.

Wow, thanks for the great in-depth feedback! 🤩

Yeah, there’s definitely other areas I could’ve delved into, like Public Clips or MFM or pagebuilding. These in-depth reviews are challenging, due to trying to strike a balance between features and actually getting something published. Most articles of this nature takes me weeks, sometimes even a month or more.

The UI definitely has a learning curve, too, but as a veteran Fedi user, it suited me just fine. I’ve dealt with far, far worse 😂

The instability really bums me out. I’d like to think that things are slowly improving, but the lack of transparency (and frankly useless error messages) make it really hard to triage where the problem is and forge a path forward. The lead dev has also been sick recently, and suddenly is not very active online.

Finally, I think Firefish takes part in a long tradition of Misskey forks, where a half dozen systems all branch off of each other. It’s a shame that more of them don’t collaborate on the same platform, leaving many devs to cherry-pick across forks. I wonder sometimes whether this hurts development more than it helps.

What’s weird is that the site is still up and works fine. My guess is that maybe the developer lost interest, or was busy with other things.

Yeah, I agree. Something that I’m tinkering with right now involves removing the comment form found at the bottom of articles, and replacing it with instructions on how to federate with the conversation tree instead.

Yes, the reader’s guide is here: https://wedistribute.org/2023/09/follow-wordpress-on-fedi/

Sure, as an open source project, everybody owns the code. But, Automattic is the corporate arm directly involved with the project, employs many of the project’s developers, and holds the trademark.

Interesting. Are Lemmy users themselves not Person/User actors? It seems like Lemmy might benefit from allowing those types to be followed, or at the very least, viewed.

Would it at all make sense or work for wordpress bloggers to “at” lemmy communities in the same way masto users have to in order to post to lemmy? It would be just like hashtags, which I presume could also work over on mastodon etc?

It’s an interesting thought, but: as an author, I have no pre-emptive concept of who is going to be reading my posts, or which community I should share something to specifically. I think it would be easier to just make certain kinds of Actors and activity types visible to Lemmy, so that those posts can then be reshared to whatever communities that somebody cares about.

If this diagram were actually true, pretty much every platform in the space would have died years ago.