Signup feedback

[Jesper Kjeldgaard]

I just signed up and wanted to leave you a bit of feedback that you may find useful.

• I kept trying to login with my email as the username until I realised that a username was generated on signup. I found this a bit confusing.
• When I wanted to link my Dropbox account I created a folder on my laptop, waited for it to sync to Dropbox, and then selected it. But because it was empty, I could not set it as my default dropbox wiki folder.

Otherwise it looks like a very promising alternative to Evernote and I'm excited to see where it takes me.

Thanks,

Jesper

[Mark Beattie]

Hi Jesper, thank you for taking the time to leave feedback, I really
appreciate it!

You're not the first to find the login part of the signup process
confusing, so clearly it needs more work. I added a message explaining
the username to the login form, but for the first login I think it
would be more intuitive to just pre-populate the field to eliminate
any chance of confusion.

The option to choose an existing folder is great for sharing Markdown
files with other apps, and quite a few people have imported their
Trunk Notes wikis into WikiPack, but several people selected the /
trunksync folder instead of the /trunksync/notes subfolder that
actually contains the Markdown wiki pages, so WikiPack now checks to
make sure that the selected folder actually contains some Markdown
files.

If you wanted to start with a fresh wiki, you could have selected to
get started with the template, but it sounds like you wanted to change
the folder that it uses. Perhaps I could improve the folder selection
process to offer to create the wiki template when the selected folder
is empty?

Thanks again,
mark

On Apr 22, 2:15 am, Jesper Kjeldgaard <thej...@gmail.com> wrote:
> I just signed up and wanted to leave you a bit of feedback that you may
> find useful.
>

>    - I kept trying to login with my email as the username until I realised

>    that a username was generated on signup. I found this a bit confusing.

>    - When I wanted to link my Dropbox account I created a folder on my

[Jesper Kjeldgaard]

Hey,

Or just allow for both email and username in the signup form and detect which is used in the backend.

I think your suggestion regarding empty folders is good.

What kind of technologies are you using?

Cheers,

Jesper

--

Jesper Kjeldgaard

@thejspr ~ thejspr.com

[Mark Beattie]

Wow, that's a much better idea! Now I think of it, I should have just
used the full email address as the login and let people change it
later if they like, rather than trying to be too clever and generating
a login automatically that just causes confusion...

I've had to engineer quite a bit of technology to get everything
working smoothly:

- Rails for the front-end
- Starling queue server for queueing up Dropbox API requests (The Ruby
version from before Twitter switched some of their infrastructure over
to Scala)
- Bespoke background processes for pulling Dropbox API requests out of
the queue and making concurrent HTTP requests
- Monit for keeping everything running
- Munin for performance monitoring (graph pr0n mainly...)

This allows multiple users to make multiple Dropbox API requests
simultaneously, and do things like save a page and have it synced to
Dropbox in the background.

cheers,
mark

On Apr 22, 11:26 pm, Jesper Kjeldgaard <thej...@gmail.com> wrote:
> Hey,
>
> Or just allow for both email and username in the signup form and detect
> which is used in the backend.
>
> I think your suggestion regarding empty folders is good.
>
> What kind of technologies are you using?
>
> Cheers,
> Jesper
>

[Jesper Kjeldgaard]

That sounds very cool. (I'm a software engineer myself ;)

I feel at home in the terminal so I will mostly use the app as an interface, not for editing.

Looking forward to how the app will evolve.

/Jesper

[Mark Beattie]

Thanks, I hope you find it useful however you use it!

On Apr 24, 3:12 am, Jesper Kjeldgaard <thej...@gmail.com> wrote:
> That sounds very cool. (I'm a software engineer myself ;)
>
> I feel at home in the terminal so I will mostly use the app as an
> interface, not for editing.
>
> Looking forward to how the app will evolve.
>
> /Jesper
>