Yep, thanks. I did just mean point value and the pointers to the new project designs I think solves any questions I might have.

Sounds like it's being tackled. Thanks for the triage.

👍

Yup! When I regenerate the graph it's well-sized.

I'll confirm in a moment.

It's a similar looking problem. Indeed, it has a similar solution!

Updated to head—no dice.

It's not, but it's fairly recent. I'm on Chrome and I'll try an upgrade.

Yeah, totally. That sounds like it's in the same direction.

Yeah, I agree that model is slimey. It's strict trick and sunk cost fallacy instead of progressive value increase. I think segmentation is fine when it leads to opening the ability for more people to receive value... Not when it just tricks people into buying more.

So, let me first walk out my use case a bit further.

That's a good point and a perfectly workable solution—good call.

This does appear to resolve my immediate needs very nicely. I'll take a look at using this feature later today.

I appreciate your concern for safety!

Cool!

Perhaps a warning when searching for words which are below the current known ft_min_word_len would demystify the behavior.

It works appropriately in workboards, but e.g.

Oh, good call! For the moment, I'll just try to use longer key words.

Yup, here's how you replicate

Nope, Yup: this is what I mean

It sort of feels like the "grey" state is when the workboard is waiting on the server to update the new list position. It could be that it's timing out or otherwise failing on my computer right now. I haven't yet been able to replicate it with developer console open—I don't yet see anything weird.

Just replicated that one on the test page :)

You know what it was? I wrote "#project." since it was at the end of a sentence. I'm not sure if that's a parser bug for the tags or just intended behavior.

I just replicated it again. Typically what occurs is after a few drags upon drop a Task box freezes in "selected" state (e.g. darker grey) and then no more boxes can be dragged.

Version: Safari Version 8.0 (10600.1.25), OS X 10.10 Yosemite
Phabricator: 1120c465e480f503686ab503e2cf1e1f1b6cf16d

How does that work on edits? Each time the document is saved the links will "re-reference"?

Cool, that's basically perfect once it works with Phriction. Will links established prior to Phriction getting up to speed be ported?