After uploading cascii.html to deepseek.com and promptCoding with it, I saw that you had the json representaion in localStorage.
I tried generating the json from the ascii exported to the clipboard but see why this could get very tricky. So, I added an Export (JSON) to file and Import (JSON) from file and placed them in a More Popup component in which I put the existing export button, so the menu bar does not get too crowded. (for code see (1)) -
This now allows me to save the json and import/edit it at a later time - no short url needed and the data stays private.
Your code was well laid out and deepseek was able to make all the changes error-free.
Hi, great app. I'd love to understand how you are maintaining state behind that short url and see if there are ways (sans server) to at least partially recreate state from the exported ascii.
Having an Import from clipboard would truly make this a remarkable app.
Cool stuff. Played around with it and here are some comments
Must have before I'm comfortable sharing with team
- Could not figure out how to edit the rules for a folder once created, had to delete the folder and recreate to get to rules
- Did not like that eesel took over my start page, I had a different start page and if i tried to keep my old start page it disabled the extension - This will likely be a blocker
- I'd like to see much more granular control over what is being seen/indexed/shared from my history and since I use more than one profile to keep things separate, I'd like to see a way to separate personal profiles from team/workspaces
Nice to have (eesel-for-developers):
plugins: I'd like a way to customize the pages/rules etc - maybe add custom javascript etc.
cli: that allows me to programmatically create a folder with url's - inspect folders, move between folders etc.
vscode-extension: to create ephemeral light-weight folders that bring source code files (github/bitbucket urls), jira ticket urls, documentation urls all together in one folder
The Padhuka Sahasram of Vedanta Desikan aka KaviTarkika-Simhan has a section called Chitra Paddathi which paints pictures in words in a matrix of artistry in praise of the feet of the Lord. You can hear it being recited at (1) read the shlokas a t (2) and see the artistry at (3) Of note, the solution to the Knight's Tour can be seen at (4)
Cool stuff. Would love to have "memorable urls" or wiki like [[Title becomes link]] syntax so I can build out a lightweight, personal faqtiki - Currently one needs to get the share link and do a [page](share url) to accomplish it (a multi-step non-memorable way)
The Vedic tradition is typically an oral one. It takes about 3hrs to recite the Padhuka Sahasram.
Those of us who come from India and have grown up with this have older uncles and others who can compose extremely mellifluous and deep meaning verses extemporaneously.
The Chitra Paddathi which comprises of 40 verses (of the 1,008) takes 7mins 37secs.
If you are so inclined you can hear it at (1) - You can follow along with the romanized english phrases with meanings at (2)
and you can see it's corresponding visual artistry at (3)
Vedanta Desikan (aka KaviTarkika Simhan - Lion of the Poet Logicians) born 1268 C.E. wrote over 100 books.
One of them is called Padhuka Sahasram, was written in less than a day in response to a challenge and contains 1008 verses in 32 chapters.
The 30th chapter called Chitra Paddathi or Picturesque Chapter (aka Matrix of Artistry) contains verses that whilst paying homage to the feet (Padhuka) of the Lord also paint elaborate patterns, such as The Knight's Tour (1).
One hint as to why "Indians did this ages ago" is of intellectual interest to "some" indians is because the middle name of the early-stage investor and long time board member of google is KaviTark.
I've been a longtime workflowy user and recently started using Fargo. Here are my likes, dislikes and feature requests.
Likes:
- Dropbox storage
- Calendar outlines as well as free form outlines
- The 'Instant outline' communication model
Dislikes:
- Too much mouse, keyboard interaction due to Fargo's quasi-implementation of the vim like command-mode (structure) and insert (text) mode sans vim-like idempotent 'esc' and 'i' or 'r' toggles.
-- So, Enter in fargo lets one exit out of structure mode by opening a sibling node, (== vim 'o') - The lack of an 'esc' however forces one to use the mouse to get back to structure mode and than keyboard 'del' to remove this empty node.
-- A mouse click on a node in structure mode gets one into insert mode. (== vim i)
- To navigate up/down by keyboard requires one to switch from down arrow to right arrow at an indent. Why can't i just use the down arrow?
Feature requests
- Auto-convert all http:// entries into <a href= links
- Support hashtags like workflowy
- Allow intra-outline linking
- Allow devs to build plugins / macros so they can customize it to suit their needs.
- Allow for multi-line outline entries (maybe a shift-enter)
1. business lock-in: Having one's whole web business(code/website&data) be hosted by a small startup out of russia(ssor) will be a non-starter for most.
2. code lock-in: Having "code lock-in" for developers, meaning writing to a proprietary code-stack for an ssor will also be a non-starter.
3. scaleability: akshell does not currently provide a clear path to scaleability for any one app let alone the potential of hosting 1000's of apps. This very rapidly becomes a cloud-scaling issue that the ec2, gae's are attempting to solve and will be a non-starter for an ssor .
4. dynamic code sharing - use'ing other libraries within askell might reduce development time, but unless there is a static version of that library associated with each instance, with any change the possibility of breaking the web services makes this a non-starter and everyone would revert to a github like "static code sharing" model.
Here are the pros
1. A custom webhook pipe builder: Say I wanted to build a "dynamic form" get user input, save state (in a db) and run it through a series of dynamically created "webhooks" and process the final output. If akshell provided "an app development api" I could dynamically create an app, generate the code have it hosted and throw the url up for user input and have the user walk-thru various webhook/needed steps to process & generate a final response.
- this is not now possible w/ appengine or ec2
- propietary code/data lock-in is a non-issue since I am not "storing" as much as I am processing.
- leveraging "dynamic community code" would be a pro/ not a con in this case.
- a freemium model would be possible as i'd need free to wade in/ test etc and with load expect to pay a per use fee.
- see some of Jeff Lindsay's webhook related work i.e. webhooks, mailhooks, scriptlets.org etc at http://github.com/progrium for related work
2. A mashup test/use-bed: Web sites with apis could create "canned akshell apps" that not only allowed developers to use("foo-api") to test but also provided examples of use and each web-service could possibly subsidise the hosting / bandwith costs of using their api-apps so developers could just plug-n-play.
3. There are a few more use cases i can think of, you could shoot me an email if interested.
This is quite innovative, a javascript appengine if you will. I am not so keen on the enforced sharing, I think separating "library modules" from "user apps" and providing opensource access to the "akshell" engine so folks could host their own, port the db over to google appengine etc. would make this rock. So, is the akshell engine's source open/available now/later??
(1) https://github.com/casparwylie/cascii-core/pull/5