epriest

6 ms·

1.
by epriest 6y ago
I think mouse users don't generally suffer from this problem: by default, MacOS always shows a scrollbar in all contexts if you have a mouse plugged in to your computer.
2.
by epriest 6y ago
This is not accurate. You can report bugs, etc., on the community forum here, which has open registration: https://discourse.phabricator-community.org/
3.
by epriest 6y ago
I mean that GitHub does not "try", in the sense of looking at the interdiff, doing fuzzy matching, trying to identify line-by-line similarity, etc. It places comments only if the hunk is exactly unchanged and gives up otherwise. P
4.
by epriest 6y ago
GitHub's implementation does not do what you claim it does. GitHub has no behavior around porting and placing comments (while Phabricator does), GitHub just hides anything it can't place exactly. See my link above for a detaile
5.
by epriest 6y ago
In particular, see < https://secure.phabricator.com/T7447#112231 > for a specific example which I believe GitHub's implementation gets egregiously wrong, by silently discarding an inline which is highly relevant to
6.
by epriest 6y ago
This is not (and has never been) the behavior of Phabricator. See < https://secure.phabricator.com/T7447 > for discussion of why this feature can never work the way you think it should work in the general case and why I
7.
by epriest 6y ago
Open source projects generally want an exact feature-for-feature copy of GitHub that looks and works exactly like GitHub, except open source. If Phabricator was this, there would be no reason for paying customers to ever choose it over Gi
8.
by epriest 6y ago
Facebook has not provided any contributions or material support to the open source version of Phabricator since around 2012.
9.
by epriest 6y ago
In my view, refocusing the roadmap on only requests from paying customers was possibly the best change I've made for the health and longevity of the project.
10.
by epriest 6y ago
Can you point me at any data which supports this? It seems like it should be true, but GHC didn't appear to see a year-over-year increase to contributors when they switched from Phabricator to GitLab in December 2018. See: https:&#x2F
11.
by epriest 6y ago
Do you have data to support this claim? For example, GHC moved from Phabricator to GitLab in December 2018, citing ease of contribution as a major benefit: https://twitter.com/bgamari/status/1069047550727069696 As
12.
by epriest 6y ago
Why do you believe Phabricator is practically abandoned?
13.
by epriest 6y ago
Interesting! This isn't how I remember things at all. Do you know where you got this sense of things from, specifically? In particular, do you remember what gave you the impression that Facebook "overinvested" a large amount
14.
by epriest 6y ago
Here's the answer to that question, from the second paragraph of the linked article: > Facebook officials said they bought the masks for their offices’ emergency disaster kits following wildfires in California.
15.
by epriest 7y ago
I found this article on this topic from a lawfirm specializing in entertainment law interesting: https://rodriqueslaw.com/blog/how-use-brands-and-products-fi... It references some of the existing caselaw. My reading su
16.
by epriest 7y ago
The title claim is untrue and trivially falsifiable, but I haven't seen any articles that have actually made an effort to verify it. Here are screens from two recent movies where villainous characters use iPhones: https://pr
17.
by epriest 7y ago
"Merman" was an internal project codename, not an individual user. I think it was a very early version of the feature that eventually became "Pages".
18.
by epriest 8y ago
I can't speak beyond 2011, but in the early part of the last decade you're giving Facebook far too much credit. Facebook went down for most of a day in ~2009 because a new hire mistakenly removed the memcached server config in sit
19.
by epriest 8y ago
Here's how to actually "solve" this problem on an iPhone: - Pay $1.99 to buy a silent ringtone from the ringtone store. - Make that your default ringtone. - Give everyone who you want to be able to call you an audible rington
20.
by epriest 8y ago
> For online attacks, an attacker can't even try the top 1000 passwords on for an account in any major website in reasonable time without triggering the alarm, as they all(?) have rate limiting (usually in the form of account lockdo
21.
You Must Sign Our CLA(secure.phabricator.com)
3 points by epriest 8y ago|0 comments
22.
by epriest 8y ago
I've contributed some code to Phabricator, happy to answer any questions about why that code is so bad. Phabricator is primarily aimed at teams with multiple approximately-full-time engineers working on projects together, and focuses m
23.
by epriest 9y ago
Attackers could otherwise verify that resources on private networks or retrievable only with the victim's cookies have certain content. See, e.g., < https://github.com/w3c/webappsec/issues/418> for
24.
by epriest 10y ago
We've been working hard to remove features, introduce bugs, and decrease quality throughout the year.
25.
by epriest 11y ago
Facebook has had essentially no involvement in Phabricator for several years.
26.
by epriest 12y ago
I originally wrote this when I worked at Facebook. The intended audience (who were submitting these reports at the time) was professional software engineers.
27.
by epriest 12y ago
This has changed; we've supported hosted repositories since late 2013.
28.
by epriest 12y ago
You can set who can view a project with Edit Project > Visible To.
29.
by epriest 12y ago
What are you missing from Phabricator? https://secure.phabricator.com/book/phabcontrib/article/feat...
30.
by epriest 12y ago
Underlying writes go to Git, Mercurial and SVN. Generally speaking, we proxy requests and pass them through to the VCS after performing authentication and broad permission checks. Requests are rewritten slightly to remap user-facing display

More ›