Yes, but I have some hesitance around adding "search for a string in another string" fields without building better infrastructure first. There's some discussion in D14411#161139.

Ok, got it. Do you think it's reasonable to search using a package name?

We don't check that the path actually exists -- you might be searching for a deleted path that used to exist, or the repository might have a million branches and it only exists on one, and you might have a thousand different repositories too.

You are right for the cases you described. But the case I mentinoed is that /src/infrastructure/PhabricatorEditor.php doesn't exist in both Arcanist and libutil.

That result looks correct to me -- if a package includes "/", that means it includes everything under "/" too. So if you search for /x/y/z.cpp, any package that owns /, /x/, /x/y/ or /x/y/z.cpp will be returned, since any package owning a parent also owns the path itself.

In T9964#148566, @epriestley wrote:

I can't reproduce that. Here's a search using "Path", which seems to work correctly:

Can you give me more details about how to reproduce the issue you're seeing?

Happy enough for v1 for me.

D14748 should fix the double feed stories.

The behavior of TITLE and VISIBILITY are also wrong: they emit the current body text, not the body text at the time the change was made.

I think this is happening because both the "Title" and "Body" transactions are emitting text:

New blogs element is great :3

I can't reproduce that. Here's a search using "Path", which seems to work correctly:

You might already know, but I noticed that the owners search is broken if I use "path" instead of "Repositories" to query. Also it would be great if we can use the package name to search.

Multiple different ways of proceeding. Current way, while not bad, has it's downsides.

In T9897#148464, @epriestley wrote:

I eventually got this live. blog.phacility.com is a little plain now, but seems to work fine:

http://blog.phacility.com/

I eventually got this live. blog.phacility.com is a little plain now, but seems to work fine:

I'm planning to just remove skin support in T9897.

Just clarifying, is this link is considered PhameHome?
https://secure.phabricator.com/phame/

That is hypothetical, but for example, lets say Evan publishes a post with the following:
/blog/750/development_notes_2015_week_494949494949494/
but really meant for the slug to be
/blog/750/development_notes_2015_week_49/

Isn't that a hypothetical?

The easiest thing I can think of is simple typos/ bad c&p job

How are you expecting bad urls to get generated?

I have a concern about the /blog/<postid>/ignored_post_title/ approach, if the blog is indexed by Google, /blog/<postid>/ignored_post_title/ and /blog/<postid>/derpa/ will have the exact same content which Google penalizes.

We use SNI and nobody says it's bad. Hell, people actually WANT SNI, since when hositng fo example small shop, you basically need SSL (even cheap one), but IP address (especially IPv4) is pricey per month. Most people when faced with "additional $$$/month with only benefit being customers using ancient software" or "0/month additional charges, only lose handfull of ancient software-using customers" chose 0/month 😉

(You could put more ignore stuff in the route too if you want the blog title.)

You can probably just do that by adding a route like this:

ah yeah thats good enough

Yes, but blogs don't have slugs right now and blog post slugs are editable.

Also, I need to fix this:

is it relatively easy to do with routes, something like /b/blog_title/blog_post/

The story on SNI actually looks pretty reasonable (we're mostly just losing IE on XP and very old mobile devices), and should be more reasonable by the time we're thinking about whitelabeling main instances.

It's also possible that we can roll our own loadbalancers by assigning a lot of elastic IPs to a single host. This currently allows us to put ~240 domains on a host, at a cost of ~$4 per domain per month (for the elastic IP) instead of ~$20 per domain per month, but is more work. In contrast, SNI would let us put thousands of domains on a host with no cost per domain.

One other thing is that custom domains won't work on Phacility by default, and I don't think we can easily make them work (we can't just have users CNAME their DNS because we won't have the right SSL certificate). So maybe that's an argument for removing the feature or adding an option (ugh) to disable it.

I should probably add a subscriber setting for posts too, though.

Ah sorry, thanks for the clarification. I also just remembered that it's still prototype.

You have blogs set to ignore subscriber changes, not posts (not really a setting for that).