@ajroach42@retro.social it is mod on top of doom source port mod yeah.

it has network play so you can play with some friends.

@moira @ai6yr racks and racks… of black leather jackets

Writing an issue and a PR with an agent that is then reviewed and commented on by an agent feels like that scene in "Real Genius" when the professor is replaced by a tape recorder playing his lecture to a room of student tape recorders recording the lecture: a room full of machines communicating in the place of people. So weird...

@ai6yr So that's, what, five 5090s?

I'm fermenting peppers to make hot sauce. I just tasted the liquid and it's going to be very hot

@tallship thanks for the thoughtful message!

Does Yonder-server support inline images when publishing?

Not as of now. This is something I support on Madblog (and also exactly the way you describe it, with alt text as a visible label etc.), but that's because it's a proper blogging platform rather than a microblogging platform.

Inline images have actually been on top of my mind for a while. And my main rationale is native support for inline MathJax formulas (as proper SVG formulas, not as Unicode shortcuts). But what held me back so far has been the fact that the major platforms out there will anyway render them as attachments at the bottom of the post.

I was unaware that you had been working on this for quite some time, as the repo merely shows the initial commit about 3 weeks ago for the license and I didn't see where it had been migrated from.

The PoC had been sitting uncommitted on my hard drive for a while, but other projects (Madblog and Songhive) took the priority over the past couple of months 🙂

I haven't really thought about whether you're using Mangane as your frontend for #Yonder, but it looks different enough, what with all of the upfront features :)

The frontend is heavily inspired by Mangane/Soapbox, but it also addresses many bugs and design decisions that never convinced me - audio/video attachments (and activities) are handled much better, all the settings are clearly exposed in the UI rather than buried in undocumented JSON/CSS snippets, more Markdown elements are handled properly (like headers and tables) and, most importantly, an admin panel that is a first-class citizen rather than an appendix registered as a separate frontend.

But it supports Mangane out of the box - just upload the zip, then, unlike Akkoma, frontends can also be set directly on user level, so if a user wants to use another available frontend they can do so without having to change the frontend for the whole application at admin level.

Btw, some functionalities of Yonder are only available through the official frontend for now. I added a couple of endpoints to fetch remote context asynchronously - so when you expand a remote post or a remote profile you can see the full remote context, posts, number of followers, likes and boosts, not only the local picture. And also an API to sync pages of posts from a user directly from their instance, so newly seen remote profiles won't look empty.

I designed things in a way to also be compatible with existing Mastodon frontends+apps (even if it meant breaking the paradigm of a few GET endpoints and get them to do async fetch in the background to fill the context).

Existing frontends and apps will also benefit from these features though, but since they were not thought for async remote fetches cases in mind they'll usually require a refresh of the page after 3-4s to see the full context.