Post

Okay, so... am I crazy to build the HappyView SaaS... on top of HappyView? 🤔 #atproto

1 repost19 likes

Like... hear me out. Login is already going to use atproto oauth. We create a space for each instance. Wanna give somebody else access to manipulate your instance? Add 'em to the space! Instance config can also live in spaces. Guys, I think I'm about to build an infrastructure SaaS on atproto. 🤣

Not sure if you recall my suggestion, but you could also federate the front-ends this way such that every install can act as a front-end for every other! I'm also starting to think that everybody would benefit from a happyview instance keyed to their social graphs. Charge for space vs instance.

Could also optimize storage and bandwidth a little by having instances share data with each other within the same provider (common database per lexicon) and across providers (like a server side bitorrent swarm!) ...i think i accidentally just reinvented the fediverse here.

Yeeeeeeah, I was thinking about this yesterday when they were talking about atmoBB on Off Protocol!

yes. Next step, you let people manage their self-hosted HappyView too, and handle offsite backup and other things.

I heard you like HappyView in your HappyView, helping you manage your HappyView!