also to note: some instances seem to be unable to resolve my emoji (leaving the text representation in their place)

Admins of tech.lgbt ( @david, @ShadowJonathan), can you confirm? :neofox_bottom: (i'm mostly interested in the current behaviour, though i can try helping with resolving the problem :3 )

I am quite a bit different here than irl, so I need to set up/redraw a boundary about interacting with me on the internet:

If you are part of my social circles irl and read my fedi posts (or other things I do on the internet), do not tell other friends too much about what I post here, and try to make sure you are not revealing my irl social graph online. (In case of doubts, just ask me, DM or otherwise semi-privately, what I consider OK.)

I don't want to get either outed irl nor being stalked from the internet to real life, except for cases when I have that under control.

Maybe think of it like this: LEdoian on the internet is has a vague shape irl, mostly materializing on events like conferences and meetups (I sometimes announce those). If you know me like “a random person on the internet who does XXX/has YYY problems”, it's this LEdoian. LEdoian irl is a bipod who [DATA EXPUNGED] and buys groceries but is not very active on the internet (and even then it's mostly DMs with other irl friends, though sometimes e uses this account, e.g. to try finding a job).

The wave function of those two entities may sometimes overlap (that's the deal with probability :3 ), but even when we occupy the same space, I feel kinda mindful about what I want to share with whom.

oh, shit, this kinda goes both ways but is not explicit. I'll rewrite this, someday, hopefully…

My identity sucks and I have the exclusive right to complain about it ^.^
/lh

Heh, I should have realised earlier: I cannot signed fetch from an instance that cannot¹ connect to my instance, as it does not have a way to get my public key.

Corollary: Even if I follow you, if your server cannot start IPv6 connections, I won't be able to read your follower only posts, even if I learn about them. (Cannot fetch them and you won't push them to my inbox.)

¹More precisely: hasn't been able to connect lately, because of caching

The end to end principle is a lie. It suggests that instance A either can or cannot reach instance B (unidirectionally).

This does not follow my observations – there is at least one instance that I appear to send my posts to¹ (push from me), it managed to get my updated bio (pull from me), meaning that bidirectional communication should likely be possible. But I don't get its posts (push from it)…

It could also be exponential backoff again, maybe. While the other instance is Mastodon, I already know that my Pleroma creates federation jobs per post, not per remote instance, so those timers are independent here. And I have no idea what Mastodon does w.r.t. broken-and-restored federation…

¹The post has just been sent to the public and to my knowledge, hasn't been interacted with. However, Fedi being Fedi, it technically might be also caused by my server not knowing…

I inspected the oban_jobs table out of curiosity, and my planned jobs should mostly run by 2026-02-16. I guess that means that after that, problems on my instance might just become permanent (and thus worthy of being fixed manually instead of waiting and hoping)…

Heh, apparently instances of the fourth kind do exist: the ones that have IPv6 outbound connectivity, but no AAAA record so no inbound traffic.

And I see them on my timeline, just can't see media and profile picture.

Now I wonder how to contact the admin in question, given that I am too lazy to create a IPv4-compatible alt account…

I have written a long-ish blogpost about the stuff I needed to do and why in a hopefully more coherent manner: http://blog.ledoian.cz/ipv6-pleroma.html.

If I get to resolve the rest of the issues, I might (or might not) update the blogpost. But the rest is mostly minor issues (unless something big shows up).

#ipv6

Well, search has given up on me (so not all is too well), so when restoring my pinned posts I had to scroll down my post history.

Two takeaways: (1) I had a good taste in humour even two years ago, and (2) I used to (shit)post a lot here. (Let's see if I can do that again :-P)

Wow, I have not seen my instance be this happy. Given how underpowered its hardware has been since the beginning, not seeing database timeouts in the log and having requests be served in few tens of ms even when I post is actually new to me.

Don't worry, the hardware itself is still unstable (bad hardware fix of the laptop the instance is running on), so intermittent issues are still expected :-)

I might have spent awful lot of time looking for unanalyzed #postgresql table. The solution was literally two words, I just didn't know :-)

That's what #selfhosting gives you :-D

My instance is cursed and wall time should not exist.

Until I understand what is so horribly wrong, here are my pinned posts: https://pleroma.ledoian.cz/notice/B2fy56ChT14sLKSWkS https://pleroma.ledoian.cz/notice/AkPQ89qoxr8GeUeS3s https://pleroma.ledoian.cz/notice/AjiTdJYO25GMhbIRNY https://pleroma.ledoian.cz/notice/AjRC6uclYTrWz5zV9E

I have no idea yet why the endpoint for pinned posts times out, but it does 🤷

I suspect something in my stack treats ULAs in a special way, leading Pleroma to complain about not getting remote/client IP address from reverse proxy (nginx). I don't remember this warning from yesterday…

ULAs are global scope, and I'm definitely treating them as such…

Well, it starts getting better. Some instances still don't send me anything, somewhy, but others are starting to appear on my timeline. Is this exponential backoff?

Reminds me of the old days when my instance was brand new and my timeline was similarly empty…

Apparently, that also meant that I was not able to log in to my instance, meaning that I wasn't able to post lol.

But I just did another bad thing to the database and now it works :-D

One of the other main troubles of my instance is that the web client seems to hammer it quite a lot, leading to exhaustion of the workers (or something, I don't completely understand it yet).

Lesson learned: Erlang serialisation format It is not a great idea to click randomly in the admin toggles. A few moments ago my instance was refusing to start, now it only doesn't let me into the admin settings.

(This is also a test post to see if I can post :-D)

A big silly realisation: I probably shouldn't expect Fedi working over IPv6, when half of it is probably deployed in Docker containers and some of it is Pleroma and forks, which I already learned cannot do IPv6 requests without tweaking.

Well, it didn't get better. Out of low hundreds of accounts I (try to) follow on more than a hundred of instances, like 8 accounts on 5 instances seem to work (and there are a few more accounts on those instances that I expect to work, but have not yet posted anything).

With most other accounts/instances, I still seem to only be able to interact (fetch posts, give favourites, maybe even reply – haven't tried that in order to not necrobump nor break things with my instance), but not fully federate (receive statuses (statii?) on my timeline).

I guess the worst thing is: I have no idea if the issue is with me being IPv6 only, or if my instance is also broken in another way. In the latter case, I wouldn't want to bug other instance admins about that…