ein neuer Spambot , muss das sein? ๐ซ
ein neuer Spambot , muss das sein? ๐ซ
@browneyes
ใพใใใใฏใใใชใฎใงใใใ็ตๅฑใฎใจใใใใใทใฅใฟใฐใใฉใๅคๆใใใใใ่ชฟในใๆๆฎตใใ็จๆใใใฆใใใฐๅ้กใชใๆฐใใใพใใ
ใใฃใจใfedibirdใชใใใใทใฅใฟใฐใคใใฆๆ็จฟใใใ ใใงใใใฃใกใใใพใใใฉใญ!
@spraoi for me, in debugging #tagspub, I set up Docker Compose environments locally.
- Add localhost hostnames to /etc/hosts
- Use caddy to reverse proxy internally and externally
- Turn debug logging up to 11
- Turn off SSRF protections
- Turn off cert checks if possible
- Add the caddy root cert if not
- Add the caddy root cert to my ca bundle
Having the source code on hand to quickly look up error messages helps too.
Some quick #tagspub data! Since 18 Feb 2026:
- 4632 distinct server domains
- 225435 unique posts
- 259272 unique hashtags
- 1,213,660 unique boosts
I'm very interested to see more servers connecting. https://tags.pub/#connect
OK, I did some debugging of #tagspub with #GoToSocial today. There were a couple of issues -- especially the unusual public key structure from GoToSocial, as noted here: https://codeberg.org/superseriousbusiness/gotosocial/issues/1186 . I loosened up our check for encryption keys enough to let these through.
Now, in a testing environment, I'm able to follow and unfollow hashtag bot accounts, and connect to the @_followback account. I think it's working pretty well -- I was able to see hashtags get shared.
If you use GTS, let me know!

As I explained here -- https://github.com/superseriousbusiness/gotosocial/issues/1181#issuecomment-1331877047 -- we have an awkward situation right now as a result of a dodgy early design decision I made to serve a stub of an Actor model at the `/main-key` endpoint. We should investigate what ...