oh, this #[4]

Reply to this note

Please Login to reply.

Discussion

Imagine if we could create custom clients by tapping into your API to pull-and-display a very specific subset. 🤩

i wonder how hard it would be to do that... i mean, "plugin" is more or less a native feature in browser javascript engines, should be possible to have a config where you can have a baseline that is just the thing that enables loading of the other things

i know that nostrudel has a heap of this kind of optional things in it, probably the code needed is already done, just a matter of building the on/off switches and moving more of the codebase inside these units

Maybe. I want the controls in relay.tools, tho.

so for white label type thing... you could also have custom themes and artwork and such as well

Ohhh... Customized relay landing pages. Like MySpace. 🤩

well i'm just saying that it's the same thing whether it's accessible in the interface but if it's in the deploy side it's more like a white label

Well, people could go there and poke around my relay. My relays are all sort of special...

The landing page for relaytools relays are about to get a lot cooler 😎 at least, I think so 💎🌊 hehee.

But yes, landing page is a huge aspect of my vision of what relays should be like.

(hence all the work to serve pretty website at the actual subdomains)

🫂

there is a relay interface viewer in nostrudel on the relay pages, it would be cool if it worked with that

Cool, I'll check it out.. 🤔 I like the nostrudel relay stuff 💎

The API exists. I have documented some of it with golang code in a branch (it manages the allow list) I'd be curious what usage of the API you are thinking would be nice.

Well, we'll be out with Alexandria, soon, and that should only show a subset of GitCitadel (long-form, wiki, and eBooks). And then we want to fork off that to create Biblestr (only Bibles and such). So, we would have to maybe query for labels, so that we could tag the stuff that should show up where, as a curation.

Nobody currently allows for manual curation on the model/controller end, but it's essential for communities and groups. Otherwise, everyone has to use the same client.