-
Notifications
You must be signed in to change notification settings - Fork 49
portal mods (js include) #38
Comments
Rotonde apps is the future of decentralized web. I could see people building discussion toolkits for sharing specific video game statistics, or $search and $crawl bots. I think appended custom.js files could build up a collection on |
How much do we want to support customizing the look of the feed itself? I've just ported a few customizations over from the old architecture, but in a very ad-hoc way (see dat://278a6181c1e488137ff1117255cfb20e48bf0f6223f5e63db8763912f3db9529/) -- it seems like there should be a cleaner way to do it. Or is forking the client code the right way to make these sorts of modifications? |
how much of that is css vs js @ianh? |
I think that we don't need to do any changes to the core client(besides adding custom.js, or service.js to the includes) to allow for this, @ianh, maybe just wait for @underscorediscovery's proof-of-concept. My only fear with this pattern is security, someone could build a service that deletes your feed and so on. But at least beaker has history and revisions. |
The changes are all to the JS (you can see for yourself at that address). |
And yeah, at some point we should do an audit for security. I think you can already delete someone's feed by embedding evil JavaScript into your name, for example! |
would the use of shadowing help with |
I've got some ideas kicking around for this, initially as a simple
scripts/custom.js
with a hookfunction(rotonde) {}
but that could probably be specialized into specific mods.As an example of a specialized mod: the idea of an embed (youtube video, pico8.com game, instagram post - whatever) being a drop in module that someone provides for portals to opt into. It is important that the fallback remain legible valid for this type of entry, but in my feed, I opt to view custom types of content in my own way. something like
scripts/embed/youtube.js
. These might also want a css and maybe even images/assets, so maybeembeds/<type>/*
.I'll try to formalize how I see this structured soon but opening discussion @cblgh @neauoire
The text was updated successfully, but these errors were encountered: