Post

Im still unsure about sidecars in this case because the enhanced post and the original post could diverge which could be bad

The votes themselves are practically identical to likes. Each of the 4 possible options has its own collection for easier constellation queries `app.reddwarf.poll.vote.a` and so on It lacks expiration and per-user option limits because those arent easily implementable using only constellation

13/1/26, 9:55 am0 reposts6 likes

More on sidecars. Its more of a problem about how which post variant that you liked/interacted matters somewhat. A like to the original bsky post might differ in meaning compared to a like towards the enhanced post

kopper

@w.on-t.work

idk, i feel like an app.bsky.feed like only matters for app.bsky.feed posts, so using it on Something Else doesn't (or, shouldn't?) mean anything. this isn't fedi, we don't have to share a generic Like for everything and have to deal with "how the fuck do i interpret Liking a Dislike"

And the problem is that you cant fit all of the extra data inside of the bsky fallback post. Even if you stuffed it in a custom field, then its still the same problem because the extra data wont ever be shown to users

The opengraph image generation for polls is my attempt at graceful degradation but even that has its limits. The image is not easily machine readable / verifiable to be the same content as the poll itself.

@aeshna-cyanea.neocities.org

The votes themselves are safe, the vote record strongrefs to the sidecar that defines the polls. But bsky likes arent, they only target the bsky post and not the poll record

autumn