awesum!

The problem with taking bug reports on prototypes is it assumes a direction in the product (ie, that this page will exist in this form). Right now I want to hold off on bug reports until something closer to "unbeta" is ready to hit. I do currently plan to build one-off UI components so Phame is more than just Maniphest or Ponder.

The difficulty in taking bugs is that it assumes a direction, and right now I'm not sold on a direction of keeping "skins". I'd rather take a really solid pass at "NoSkin" and leave it at that for v1, and maybe look at skins again in v2. Mostly though @epriestley and I haven't really discussed it much, so the direction remains up in the air. Phame was something I've considered working on in some spare time.

I am aware of that, but as @epriestley added some tasks for Phame, I thought: "why not had some more". :-)

Phame is a prototype application, and will likely undergo heavy reworking before it's ready for production.

Gotta have long-term plans, eh?

Well, I don't expect to actually fix any of this for like 20-30 years, I'm just filing it.

yesss! ❤️

The actual skin would also be bad for a Medium-alike with a huge image of a tree or a house or whatever at the top since you couldn't preview it meaningfully.

I'm trying out Phame for providing companion notes to the Changelog so I'm going to file some stuff I hit. This is probably mostly stuff that we would have naturally fixed anyway, but some of it isn't totally obvious.

at least, I think I converted it all the way.

Phame is on ApplicationSearch, so the bug is something else.

Thanks for the feedback on Phame, we don't have a firm plan on where it's going to end up, but "internal blogging tool" is likely the most likely place it will end up down the road. We have no current plans to prioritize work on it, though.

Resolved-ish, will improve more down the road.

Phame is a prototype application. See this guide for more information:

I would like to use this to keep my users updated about recent changes of our Phabricator instance.

This should be resolved in HEAD. Thanks for the report!

@epriestley thx Evan - please let us know if there's a workaround. We use these weekly blogs to track everyone's work so right now we can't monitor folks' work anymore.

See also T6403 for a longer-term fix for this.

Haha, sorry, figured I was doing slightly better than that. This should be easy to fix up.

Well, this is certainly fun drive with policies and edge cases...

D12793 might be missing some edge cases with unusual objects but should fix at least 95% of this. Let me know if you run into more cases after D12793 lands.

Sorry, we don't accept feature requests for prototype applications like Phame. See:

Phame doesn't use application transactions so the fix here is to move it over to use an Editor + transactions and this comes for free.

(In fact, there's no attached tab even present)

If it helps, the phame post doesn't show up under the 'attached' tab on the
file.

Sorry, misread. Ignore me. This is probably a bug on our side.

If you're sure other users can't see them, update to HEAD.

This issue is present also on https://secure.phabricator.com - namely: try cklickin on any author inside http://blog.phacility.com Links point to http://blog.phacility.com/p/btrahan/ instead of https://secure.phabricator.com/p/btrahan/ (should be @btrahan) and result in 404.

Just my 2 cents -- I would find it very useful if there was a dashboard panel that could display an arbitrary atom feed -- including, of course, a Phame feed.

Same issue with any link to Phabricator object, like tasks.

Closed by commit rPa4b281aa2916.