Recent searches
Search options
Dear #fediverse #instance #admin
the current situation with the @guppegroups@a.gup.pe Handles is very confusing.
It drives me crazy ;)
The server "gup.pe" is now "a.gup.pe" (maybe @datatitian can confirm).
The problem is the cache of the old handles. In mastodon, people find the non-existent "gup.pe" handles before they find the correct "a.guppe" handles (`Group` `Actor`) …
Can we [after consent of the domain owner above] maybe delete the cache for the old "gup.pe" domain?
@sl007 @guppegroups
The reason I had to change the domain was because these Masto servers seemed to have gup.pe listed as a known dead server because they weren't attempting any deliveries when I put it back up on the original domain, but why do they keep suggesting the handles if they know the server is dead?
maybe handle suggestions are in a local cache
@sl007 @guppegroups
Nope I still get the old suggestions in a private window
@datatitian @guppegroups@a.gup.pe
well, yes, it seems to be an per-instance-local cache.
@sl007 @guppegroups I thought maybe a local cache as in browser local storage, but it's not that. I think this would qualify as a bug in Mastodon - why suggest handles that your server won't deliver to?
Are you an admin on your instance? Would be helpful to confirm gup.pe is listed as a dead instance
@datatitian @guppegroups@a.gup.pe
No, @chpietsch is the instance of my admin :)
The bug is the same than with the local peertube cache. We had it before with ActivityPub Conf. Then instance admins deleted the old cache and everything was fine.
[ Christian, initial post was https://digitalcourage.social/@sl007/108125646328934764 ]
PS, just btw: TUE meeting was fine, later today is another one https://socialhub.activitypub.rocks/t/interconnectivity-meeting/2379/2