In July 2025, @0x3b0b posted a blog post, noting the Actually Legitimate URL Shortener was causing a problem:

...It was uBlock Origin. More specifically, it was a custom filter list I added to my uBlock Origin configuration somewhere along the way, the ➗ Actually Legitimate URL Shortener Tool. I don't remember why, so I should probably dig into that and see whether I really want that filter list - that's neither an endorsement of the list itself nor a censure; I'm just acknowledging that if I don't remember why I'm using it, I should probably make sure I still want to. I think I must have started using that list more recently than I thought, because I don't think I always had this problem with my blog, but this commit from October 2023 added a filter to remove the query-string parameter ap_id any time it appears. And that's the parameter #microblogpub uses on the /object endpoint when the logged-in admin wants to look at a post in its threaded context, to identify the post being focused.

https://bw3.dev/articles/2FHb1/state-of-the-blog-address

I happened to find that blog post when searching the internet for pages referencing "Actually Legitimate URL Shortener Tool" - it was on page 5 of my search results.

And now, months later, I have patched it: https://github.com/DandelionSprout/adfilt/commit/b4b12d96eb0501e8dd2bdc3691199c50bc7542f0

If someone uses this software, and can confirm the patch works (or doesn't), I would appreciate feedback.

I don't want to shame OP, but in the future, if anyone has an issue with the Actually Legitimate URL Shortener, the best place to report it is in this GitHub Discussions thread: https://github.com/DandelionSprout/adfilt/discussions/163

Maybe the OP did report it there and it just got buried, I don't know. Again, I'm not trying to shame the OP, just trying to inform people since not everyone knows.

Response times for issue reports range from a few minutes to a few months, depending on how busy we are. Generally issues should be addressed within at most a week.
If you don't have a GitHub account or don't get a timely (within a week or two) response, feel free to ping me here or by email.

I think, due to an ill-advised attempt (or perhaps more accurately ill-timed - late at night right before going to bed not really being ideal) to update my reverse proxy, I might have somehow caused it to block posts from all instances. Either that, or everyone's been really quiet for the last day. I'm trying to get it fixed now.

The intent was to switch from blocking all traffic from snac instances to blocking only their POST requests. I'm not sure yet what, if anything, I messed up.

Snac has a default setting to send all posts to all known inboxes, to improve reach for small instances; what I read on my #microblogpub instance is essentially the whole instance inbox. I do not find the result acceptable. I'm going to have to get more creative if I ever want to follow someone on a snac instance, but for now I thought I'd try to make it so that snac users could maybe make their instances retrieve my posts, even if they couldn't talk to me without someone else boosting them over the wall. Unfortunately, something seems to have gone awry...

Messages being sent to all known instances

Hey there. My instance has been receiving messages in the inbox from at least a snac2 user that I don't follow and that doesn't follow me. Those messages are also not replies to any thread I'm involved with, so I don't understand why I'm getting those messages. Example of one of those messa...

Codeberg.org

Teste de hashtag

#microblogpub #testing

State of the Blog Address

Been a while, hasn't it, folks? I thought...

㬋's microblog

TL;DR: Jelikož se mi tak nějak nahromadilo pár věcí najednou, budu si migrovat účet na jiný server. 

Pokud to @xChaos nebude vadit, usadil bych se u něj jako @albi. Možná jen na chvíli, ale možná na dýl.

Důvody jsou mnohé, tak pokud to někoho zajímá:

  • jedu ještě na Debianu old-stable, protože #YUNoHost do teď neumožňoval upgrade
  • moje #Akkoma už dlouho nejde aktualizovat, protože nové verze vyžadují knihovny na old-stable těžko udržovatelné, navíc není v úplně optimálním stavu kvůli přechodu z původní Pleromy
  • YUNoHost konečně umožňuje upgrade na Debian stable, ale migrace DB Akkomy skončí chybou kvůli nekompatibilitě verzí Postgresu
  • Nextcloud, co se mi při upgradu taky rozbíjí, jsem už obětoval (zmigroval jinam)
  • stejné mám v plánu v dohledné době přemigrovat celou skládku z dosavadního výborného #VPSFree na domácí serveřík s Dockerem, takže se s tím nemám touhu už víc crcat
  • v budoucnu bych se rád zase vrátil pod svoji doménu na nějakém ještě lehčím systému jako @gotosocial nebo #MicroBlogPub, ale ani jeden mi zatím nepřipadá spolehlivý … a možná časem někdo chytrý přijde s řešením hostování identity pod vlastní doménou bez ohledu na server 

Je to moje první migrace fedi účtu, tak se mnou prosím buďte trpěliví.

Akkoma

State of the Blog Address

So there's some folks, starting with...

㬋's microblog

@[email protected] I still microblog.pub even though I have two problems:

  • memory is getting low on my host running all the services I'm using (4GB RAM)
  • time needed to maintain microblog.pub beside #GoToSocial.

But it's still worth it I guess - otherwise I wouldn't have made the #yunohost package version 2 to keep #microblogpub available for yunohosts next version.

BTW: for yunohost a database integration would be great - there's always running mariadb.

This looks pretty great @[email protected]!

I also recently looked around for a #Fediverse server and thought that #GoToSocial is pretty great. (I was actually thinking if we really need to reimplement a server for #MicroBlogPub. But I guess having a micro federated server in #Python is something nice to have out there.)

I actually just added a discussion about this in our project.

Refactoring and modularizing the protocols out of the App/blog repository (v3?) · microblog-pub · Discussion #16

One of the things I am most interested in (and that brought me to uBlog.pub) is the implementation of open web protocols. (BTW, I am not alone. Check #14.) For instance, I would love to contribute ...

GitHub

Hey @aonrud @[email protected] @[email protected]! I noticed you also use #MicroBlogPub. I recently started playing around with it and then realized the original author stopped responding/maintaining it...

I am starting to talk to other users about creating a new home for central coordination here: https://github.com/orgs/microblog-pub/discussions

It would be great to exchange ideas and maybe work together to keep this project up...

Build software better, together

GitHub is where people build software. More than 100 million people use GitHub to discover, fork, and contribute to over 420 million projects.

GitHub

I looked at this again and found that the two notes requested very often from my #microblogpub are those that I 'pinned' that can be found at /featured.

The rest are paths pointing to information about this side. Maybe it has been some kind of #fedibot?

Here's a #fail2ban config that helped me blocking the IPs:

# cat /etc/fail2ban/filter.d/manual.conf [Definition] # cat /etc/fail2ban/jail.d/manual.conf [manual] enabled = true bantime = 14d

This seems to lead to a jail which isn't connected to a logfile and for which manually added IPs stay blocked for 14 days.

To block IPs I used fail2ban-client -vvv set manual banip $IP which leads to

# fail2ban-client status manual basic Status for the jail: manual |- Filter | |- Currently failed: 0 | |- Total failed: 0 | `- File list: `- Actions |- Currently banned: 4 |- Total banned: 4 `- Banned IP list: 34.229.130.24 44.206.236.255 54.164.161.50 3.238.157.198

fail2ban is integrated into my #yunohost and even though it doesn't come with the greatest documentation I'm starting to love it.