If @smokesignal.events allowed you to comment on an event, what would that record be? Re-use the bsky feed post? Set the root / parent reference to the event aturi? Something else entirely? #ATProtocol #atdev #LazyWeb

November 07, 2025 - 20:31 UTC

10
0
12
Both @recipe.exchange and @leaflet.pub have a share record flow which requires a bsky post that they then use as a "container" so they can make feeds.

It also explicitly "opts in" to spread it publicly.

I'm encouraging @cosmik.network to maybe auto-post to bsky with note text on a per-collection.
2
0
7
Also ppl can built it themselves with ITTA? semble.so/url?id=https://ifthisthen.at/
0
0
0
So, that seems to argue, for now, for a similar "share this event" flow.

One thing: in the other systems mentioned, you only have one chance to share, otherwise you are in "don't share" mode.
0
0
0
@anna.germnetwork.com was that the proper use of millennial hashtags?
1
0
1
#yes #greatwork #keepupthegreatwork
0
0
2
Just as an experiment, this doesn't look like it's indexed: pdsls.dev/at://did:plc:cbkjy5n7bk3ax2wplmtjofq2/app.bsky.feed.post/3m52xhp6kzk2y
1
0
1
Oh, maybe it is ...

bsky.app/profile/ngerakines.me/post/3m52xhp6kzk2y
3
0
3
Leaflet comments? idk how bluesky would show posts to replies it doesn't have access to?
0
0
0
I would expect the Smoke Signal comments to be fully separate from Bluesky and any sort of mirroring would be implemented separately and optionally. imo tying it back to Bluesky automatically or reusing their comments makes it feel like Bluesky is the default rather than being a separate product
1
0
3
Personally I like the idea of having the option to simul-post to Bluesky and then in the Smoke Screen UI collate both Bluesky replies and Smoke Signal specific comments into a single list
0
0
3
i think there could be a version that’s very explicitly framed on smoke signal as “here’s the conversation happening about this event on bluesky”

if that’s not the vibe for the smoke signal view i’d say separate lexicon. i wouldn’t expect my website comments to show in peoples’ feeds.
2
0
7
Oooh I like this
0
0
1
Oh my gosh, that's it. Event feeds.
0
0
3
It may be a bit out of scope. But I think a dual comment would be cool if you reuse feed post. As in making a bsky post on event create, user comments on smoke signal, it shows there and on the post made at event create. It would drive engagement in two spots.
1
0
0
But other than that my gut says maybe it's own lexicon since bsky wouldn't be able to use it
1
0
1
I’d assume a different lexicon, or at least the Bluesky lexicon but redone at a new NSID. Purposely making your service depend on invalid records under a different service’s NSID seems jank and malicious
1
0
1
That is, unless I’m confused about something relevant to SmokeSignal, does a post get auto made when an event is made?
1
0
0
I think attaching a post + replying w/ bsky posts is the best if people are talking about a specific moment, i.e announcing the event. I think if you're imagining comments as more for rich discussion then better to roll your own lexicon
0
0
3
For now:
* link to a web-view of the event with an ok infocard (and backref to canonical aturi somehow)
* ideally a toggle between post-as-bsky (app.bsky.feed.post) / post-as-smokesignal (defaulting to safer smokesignal option)
0
0
0