wait could vandelay.systems not be federating with mastodon.social, this is relevant to my life
@konklone even my local timeline is lagging to hell
@konklone Looked like you typed "vandelay.system s" (with a space) in that last toot
@lmorchard hmm, it doesn't look that way to me, are you sure
@konklone Poking at your tooter, I do see one weird thing: It seems like somewhere you might have `https://vandelay.systems` where you should have `vandelay.systems` (also: nice domain :) )
@konklone I know that's super vague, but... if you look at the result of https://vandelay.systems/.well-known/webfinger?resource=navinvembar, the <subject> in the XML has acct:navinvembar@https://vandelay.systems
If you look at https://toot.lmorchard.com/.well-known/webfinger?resource=lmorchard - my <subject> is just the domain name
@konklone My guess might be that you have LOCAL_DOMAIN=https://vandelay.systems in your .env.production when you want LOCAL_DOMAIN=vandelay.systems
@lmorchard I don't run vandelay.systems, but that sounds like potentially the problem, yeah
@konklone Oh! Derp! For some reason I thought that was your instance
@konklone Surely this wins for the best-named mastodon instance.
(Do we call them instances?)
@schmod I agree and I desperately want to know if @navinvembar@vandelay.systems feels the same way
@konklone It looks like that might be the case. Another possibility is that mastodon.social is generally lagged to the point that it has not yet tried to connect with vandelay.systems
It's kinda of a thing the last day or two. Timelines are lagged to hell and back, mostly because OMG NEW TOY en masse.