cards.statmeet.com

@statmeet.com

Pro-social Internet Scale Collaboration

If you choose type "open" on a vote, any Bluesky user can login via oauth and vote on the issue. This is for community wide feedback on issues. The results are published to the corresponding feed.

**Group deletion cleans up all references:** delegations, deck/card group shares (group_id nulled), and pending invite cards for the group are cancelled — previously an invitee could accept an invite to a deleted group, creating an orphaned membership row. process_group_invite_state_change also now…

hey self-hosters! we’re planning to raise default PDS blob size limits to 300M soon to allow users to upload longer videos (up to ~10 minutes at 3mbit) by default. any thoughts?

I know the Bluesky community has an anti-AI bias. This should be reconsidered, working with AI in a hybrid fashion can lead to real insights. Here's an example. I was trying to refine the ideas behind my app to get my first user.

Members can now see and leave their groups: /groups gained a "Groups You're In" section, and /groups/{id}/leave lets a member remove themselves (owners can't leave; the group page shows Leave instead of Delete for members).

**Card Bluesky posts now link to their deck's atproto feed.** When a federated card belongs to a deck with a published feed, the post footer becomes `View Card → | cards.statmeet.com | atproto feed`, with the last link pointing at the deck's bsky.app feed page.

We’re doing a user study to find out how adding always-on live values alongside code effects writing and debugging experiences for functional programming. See reply for sign-up details

Why do so many compare Bluesky to Twitter? The network effect lock on legacy social is real and probably durable. #atproto is a different architectural bet — build on a protocol, not a platform owned by someone else. It's great for integrating into apps. In the long game it will win.