Excerpts from Melvin Carvalho's message of 2012-06-26 14:49:28 +0000:
> PS we also need to turn docrastinate into a verb! 'Docrastinate it!' :)➜ whois docrastinate.it
Domain: docrastinate.it
Status: AVAILABLE
Hey Melvin, cool you like it! It was born out of the need for having
multiple documents next to each other and is mainly just a personal
hack. I’m actually working on another text app which focuses more on
distraction-free writing.
The typeface is that dark by design because once you know it, these
headers would be obtrusive when more visible.
If you like it, I just added a Flattr button to the app, and you can
also flattr it directly at:
https://flattr.com/thing/665327/Docrastinate
(Flattr folks: is there a dark theme for the button? It’s pretty
intrusive so I reduced the opacity but it still looks weird.)
Cheers!
we have all of this (soon ready to launch) in
http://remotestoragejs.michiel.5apps.com/example/docrastinate/
it will store e.g. the 'projects' pane on
{baseUrl}/documents/notes/projects as a json-ld object like:
{
@type: 'https://remotestoragejs.com/spec/modules/documents/text,
title: 'projects',
content: (the pane content)
}
i had a bit of trouble deciding whether it should be called 'content'
or 'contents' and whether to use https in the @type URI
we have all of this (soon ready to launch) in
http://remotestoragejs.michiel.5apps.com/example/docrastinate/
it will store e.g. the 'projects' pane on
{baseUrl}/documents/notes/projects as a json-ld object like:
{
@type: 'https://remotestoragejs.com/spec/modules/documents/text,
title: 'projects',
content: (the pane content)
}
i had a bit of trouble deciding whether it should be called 'content'
or 'contents' and whether to use https in the @type URI
On 7 July 2012 12:44, Michiel de Jong <mic...@unhosted.org> wrote:we have all of this (soon ready to launch) in
http://remotestoragejs.michiel.5apps.com/example/docrastinate/
it will store e.g. the 'projects' pane on
{baseUrl}/documents/notes/projects as a json-ld object like:
{
@type: 'https://remotestoragejs.com/spec/modules/documents/text,
title: 'projects',
content: (the pane content)
}
i had a bit of trouble deciding whether it should be called 'content'
or 'contents' and whether to use https in the @type URI
You're probably correct with 'content' as exemplified by :
http://sioc-project.org/ontology#term_content
we have all of this (soon ready to launch) in
http://remotestoragejs.michiel.5apps.com/example/docrastinate/
it will store e.g. the 'projects' pane on
{baseUrl}/documents/notes/projects as a json-ld object like:
{
@type: 'https://remotestoragejs.com/spec/modules/documents/text,
title: 'projects',
content: (the pane content)
}
i had a bit of trouble deciding whether it should be called 'content'
or 'contents' and whether to use https in the @type URI
On 7 July 2012 12:44, Michiel de Jong <mic...@unhosted.org> wrote:we have all of this (soon ready to launch) in
http://remotestoragejs.michiel.5apps.com/example/docrastinate/
it will store e.g. the 'projects' pane on
{baseUrl}/documents/notes/projects as a json-ld object like:
{
@type: 'https://remotestoragejs.com/spec/modules/documents/text,
title: 'projects',
content: (the pane content)
}
i had a bit of trouble deciding whether it should be called 'content'
or 'contents' and whether to use https in the @type URI
When running my own version, I'll just make a *slight* change, in that I'd like to store my data encrypted. This way, I can access it, for example, from an internet cafe, and I'll know it's 100% safe.
I think it's just a case of adding a single function. It doesnt seem to be AGPL, so I could just maintain that feature in my local branch? If anyone else was interested, I could publish the source tho ...
>
> --
>
>
>
--
Even if it’s possible, we shouldn’t really endorse or do it as it
creates walled data gardens. We have modules exactly so this doesn’t
happen.
On Tue, Oct 2, 2012 at 2:46 PM, ☮ elf Pavlik ☮
<perpetua...@wwelves.org> wrote:> --
> Excerpts from Michiel de Jong's message of 2012-10-02 12:26:08 +0000:
>> On Tue, Oct 2, 2012 at 2:03 PM, ☮ elf Pavlik ☮
>> <perpetua...@wwelves.org> wrote:
>> > it sounds interesting to have some sort of /misc path where you can have your localstorage simply syncing without any modules to remote storage and just makes a subpath per domain /misc/today.do.me /misc/work.do.me etc...
>>
>> that's the opposite of what we want. it would lock all your data into
>> the '*.do.me' walled garden.
> well if i want to do it this way - why not? also with apps like seven20 i can move my data to wherever i want to + most likely i will clone apps anyways and run them from domains i like so no problem with locking here
>
> i don't say about doing it INSTEAD of modules but as COMPLEMENTARY option... functionality of 'just sync my local storage' seams to me rather practical and i believe straight forward to implement?
>
>
>
>
--
Oh and btw on the point of »free software«: We are _not only_
concerned with software freedom, but especially data freedom and to
that extent the freedom of the people to be in control. This is only
possible if it’s transparent to them what happens with their data.
See also: »Freedom 4: The freedom to use the program effectively,
efficiently and satisfactory.«
– http://jancborchardt.net/usability-in-free-software

Bottom line: If I see Docrastinate – or any unhosted web app for that
matter – I want it to display my notes (or respective other module),
always the same ones. Not use a different module or data set of which
the management is intransparent to me. If you want to have more notes
than the 3 offered by Docrastinate, it’s the wrong app for you. Don’t
shoehorn it into something it’s not made for. (If anything, rather
than subdomains there should be something like a groups dropdown in
the app. If you want to do that, go nuts with the code:
https://github.com/jancborchardt/docrastinate )
Litewrite will solve all your problems. Just chill. And contribute:
https://github.com/litewrite/litewrite
--