# orderedItems[].object.content
:goose_honk:

# orderedItems[].object.content
I haven't posted in a while as I've been really busy at work, but I should be able to resume development soon.

# orderedItems[].object.content
@gekidasa@fandom.ink I answered here: https://todo.sr.ht/~tsileo/microblog.pub/126

# orderedItems[].object.content
@gabriel@fediverso.publicar.uy (cc @sean@opalstack.social) I did try to tweak the in-memory cache settings, but it's been a while this was pushed.

When was the last time you updated your instance?

# orderedItems[].object.content
@kevinisageek@kevinisageek.org Sorry for the late reply. I see you went ahead and it seems to work correctly 😺

# orderedItems[].object.content
Recent #microblogpub updates:

fixed "JSON LD signature" context

support for running server on sub.domain.tld while being reachable @domain.tld, doc here

usual bunch of fixes and improvements

The signature issue may be impacting a lot of instances, so it is recommend to update as soon as possible.

# orderedItems[].object.content
@paulox@fosstodon.org on my side, yes, but I think the scope is a bit different.

But it does look interesting and I follow the development a bit.

# orderedItems[].object.content
@LeonardoDiOttio@mastodon.social it has support both "Notes" and "Articles".

You can see how articles look like here: https://testing.microblog.pub/articles

# orderedItems[].object.content
@a13x@mastodon.social You can try touch data/_theme.scss to unblock you.

It should have been created automatically, I will double check if there's a bug there (or maybe it was a permission issue).

# orderedItems[].object.content
Recent #microblogpub updates:

New task to import follows from Mastodon export

New option to hide shares/announces from a specific actor

As usual, small fixes and tweaks

Improved OAuth 2.0 support

Improved ActivityPub C2S (client to server) support (more on that later!)

New YunoHost update available

Happy holidays! 🎅

# orderedItems[].object.content
@PresGas@freeradical.zone yes, you can block actors via the admin UI, blocking domains is done via the config file: https://docs.microblog.pub/user_guide.html#blocking-servers

# orderedItems[].object.content
@me@m.nevkontakte.com Thank you! Editing support is planned, but the feature is a bit tricky to implement. It will land at some point!

# orderedItems[].object.content
@tofeo@microedit.ion.ovh Hey, it should be in /opt/yunohost/microblogpub.

# orderedItems[].object.content
@charadon@mb.iotib.net Hey!

About following hashtags, there's no way to achieve that with ActivityPub (if you talk about what Mastodon supports, following a hashtag only works within an instance and it does not federate).

About providing a RSS feed for the stream, that seems reasonable, I will add it to my todo list.

# orderedItems[].object.content
It's been a long time I haven't posted a #microblogpub update, so here we go:

On the #ActivityPub side:

A blocked server entry now blocks all subdomains

New "GIF mode" for video without audio (as Mastodon converts GIF to video, we now autoplay them in a loop when "hovered")

The media proxy is more stable (bigger timeout + retries)

A bunch of bug fixes and improvements

On the #IndieWeb side:

Webmentions replies/likes/reposts are now being merged with ActivityPub interactions

Improved microformats2 markup in templates

Also, in case you're worried, microblogpub is not vulnerable to the activitypub-troll[.]cf "attacks", as we're not fetching all the profiles mentioned in a note.

And I also pushed a #YunoHost update.

Thanks to all the new contributors!

# orderedItems[].object.content
@thej@social.thej.in Hey! That looks cool!

I am curious, I guess you run it with only "1 instance"?

And do you have any kind of SSH access? As for now, some maintenance tasks are done via the command line (like pruning old objects from the DB to save space).

Thanks!

# orderedItems[].object.content
@reidrac@mastodon.sdf.org Hey, thank you!

I took a look in the logs, and I did see that an Accept activity was sent to your server in response to your follow request:

2022-11-19 19:08:16.851 | INFO     | app.activitypub:post:394 - Posting https://mastodon.sdf.org/users/reidrac/inbox (payload={'@context': 'https://www.w3.org/ns/activitystreams', 'id': 'https://microblog.pub/o/958c3f251d4a451eaf3cd861b2120f4c', 'type': 'Accept', 'actor': 'https://microblog.pub', 'object': 'https://mastodon.sdf.org/e70e795f-a99e-4f39-8249-68b937a1fd91'})
2022-11-19 19:08:17.480 | INFO     | app.outgoing_activities:process_next_outgoing_activity:263 - Success

So it looks like the issue is coming from your instance. Maybe it was overloaded and the queue still hasn't process the reply? You can try unfollow and send another follow request though.

# orderedItems[].object.content
@0xba@social.tchncs.de yes I think for multiple users, GoToSocial/@gotosocial@gts.superseriousbusiness.org should be a reasonable alternative.

Serving microblogpub on a path is possible, but you will still have a config/DB per users. Then each administrative tasks like pruning old objects would have to be performed once per installation.