Just some notes for later

No errors in the console..

By the way I understand that manually putting something like {F123} in the article should allow to manually attach that file to the Phame Post object. So, I see and agree this is a separated problem related to Phame.

Can I ask you if you are on latest version? If yes, can I ask you if you have errors in your console? if yes, see this:

Honestly, do you still like this Diff after all these compromises? :D

Thank you for this patch. I also agree with @bekay since I'm also concerned about SEO. I tried to apply it.

Somewhat related - see T15050

For the record, I am against this change.

@speck I made this task because posts in Phame uses an ID that starts with J, and tasks in Maniphest uses T for the URL too.
I just request that the URL for posts in Phame changes to be similar to Maniphest.

Could you elaborate on what this would help with? I recall reading something in Phabricator’s past that the current url scheme is intentional as opposed to using the monogram/slug. I did a quick search and couldn’t find much, though in this change release
https://secure.phabricator.com/w/changelog/2015.51/

Removed dedicated titles/slugs. Phame posts now automatically generate readable URIs, but the slugs are no longer semantic.

We should investigate the history related to the current URL scheme before making a change. My suspicion is that it has to do with phase posts being “public” or published where having a url with part of the title is very common for linking across other content.

I mentioned on the diff but also mentioning here. Blog posts can be directed to users external of the system where monograms might be more confusing. Maybe we can find another place on the page to put the monogram that doesn't affect the title?