@paytonrules I hope I donβt sound wishy-washy here, but the idea keeps evolving with every person who adds their comments. Iβd call it βstone soup developmentβ if I ever wrote a book.
Fedi could AT LEAST provide identity and sign-in.. and maybe allow people to post/boost reviews from their profiles.
The biggest value might be in using the social graph to determine βtrustworthyβ reviews and filter out the bots.
I've posted some updates to my original PR here: https://codeberg.org/benpate/fep/src/branch/fep-3b86/fep/3b86/fep-3b86.md
I'm pretty pleased with these changes. I think it alleviates some of the confusion, and it locks down the specific parameters that each intent would accept.. which, addresses one of my specific pain points with ActivityStreams in general.
Let me know if this new revision makes sense to you? I *really* appreciate the attention you've given this so far; it's already far better because of your feedback
I have a few more βTβsβ to dot, and βIβsβ to cross, then Iβll probably open up a limited beta test. Iβd *love* to chat once thereβs something more tangible than my silly videos.
This set of #Emissary templates is ready for developers, but not regular users just yet. Iβm actually sitting at my desk right now working on band profile pages, and I hope to post another video with more progress really soon.
You can check out Emissary at https://emissary.dev and follow my feed to see when this band profile is ready.
Iβm thinking I might even offer hosting for it if I get some interest in that. οΏΌ
@jupiter_rowland Gotcha. Thanks. I'm going to keep watching this, because it seems like a great idea.
And remember: This just started as me publishing the URLs I know about. I'm not the official gatekeeper of anything.
But I do want to be careful about linking to APIs that might expose users/sites to attack.
I'm not saying that OpenWebAuth does, just that I couldn't find any resolution to the issues other devs raised. I'm hoping to learn more about this one as the FEP progresses.
@maphew In more practical terms, I'm a little stuck with MongoDB's NoSQL document structure and 24-byte ObjectIDs. It *does* make some queries really easy.
So I expect that Emissary should be portable to other DB architectures, but I'm going to have to figure out how to map "document-based" data and ObjectIDs into SQLite (or whatever comes next)