I set up forestry on my father's bed and breakfast website. I am very pleased.

Glad to hear! I'd love to know how we could improv the experience if you have sky feedback

I'm using forestry for my company site now to give my non-tech cofounder an easy way to write blog posts.

Two suggestions that would really improve my life:

1. A better wysiwyg editor. I've taught her some markdown but every time you switch to wysiwyg and back and make a change I get loads of spans injected into my md.

2. A better media manager with: - folders - image resizing (maybe integrate filestack.io as they have some image manipulation)

I love the simplicity of forestry and it's really close to perfect for my use case. Github -> s3 is seamless and having edits committed back is great.

Thanks for the suggestion! #1 is in the works and #2 is in early planning stages.

I was unable to find anything that suggests this. Are you speculating?

Could be that, could be a troll, could be an actual Googler (355 Main Street is Google's address in Cambridge MA)

Probably speculating given the lifetime of most small-scale Google apps.

I can certainly see the value, I've fallen in love with build on save. I thought I would mention a solution here for people that wish to stay with their current browser but like the sound of automatic build.

I've been using a fork of fresh[1]. I haven't found a single issue yet. I simply cd to my project and run it.

[1] https://github.com/lateefj/fresh

I am extremely ignorant about this topic. But I don't think that's how it works. Can someone else weigh in please.

unsalted:

username | sha256 hash john123 | ef92b778bafe771e89245b89ecbc08a44a4e166c06659911881f383d4473e94f joe456 | ef92b778bafe771e89245b89ecbc08a44a4e166c06659911881f383d4473e94f

salted:

username | salt | sha256 hash john123 | ponies | 98d4c01710b2b775e41b0bf4984f0cec7621ae1dfc4304047b196af46ed589b2 joe456 | beards | 0f7c74279db5daa1f4de41cc7f6acc94651da754c41675dcde8dcf151d14f5bf

their passwords are all `password123`

The way the teaching was sequential really made it an understandable to a layman like myself.

The comment is terrible because you lack the qualifications to comment outside if your own personal expertise (whatever that may be). Second, assuming you get to comment, you will be working for free. Not much money. So yeah, two thumbs down. awful comment

See what I did there :P

I thought the same thing!

We'll be nice and give the author the benefit of the doubt and say it's juxtaposition :P

First time I giggled at a comment on here in a while (=

At first I agreed with you; but then I read one of the comments on github that swayed me.

"You are the one playing games - calling core parts of Windows like Explorer "3rd party tools", and suggesting that not supporting long paths is a bug. Microsoft have made it clear repeatedly that non-support for long paths is not a bug, and not something that will change.

A package manager creating paths that do not work with the majority of the software written for an OS, then claiming compatibility with the OS, is playing games, at your users expense."

At the end of the day Windows wont be the thing changing. haha.

I don't follow, should we then rename everything to cryptic, short characters like some people do in MongoDB (as someone suggested using n_m instead of node_modules)? If it works well in other platforms, it's an issue with that specific platform

windows has path length limits. Figure out how to live in them, whatever way is best. If that means using cryptic names, then do it. cryptic folder names, while not a good thing, are extremely common in windows.

Or, don't support Windows.

Yes, fine by me.

I think we're arguing different things. I'm more talking semantics.

Right, in practical terms it's up to Node to fix this (or go extreme and drop Windows support), but in a more abstract sense I still blame Microsoft for such a glaring design flaw in their software that they are unwilling/unable to fix.

Microsoft can decide to not call it a bug but that doesn't mean the rest of us don't believe it's a bug.

Here is a fork for anyone that hits this from google; https://github.com/Atraci/Atraci