If we do this, one has to be designated "primary" (like Projects) so we can get a consistent default /u/xyz when rendering. This broadly seems like a lot of work for not a lot of payoff, to me, at least today.

User Guide: Prototype Applications

If a Phurl doesn't have a name, should we still show the empty name property on the object view?

If a Phurl doesn't have a name, should we still show the empty name property on the object view?

As mentioned in T9775, we think this would be a very useful feature for those of us who need to work on multiple projects. Having it tied to the flags application would make it awesomely customizable (and make Flags a much more useful application).

I'm just going to merge this into T5867

• The view page doesn't actually show the short URL anywhere. You can copy it from "View URL", but I think this isn't totally obvious, and we probably have enough room to reasonably add it (e.g., "Short URL: ..." under "Original URL: ...").
• If a link has an alias, "View URL" still links to the non-alias version (e.g. U6 links to /u/6, but a more-preferred link would be /u/bug).
• The "Remarkup Reference" document (https://secure.phabricator.com/book/phabricator/article/remarkup/) should explain how to use ((6)) and ((bug)). It might be worthwhile to hint these on the U6 page itself, e.g. In Remarkup: ((bug)) in the properties? Not sure how useful/cluttered that would look.
• Maybe show aliases on the list at /phurl/?
• Maybe let users search for the link with a particular alias? If I know ((bug)), there's no way for me to actually find the URL object right now. Hovercards would be one fix but just going to Phurl and being able to search for "Alias: bug" is probably good too.

Also "Active" in the Object Header should just be the normal color, not green. Our design pattern is "normal" states are plainly colored and exceptional states are actively colored. (red, green, purple).

Oh, transaction publishing from Phurl also currently fails in the daemons:

A couple of notes so far, after poking at this:

I'm starting to think Phurl is something entirely different than what I'm thinking of... Yup. Nevermind me then.

Used

./bin/config set phurl.short-uri http://p/

So I just tested this out, against: http://p/ and all I'm getting is a 404 page. Does it need to have a TLD?

(This is just a note for me to make sure I don't forget about it, I'll follow up here before we unprototype.)

Yep, this is good.

@epriestley This is already implemented, right? Checking that this doesn't entail anything more complex than what we already wrote.

I think this is wrapped up. Any loose ends should be added as separate tasks.

I don't think we need to auto-generate (and think it's slightly desirable not to -- I don't think we can do anything reasonable most of the time, and it will tend to make it harder to find a good alias when you actually want one if we do).

@epriestley I wrote in the original description (possibly after talking to you):

Should be an optional field that auto-generates a value if no value is given.

I think this is exceedingly mild/theoretical.

This is probably geared towards more public installs, where short urls could be abused, (such as this one).

Can you give me a specific scenario where this would be useful?

pretty neat and useful idea

Oh! I didn't notice the prototype tag all the way on the right (we have really wide monitors). That is totally fair. Apologies for wasting your time on prototype bugs.

@ox it literally was just started a few days ago, it should be more usable in a few weeks.

See T9022 / https://secure.phabricator.com/book/phabricator/article/prototypes/

I'm just going to close this and T9009 out under the "we know prototypes are super broken, wait until they unprototype before reporting bugs" rule, I think @lpriestley has a handle on it.

@chad: Not even eventually?

I don't believe Phurl is meant to be usuable.

As noted in D13759, there is also no route and no comment controller.

yup: https://secure.phabricator.com/diffusion/P/browse/master/src/applications/phurl/controller/PhabricatorPhurlURLViewController.php;b24935df2f74006c8221ee934c3d06b0781ac70b$48

Probably a getApplicationURI('phurl/x/') which should be getApplicationURI('x/').

+1 on this, we have phabricator on an internal searchdomain for our deploy. http://p/

Not sure that is needed, on intranets you can have sites like "http://someserver/some_folder/and.file" which isn't a valid public URL but is valid.

See also T5867

With my 'I have a corporate install' hat I think 'Alternate Short Domain' is needed for the 'Shortener' case to work out in practice. phabricator.mycompany.com is already longer than an entire t.co url. Those two features are probably enough to replace our current internal shortener thingy.

Walking through some use cases, roughly in increasing order of complexity, and general behaviors -- this is all me just imagining things, not necessarily the best way forward: