julian

https://activitypub.space/user/julian

Public Key

npub1mlkrpm79rjl0lsz9hhjx3j0n6s7ylqykfwm5q3kcjn4y8ky4j3hqk2nu5a

NIP-05 Address

julian_at_activitypub.space@momostr.pink

Profile Code

nprofile1qqsdlmpsalz3e0hlcpzmmerge8eag0z0sztyhd6qgmvff6jrmz2egmsprpmhxue69uhhyetvv9ujumt0d4hhxarj9ecxjmntqy8hwumn8ghj7mn0wd68ytnddakskl678y

Publishing to

relay.momostr.pink

nostr.mom

nos.lol

Author Public Key

npub1mlkrpm79rjl0lsz9hhjx3j0n6s7ylqykfwm5q3kcjn4y8ky4j3hqk2nu5a

Show more details

Last Notes

2026-09-08 18:36:36 UTC

Hi @npub1swx…medf, I think I found a bug with FediBuzz and how it does its Webfinger responses.
In a nutshell, FediBuzz tag actors have `preferredUsername` set to `tag-whatever`, but the corresponding webfinger lookup `?resource=acct:tag-whatever@relay.fedi.buzz` fails with a 404, but `whatever@relay.fedi.buzz` works fine.
cc @npub1764…nuj0
AI slop explanation follows (feel free to ignore!):
> **tags.pub** does it correctly:
>
> ```json
> {
> "id": "https://tags.pub/user/nodebb",
> "preferredUsername": "nodebb"
> }
> ```
>
> WebFinger `acct:nodebb@tags.pub` → resolves to `https://tags.pub/user/nodebb` ✅
>
> **FediBuzz** breaks the round-trip:
>
> ```json
> {
> "id": "https://relay.fedi.buzz/tag/nodebb",
> "preferredUsername": "tag-nodebb"
> }
> ```
>
> WebFinger `acct:tag-nodebb@relay.fedi.buzz` → **404** ❌
>
> Yes, it's a FediBuzz bug. `preferredUsername` must match the WebFinger subject so that `acct:{preferredUsername}@{hostname}` resolves back to the actor's `id`. FediBuzz added a `tag-` prefix to `preferredUsername` but didn't update WebFinger to match.
>
> They should either use `preferredUsername: "nodebb"` (matching tags.pub) or serve WebFinger for `acct:tag-nodebb@relay.fedi.buzz`.

2026-08-20 18:03:30 UTC

- reply

I see your avatar from activitypub.space, is that what you mean?

2026-08-20 13:27:41 UTC

- reply

I do see your avatar here? :thinking_face: