Hi twt.social / yarn.social :)

Been a while since I’ve been here.

I just read @jlj@twt.nfld.uk recent blog entry and noticed for the users with their own instance, the link to their blogs is only visible from their side. Is this by design at this stage? Only users on the same instance can reply comment on a blog?

@prologic@twtxt.net @jlj@twt.nfld.uk Yeah, as jlj shared the direct link to the blog, not the twt about the blog, the reader has to go looking to see if there is a twt to reply to.

The twt propagates across pods but the user profile of a different pod doesn’t show the link to blog entries on a different pod.

If I saw the twt at his page, I could copy the ‘conv/qc5b6ba’ and manually add it to twtxt.net to reply. Maybe for now, if pod owners wanted to make it easier to reply, they could copy the link and edit their blog entry to include it.

Interesting – I had no idea that blogs were any different; thanks for the heads-up, @lazarus@twtxt.net! Good to see you too. :-)

Looks like GNU social is now advocating a Docker based deployment; might opt for that instead, actually. That’s the route I went down, hosting vaultwarden on my Pi 3A, and I’m pretty happy with the results, to date.