HyperDraft is a note taking app that uses the remoteStorage spec to enable users to own their data.
We’ll find out more about what Rosano is working on, their approach to software for users, asking users for funding, and discuss how these might fit into the Fission platform.
For sure, I can give you the file or Vimeo access if you need anything. It was kind of mildly organized stream of consciousness. I was feeling so silly about not demoing anything the whole hour with everyone
Would love that. I’ll try to attend, no Fission apps to demo though… I definitely want to come back when Launchlet is more developed to go into detail about customizing apps that are already published.
Yeah, doesn’t need to be a Fission app…yet This is our first one, time to celebrate and meet other makers. I’ll add you to the list.
Yeah, so we should talk about this from a spec perspective, too. Design is always going to be tricky. Basically, like remote storage or whatever, just a well known location where a user css file lives.
In Fission’s case, this would be /private/Apps/[developer]/[appname] and then… user.css? custom.css?
This is all stale now (Sept 2019!) but here’s where we were looking at user preferences:
Let me know what you think or if you’ve written anything down in your Garden about user styling.
Also: I forgot to ask you about cross linking gardens. I vaguely was thinking about Webmentions and also the Web Annotation spec Web Annotation Data Model
I meant, like, for different Fission things I need to turn into videos This is great to illustrate funding, and very awesome that I can just embed the video in our blog post about our discussion.
I’ve added timestamps to the Vimeo page, will update the description. First time making an actual overview of this for myself—wow that’s a lot of stuff…
I don’t have a complete thought yet but my approach is definitely not file-oriented or dependant on a certain way of storing on the filesystem, it’s just simple declarative key/value data, at least for now:
So, “file system” isn’t really the right way to think about it / doesn’t matter. It’s all interfaces anyway.
So, on the developer side, webnative.userStylesLoad() or whatever.
On the user side, we can make a CSS Editor App … which lists apps and styles and such.
But we start, in our case, with “go look in the place where your app settings are set and edit the user.css file in there”. Having a file system gives devs / early adopter users a way to start … and we ship Drive with a basic text editor.
Also, I’m definitely not including fragments of JS Brooke will have a better idea of what threat model works here.
I guess prefer to think of them as first-class documents because Launchlet is built for that, as opposed to settings: it should be highly-visible, malleable, ‘just data’, normal.
I imagined Launchlet as a user script / user style app. I heard it’s terrifyingly unsafe to deal with javascript this way so I will need to consult with someone at some point…
This is our first one, time to celebrate and meet other makers. I’ll add you to the list.
This is great to illustrate funding, and very awesome that I can just embed the video in our blog post about our discussion.