Users asked for user <-> admin comms without exposing email, this is a minimal implementation.
On the OpenMeet group page as an admin, click the "manage group" button and there is a "send message to members." Select the member(s) you want and type a response to send them an email.
Yes, it's a version of permissioned data. Public events/RSVPs are kept on PDS, other data is centralized. We'll adopt what emerges as standards, but are filling in gaps now. Any concerns?
For a technical look at how we handle the service authentication, getting you logged into OpenMeet from Roomy to manage events, and open questions see:
openmeet.net/cross-app-au...
@roomy.space provides spaces for groups to chat and collaborate. OpenMeet is a Meetup Alternative, and has an an API for managing calendar events for groups.
We mashed up our services to give Roomy a group calendar feature: blog.muni.town/roomy-events...
500 people are now using OpenMeet to organize events and build community on the open web!
We want everyone to have access to #CommunityManagement tools. If you've been looking for a #Meetup alternative that runs on #ATprotocol — we'd love to have you.
openmeet.net
If you are with driving distance of Cincinnati and want to get together for an #atprotocol meetup, let's organize something.
Suggest a venue for around noon-4pm time for food and lingering.
Would the week of April 13 or May 4 work?
Grandes atualizações na lista de PDSes!
blog.vicwalker.dev.br/3lz4g6zxeic2p
- Vários apps com PDS próprio foram adicionados: @openmeet.net @surf.social @pckt.blog
- PDS do @transrights.northsky.social agora está na categoria "PDS com client próprio" com o começo do desenvolvimento do client deles
Should no longer be a problem
Oops, sorry about that. It's definitely on our side and a bug. Will have a fix out today.
Looking into it now. We shouldn't do that, but bugs happen 😅 Thanks for the heads up, you all.
So nice to hear! Your kindness abounds :)
It's a real problem.
Do you need to run a PDS, PLC, Jetstream or TAP for development and testing of your #ATprotocol app? A couple of us needed it for independent projects and we try to DRY so first pass is at github.com/OpenMeet-Tea...
How are you managing that stack for your project?
Good bot. Add one more.... at least one operator is using sqlite to gather application level metrics. Adding that endpoint would be ideal.
What do people do to monitor the Bsky PDS they host?
There doesn't seem to be any exporting of service metrics.
Was that a design decision or just delayed?
People could login using atproto before. Now web users can join the party. Users may link an existing atproto account, or have us manage one for them until they are ready to take over control.
New territory for us, so feedback is very welcome.
Yesterday we launched a new feature and now our existing web users can bring their own DID or we can be a temporary custodian of a new identity. Either way, now every user's PDS is the source of truth for public events and rsvps.
openmeet.net/your-identit...
#ATprotocol
you can now Login with Bluesky to dandelion.events ☺️
pds.ls is now live!
pdsls.dev remains valid too
Now we're talking! I love it!
It turns on the connection between openmeet and atproto. If it is off, you can't publish events using this account. That setting will be going away in the next few weeks.
It was a bug in location handling... I think I've fixed it 😅. Your next one should work.
🫠 I'll look into it a bit later today. it's a bug for sure.
One of the events and rsvps are at pdsls.dev/at://did:plc... and the backlinks.
The other probably didn't have that second toggle set, which sounds like a UX bug to me. It defaults to off, but it should probably default on
We want to meet folks where they are, and right now, that's still email for many.
Do you have a list of things you're looking for? Would love to see it and put gaps on the roadmap.
Event and RSVP data lives on PDS (except when there's bugs). Groups are still in the works. For non-at users, that data lives in our community instance db.
Oh... that could be a bug or just bad UX, but let's figure it out.
- In settings, turn "use atproto as event source" ON.
- create a new event: toggle ON "publish to atproto".
Then the event will show in the PDS or its a bug.
I don't remember why we added the second toggle. Designers HALP me!
