Not sure if you've tried Go, but it's felt much more suited for AI use than Rust.

I originally tried out option 2, oauth made it pretty complicated for a mobile first experience I'm shooting for. It's not impossible, but required a lot.

Ended up moving to client based PDS oauth. Eventually maybe the UX will be worth migration back, but proxying the PDS through the client is fine

Will probably be niche forsure, but the amount of times I wish I could tell CC to go solve an issue has been uncountable. I could do that dev work but that process with AI is still in the weeks of dev time.

We've already went from Years -> Weeks with AI, we just need another jump from Weeks -> Hrs

Ahh unfortunate

Did anyone happen to report through the find it fix it app? Usually goes straight to the park dept and they're pretty quick about fixing. Might be worth sending in multiple reports to up the priority as well.

I've had more success cloning the library codebase then asking it to dig through its code and do the integration.

If that doesn't help have it set debugging logs at every step eventually he'll reach the root problem.

Yeah mostly agree except there's some cool platforms like kbin that tackle both in an everything was, but I don't see Bluesky moving that direction. Would be cool though.

For me it centers around following and discussing a specific topic and it's events, NBA is a good one. I follow people here that post about the NBA but it's not the same as a dedicated community who post game highlights and discuss each game. Then expand that to any hobby youre into

This focuses a lot on physical alien life which I agree is unlikely risks. Things start to get very spicy when talking about plasma or 4th dimensional beings and their role in who and what we are

With physical I'm fine with dying, the soul will live on, but what if the soul is manufactured by them?

Great last paragraph, I've wondered a lot about whether interoperability with Lemmy and an AT platform would even be wanted.

Other instances could defederate but it would certainly still impact the "vibe" of Lemmy as a whole given the low user count.

Shout-out to Kagi News that gave me this idea, they will likely be the first aggregator in alpha (with attribution)

This can also enable cool stuff like automate complex multi RSS + LLM bots which can help reduce the bombardment of multiple links for the same event across a variety of sources.

I think the idea of "own your community" is great but depends on who "your" means and whether that's the creator, or the actual community members.

The prior is an easy implementation but not super useful to most imo. The latter is a much much harder implementation but very impactful.

It somewhat fights against your typical atproto architecture as moderation needs to exist on the community repo despite it being applied per user
And you need to maintain a PDS repo per Community. It's interesting but I can't see another way around it that implements proper portability

I'm currently going down the path of Group Controlled DIDs now here: tangled.org/@bretton.dev...

Short-term I'm assigning ownership to the "instance" DID which is very Lemmy like for better or for worse, but unavoidable imo. Long-term going to try to implement multi tenant ownership & portability

Physical verification via NFC (unique bluetooth nearby devices too?) is a very interesting concept I haven't ever thought about.

Actually been building a similar platform and basically moved forward with this exact structure. The only problem is portability has to be built into the platform since it's not "your" record it's an independent DID with its own repo. Not sure if it's an actual problem but feels weird lexicon wise

I have socialmeshes.com up but it's definitely not comprehensive and I've been pretty slow on updating it. Also somewhat more geared to platforms than clients.