Notices by Nimda (nimda@wizard.casa)

@silverpill @elvecio you mean just from the search? Seeing this:

@silverpill @elvecio looks like the import was clean:

>>200268509
I passed the IQ test and figured you mean mastodon.social :heyface:
Also just followed the i2p account there, and loaded their posts with picrel, no idea if bloat has that ability, but posts should be populated for you now too

have fun

>>506218308
Nothing that I would really push for because I don't mind CLI/config editing administration, but just exposure for stuff like:

- editing the server description and other "about" fields
- federation filter list, add/remove domain, select option dropdown for each filter type
- edit registration values (type, default_role)
- UI for relay following
- custom emoji management
- monero wallet health/settings

etc... I just have the config.example.toml open here and picked some things off

@silverpill yes, better than nothing for sure
...and it's reminding me that I really should clean up old unused accounts sometime

Just updated :mitra:

@frogzone @silverpill I'll also do some maintenance, I'm sure the i2pd needs updated on that server

Mitra has been updated!
v5.6.0 :mitra:
Groups in my fedi? It's more likely than you think!
Pleromos in shambles :cirnofortnite:

@ps @ufm @silverpill
is ufm seeing your posts?

:aru_0450:

@foolghool Thanks for letting me know, I never user bloat (or tor, i2p, just yggdrasil) I'll see what's breaking and let you know what's up

@foolghool bloat's back!
I don't know what happened, but the service was just down for 9 hours, I know I had some trouble with the update yesterday.

I tried the list thing too and got this error, same on the backend
2026-02-06T07:34:49 mitra_api::http [INFO] POST /api/v1/lists : Content type error

looked into it for a bit and bloat is sending generic form encoded data but Mitra expects JSON on that endpoint, not sure which side should get patched in the end though (@silverpill -- want an issue made for this?)

@visionaire Not sure, looking at the documentation:

https://codeberg.org/silverpill/mitra/src/branch/main/docs/relays.md

if the @tag-fediverse is a "relay actor" it might just inject posts into the https://wizard.casa/federated timeline? But it also says it would follow you back and that didn't happen when I tested it

What did you try and what did you expect?

@visionaire I see, have you tried it on another server? I just tried on a Pleroma alt and I'm not sure if it's working over there either. Maybe @silverpill knows more about how these actors work with Mitra?

@silverpill @dsdarkkogo showing my ignorance here, but I thought 'media proxy' was just when we don't reject media and instead download it locally so clients don't hit other server's media

Can you point me to what you mean? Sounds like the opposite of what I thought where we don't host the media and instead have clients "hotlink" media from other instances

I was thinking it could be useful to have a setting for media retention instead of post retention: keep the posts, but delete the media until they're loaded or something like that

@dsdarkkogo The biggest use of disk space here is proxying media on posts and that size depends on how many accounts your instance is following (or posts with media attachments federating to you really)

Since there are some accounts here that are really aggressive with follows, the media directory can become an issue, but I countered by being really aggressive with this setting:

Which can be annoying to users that like to browse hashtags since if nobody interacts with a post it'll be removed. Database size is also dependent on number of users, relationships etc, but since you asked here's the stats:

media dir: 43G
postgres db dump: 891M

but for a single user instance it should be MUCH much smaller!

Just remembered wizard casa has been around for just over 3 years now (birthday is in September) and updated the about page

@bmcd hi welcome :waving: from an admin perspective it's been much easier to run mitra over pleroma, for end users there probably isn't much difference. Most difference is in the front end, we have bloat https://bloat.wizard.casa/ here too

@bmcd I left it default at 5000, I've never tried pushing past it so idk what happens if you try

@silverpill awesome :acat_gangnam: I'll definitely experiment with it sometime and let you know if I run into anything :cat_cheers: