Fediverse notifications

Posted Jul 28, 2025 13:18 UTC (Mon) by corbet (editor, #1)
In reply to: Re: LWN is back by rschroev
Parent article: LWN is back

But we did post such things to the fediverse feed, starting shortly after the outage began.

Perhaps the problem is everything was posted as replies rather than a new post, Mastodon seems to like to hide those. Lesson learned, next time we'll be sure to put up a not-reply message as well.

Fediverse notifications

Posted Jul 28, 2025 13:25 UTC (Mon) by rschroev (subscriber, #4164) [Link]

Indeed, I missed that. And yes, something like that is all I expect, but indeed better as a non-reply message.

Fediverse notifications

Posted Jul 28, 2025 13:51 UTC (Mon) by jag (subscriber, #3766) [Link]

I checked everywhere else*, but I didn't think to check the replies.

*) speaking of, your Twitter/X account is clearly dead, and it looks like your Bluesky account is headed that way; I think it would be helpful if there were a (pinned) post on both pointing to your Mastodon instance.

Fediverse notifications

Posted Jul 28, 2025 15:43 UTC (Mon) by zdzichu (guest, #17118) [Link] (1 responses)

This post is not visible on https://fedi.lwn.net/@lwn . Visible posts are, at this moment: Security updates for Monday; LWN is back; 6.16 is out; Rethinking confidential VMs. Last post, about rethiking, is from "3d ago".

Fediverse notifications

Posted Jul 28, 2025 15:51 UTC (Mon) by jzb (editor, #7867) [Link]

Yes; we have realized that replies are not visible from the profile page unless one clicks on "Posts and Replies". We'll be working on more redundancy and better notifications in the event this happens again.

Fediverse notifications

Posted Jul 28, 2025 15:51 UTC (Mon) by mote (guest, #173576) [Link]

> posted as replies rather than a new post, Mastodon seems to like to hide those

Hopefully constructive feedback from a very lightweight Masto user (lurker/reader) - the problem is incoming information overload for the amount of time I want to devote to the platform; I quickly found that I needed to disable all replies and boosts in my main feed. Reply content is never seen unless I intentionally click-to-open a post and read the replies. My personal usage mirrors what you've felt as a content publisher. $0.02 hth