But bump for bored high people I guess.
I'm just experimenting with/checking on the following:
1. Daily Paul friendliness with framed, sandboxed, non malicious external content (all client user agent source code visible any time for inspection)
2. arbitrary, user defined interactive directed graphs
3. intent to have later on user defined verbs, actions, and metadata attached to those nodes and links, per user, with local storage
4. also later on, private, and public shareable sub graphs, when acyclic
5. finally (3) and (4) queryable by the user, on demand or on scheduled, predefined regular basis
"Cyril" pronounced "see real". I code stuff. I care quite a bit about language.
Did you know? 1,299,830,899,481 can be factored in no more than 55,655 steps.
Do you anticipate much overhead on the dailypaul.com servers, or is it all client-side view layer stuff for DP reader browsers?
I'm guessing something interfaced with the Experience API. Close?
Overhead on Daily Paul servers? No. There is none.
This little thingy above sits in its own iframe the content of which is served by my host only. As for the rendered layout and animation (assuming it even bothers to work, since that requires a recent browser), is entirely performed on the client, user's browser.
I was just curious whether such an iframe-based integration would render friendly enough as part of a DP post or page.
That helped a whole lot. 0.o
I think I'll stick with gardening Lys.
But good luck on your venture.