fabio

joined 11 months ago
[โ€“] fabio@lemmy.manganiello.tech 1 points 1 week ago (1 children)

Initially Webmentions and AP reactions were rendered on separate panels (with the Jinja rendering templates provided by the webmentions and pubby libraries respectively), but then I found that a bit confusing and cluttering, because there were basically two comment sections with two different time-sorted lists of threads. But if people prefer the other way around I could also add it as an option or a filter toggle ๐Ÿ™‚

 

#Madblog now comes with support for federated author replies and reactions too. All from #Markdown files, as usual.

At the current state it's only single-user, but I'm working on a multi-user implementation. It should be available as soon as I have a proper implementation for the ActivityPub Group actor (similar to what WriteFreely already does, where you have a Group @blog actor that aggregates post from multiple Person actors). That would also unlock full compatibility with Lemmy/NodeBB and other threadiverse implementations. But it takes a while to get done right - and a multi-user set up is also a design challenge when your selling point is to have a blog running on a single folder with Markdown files.

About a free instance, it's not currently available (you'll need your own domain and host and then you can just spin up a Docker container), but AFAIK YunoHost is considering adding it to their offering.

[โ€“] fabio@lemmy.manganiello.tech 2 points 3 weeks ago* (last edited 3 weeks ago) (2 children)

I'll test it just in case by giving @fabio@manganiello.blog a shout

--EDIT--

Interesting, this actually looks like a bug in my implementation. It's not about Lemmy or Mastodon (at least in the case of receiving loose mentions), it's about the REPLY type that was ignored. Should be fixed now ๐Ÿ™‚

That's right, there's no pagination on the outbox right now - it's just a few text files anyway so I didn't bother to implement it yet. But it's on my (very short term) radar. The RSS/Atom feeds are already provided over /feed.rss and /feed.atom routes respectively though. About embedding the whole object vs. a reference, that can be configured via activitypub_object_type. It defaults to Note, so the whole content is included, but it can also be set to Article - in that case only a reference to the object is rendered, similar to what WriteFreely does in its latest implementation.

[โ€“] fabio@lemmy.manganiello.tech 3 points 3 weeks ago* (last edited 3 weeks ago) (3 children)

It doesn't fully work with Lemmy yet, but it should work from a Mastodon/Pleroma account.

Full federation with Lemmy is still an open point because it requires me to properly implement a Group actor for full threadiverse compatibility. From what I've seen so far even Akkoma hasn't implemented it properly.

 

Using #Madblog as the easiest way to spin up an Indieweb/ActivityPub-compatible blog.

Zero db, zero JS, entirely hosted on text files.

 

Using #Madblog as the easiest way to spin up an Indieweb/ActivityPub-compatible blog.

Zero db, zero JS, entirely hosted on text files.

 

Using #Madblog as the easiest way to spin up an Indieweb/ActivityPub-compatible blog.

Zero db, zero JS, entirely hosted on text files.

 

Using #Madblog as the easiest way to spin up an Indieweb/ActivityPub-compatible blog.

Zero db, zero JS, entirely hosted on text files.

blog:http content is usually dynamically managed via asynchronous requests.

Your best bet is to use the Network tab and filter the actual request made by the browser when it tries to expand the resource.