Making some progress on full-text search support in #microblogpub!

Here is a sneak peek of the upcoming support to show #Webmention replies merged with #ActivityPub replies!

@ayourtch@mstdn.io Looking at the logs, you added an extra space @Ayourtch@mstdn.io, but it should be handled by the server.

I will fix that.

@gotosocial@gts.superseriousbusiness.org This is a good PSA 😺, I think it applies to almost all servers/implementations.

I did add a tweak to re-fetch/refresh the key in case of invalid signatures in microblogpub to help with this issue.

@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?

@charadon@mb.iotib.net done!

It's not documented yet (and I just pushed it), but once you update and go the profile page of an actor, you should see a "hide/show shares" button.

I just pushed part one of an update that will merge #ActivityPub and #IndieWeb interactions.

For now the facepile will look a bit funny if you have IndieWeb interactions, but it will be fixed soon with part two.

For now, the replies/likes/shares counters of #microblogpub will combine the two, but an update in the templates is still needed, as it will still show all the webmentions reactions as "Webmentions". Soon they will go to the right section (likes/shares or displayed as a replies). Older webmentions will be considered as unknown (for now).

(cc @ash@acegiak.net)

@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.

@defulmere@mastodon.online Thanks! That's really cool, I will add link to this in the official documentation.

@twizzay@thisis.mylegendary.quest (cc @delimiter@csv.jodh.us) filtering is not yet implemented, but it is definitely in the roadmap!

In microblogpub, there's 2 timelines: one for the stream, and one called "inbox" who shows all the received objects.

I wonder if the filtering should just prevent some objects to appear in the stream, or if it should delete them? Maybe it should be an option, i.e. "hide from stream" or "delete" flag for each keyword/regex?

At some point, the plan is to also have a Python callback to customize what makes it into the stream (i.e. some users have asked not to show shares/announces).

@hamefang@weirder.earth Hey, for now that's not an option.

It is something that could be implemented, but I think it would require quite a bit of work and thoughts to be done correctly.

Do you have examples of other fediverse software having this feature?

Some points that I think would be tricky:

• Public posts would still be visible on the "public website"? It's just that interaction would be blocked (like searching for the profile or an object URL)?
• Should a microblogpub user see an error if he tries to lookup an object on a "not-allowed instance"?
• If an actor for an allowed server shares a post from a non-allowed server, I guess it should be rejected?

If that's something that keep being requested and we come up with a good plan/list of requirements, I can eventually consider it.

@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.

@tofeo@microedit.ion.ovh Hey, it should be in /opt/yunohost/microblogpub.

@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

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! 🎅

@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.

@piwi@framapiaf.org (cc @ash@acegiak.net) For now I am still focusing on the backend side, so your best shot would be looking at forks.

Having few themes out of the box would be nice though, I will try to see how we can make that happen!

@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!

@defulmere@mastodon.online Hey! Not yet, but if you have some suggestions on what could be done to make it easier, please let me know!

One thing I am working on right now is to allow overriding the index page and add custom pages, but it's a work in progress and not yet documented.

@Razemix@cztwitter.cz Hey! It is how Activity Pub works (the underlying protocol used by Mastodon).

I think no one is/was following this profile from your instance, so it does not know about existing posts.

Now that you're following this instance, new posts will be cached in your instance.

I hope this helps, thanks!