It's a 720x1440 device, which is on the low end of screen resolutions nowadays.

Here is the commit that introduced this

In T15055#1426, @speck wrote:

The effort to rebrand Phabricator is going to result in changes to a lot of text which would likely invalidate a large number of translation entries.

It is not very clear to understand where the problem is and how to try to help improve it. I am not familiar with Pirate English. Other than adding "Arrr." I mean.

trim whitespace from name and email

In T15059#1654, @speck wrote:

I just checked the emails I receive to my gmail account and noticed that the emails seem to be from the secure.phorge.dev domain. Should those be received from we.phorge.it instead? I was in the process of filling out an issue form for Microsoft and noticed this discrepancy. Could that cause issues like this?

fix lint issues

In T15059#1654, @speck wrote:

I just checked the emails I receive to my gmail account and noticed that the emails seem to be from the secure.phorge.dev domain. Should those be received from we.phorge.it instead? I was in the process of filling out an issue form for Microsoft and noticed this discrepancy. Could that cause issues like this?

I just checked the emails I receive to my gmail account and noticed that the emails seem to be from the secure.phorge.dev domain. Should those be received from we.phorge.it instead? I was in the process of filling out an issue form for Microsoft and noticed this discrepancy. Could that cause issues like this?

I noticed this recently too. These PHP 8 updates have been frustrating because it breaks Arcanist for users as well...

Time tracking is an interesting topic. At my company we addressed this by having a Herald WebHook hit our internal server whenever activity we're interested in tracking happens. Our internal server tracks these activities from multiple sources (not just Phab/Phorge) and users can go in to see all their activity linked up and input the approximate time spent on those activities.

A few months back this story came up on hackernews which seems relevant. There might be things in there we can attempt to appeal to Microsoft to allow emails from this Phorge instance to go through

What mobile display are you using? From the screenshots it looks like based on the dimensions of the display phorge isn't detecting that it should render as mobile view.

I think updating the current pem file is a good holdover patch for now (sorry for the delay in reviewing the change). Re-working how arcanist manages certs is something we can look at addressing long-term.

I computed the sha256 sum of the change/updated file and verified that it matches the cert file on https://curl.se/docs/caextract.html for 2021-09-30.

After making lots of changes in my clone to suppress deprecation warnings, I am stuck at the following error.
[Wed Dec 01 16:06:24.853494 2021] [proxy_fcgi:error] [pid 2472770:tid 139879417599744] [client <REDACTED>] AH01071: Got error 'PHP message: [2021-12-01 16:06:24] EXCEPTION: (Exception) Bad getter call: getPreferences at [<phabricator>/src/infrastructure/storage/lisk/LiskDAO.php:1620]
PHP message: arcanist(head=master, ref.master=c53bb21bbd3e), phabricator(head=master, ref.master=4448a93a4067), testwiki-ext-misc(head=master, ref.master=c12e85d3a97a)
PHP message: #0 <#2> LiskDAO::call(string, array) called at [<phabricator>/src/infrastructure/storage/lisk/LiskDAO.php:1598]
PHP message: #1 <#2> LiskDAO::call(string, array) called at [<phabricator>/src/applications/people/storage/PhabricatorUser.php:446]
PHP message: #2 <#2> PhabricatorUser::loadGlobalSettings() called at [<phabricator>/src/applications/people/storage/PhabricatorUser.php:377]
PHP message: #3 <#2> PhabricatorUser::getUserSetting(string) called at [<phabricator>/src/applications/people/storage/PhabricatorUser.php:428]
PHP message: #4 <#2> PhabricatorUser::getTranslation() called at [<phabricator>/src/applications/auth/engine/PhabricatorAuthSessionEngine.php:1127]
PHP message: #5 <#2> PhabricatorAuthSessionEngine::willServeRequestForUser(PhabricatorUser) called at [<phabricator>/src/applications/base/controller/PhabricatorController.php:109]
PHP message: #6 <#2> PhabricatorController::willBeginExecution() called at [<phabricator>/src/aphront/configuration/AphrontApplicationConfiguration.php:271]
PHP message: #7 phlog(Exception) called at [<phabricator>/src/aphront/handler/PhabricatorDefaultRequestExceptionHandler.php:41]
PHP message: #8 PhabricatorDefaultRequestExceptionHandler::handleRequestThrowable(AphrontRequest, Exception) called at [<phabricator>/src/aphront/configuration/AphrontApplicationConfiguration.php:751]
PHP message: #9 AphrontApplicationConfiguration::handleThrowable(Exception) called at [<phabricator>/src/aphront/configuration/AphrontApplicationConfiguration.php:296]
PHP message: #10 AphrontApplicationConfiguration::processRequest(AphrontRequest, PhutilDeferredLog, AphrontPHPHTTPSink, MultimeterControl) called at [<phabricator>/src/aphront/configuration/AphrontApplicationConfiguration.php:204]
PHP message Log, AphrontPHPHTTPSink, MultimeterControl) called at [<phabricator>/src/aphront/configuration/AphrontApplicationConfiguration.php:204]
PHP messaghutilDeferredLog, AphrontPHPHTTPSink, MultimeterControl) called at [<phabricator>/src/aphront/configuration/AphrontApplicationConfiguration.php:204]PHP messaguration.php:204]
PHP messaglicationConfiguration.php:204]PHP messagont/configuration/AphrontApplicationConfiguration.php:204]
PHP messagd at [<phabricator>/src/aphront/configuration/AphrontApplicationConfiguration.php:204]
PHP message aphrontPHPHTTPSink, MultimeterControl) called at [<phabricator>/src/aphront/configuration/AphrontApplicationConfiguration.php:204]
PHP message: #11 AphrontApplicationConfiguration::runHTTPRequest(AphrontPHPHTTPSink) called at [<phabricator>/webroot/index.php:35]PHP message: [2021-12-01 16:06:24] EXCEPTION: (PhutilAggregateException) Encountered a processing exception, then another exception when trying to build a response for the first exception.\n - Exception: Bad setter call: setUserPHID\n - Exception: Bad getter call: getPreferences at [<phabricator>/src/aphront/configuration/AphrontApplicationConfiguration.php:316]
PHP message: arcanist(head=master, ref.master=c53bb21bbd3e), phabricator(head=master, ref.master=4448a93a4067), testwiki-ext-misc(head=master, ref.master=c12e85d3a97a)
PHP message: #0 <#4> LiskDAO::call(string, array) called at [<phabricator>/src/applications/people/storage/PhabricatorUser.php:446]
PHP message: #1 <#4> PhabricatorUser::loadGlobalSettings() called at [<phabricator>/src/applications/people/storage/PhabricatorUser.php:377]
PHP message: #2 <#4> PhabricatorUser::getUserSetting(string) called at [<phabricator>/src/applications/people/storage/PhabricatorUser.php:428]
PHP message: #3 <#4> PhabricatorUser::getTranslation() called at [<phabricator>/src/applications/auth/engine/PhabricatorAuthSessionEngine.php:1127]
PHP message: #4 <#4> PhabricatorAuthSessionEngine::willServeRequestForUser(PhabricatorUser) called at [<phabricator>/src/applications/base/controller/PhabricatorController.php:109]
PHP message: #5 <#4> PhabricatorController::willBeginExecution() called at [<phabricator>/src/aphront/configuration/AphrontApplicationConfiguration.php:271]
PHP message: #6 <#3> LiskDAO::call(string, array) called at [<phabricator>/src/infrastructure/storage/lisk/LiskDAO.php:1598]
PHP message: #7 <#3> LiskDAO::__call(string, array) called at [<phabricator>/src/applications/search/engine/PhabricatorApplicationSearchEngine.php:666]PHP message: #8 <#3> PhabricatorApplicationSearchEngine::getBuiltinQueries() called at [<phabricator>/src/applications/search/engine/PhabricatorApplicationSearchEngine.php:500]
PHP message: #9 <#3> PhabricatorApplicationSearchEngine::loadAllNamedQueries() called at [<phabricator>/src/applications/search/engine/PhabricatorApplicationSearchEngine.php:537]
PHP message: #10 <#3> PhabricatorApplicationSearchEngine::loadEnabledNamedQueries() called at [<phabricator>/src/view/page/menu/PhabricatorMainMenuSearchView.php:157]
PHP message: #11 <#3> PhabricatorMainMenuSearchView::getGlobalSearchScopeItems(PhabricatorUser, PhabricatorFlagsApplication) called at [<phabricator>/src/view/page/menu/PhabricatorMainMenuSearchView.php:205]
PHP message: #12 <#3> PhabricatorMainMenuSearchView::buildModeSelector(string, string) called at [<phabricator>/src/view/page/menu/PhabricatorMainMenuSearchView.php:89]
PHP message: #13 <#3> javelin_tag(string, array, array) called at [<phabricator>/src/view/phui/PHUIListItemView.php:426]
PHP message: #14 <#3> phutil_tag(string, array, array) called at [<phabricator>/src/infrastructure/javelin/markup.php:70]
PHP message: #15 <#3> javelin_tag(string, array, array) called at [<phabricator>/src/view/AphrontTagView.php:161]
PHP message: #16 <#3> AphrontTagView::render() called at [<phabricator>/src/view/AphrontView.php:222]
PHP message: #17 <#3> AphrontView::producePhutilSafeHTML() called at [<phabricator>/src/infrastructure/markup/render.php:111]
PHP message: #18 <#3> phutil_escape_html(PHUIListView) called at [<phabricator>/src/infrastructure/markup/render.php:135]
PHP message: #19 <#3> phutil_escape_html(array) called at [<phabricator>/src/infrastructure/markup/render.php:97]
PHP message: #20 <#3> phutil_tag(string, array, array) called at [<phabricator>/src/view/page/menu/PhabricatorMainMenuView.php:168]
PHP message: #21 <#3> PhabricatorMainMenuView::render() called at [<phabricator>/src/view/page/PhabricatorStandardPageView.php:374]
PHP message: #22 <#3> PhabricatorStandardPageView::willRenderPage() called at [<phabricator>/src/view/page/AphrontPageView.php:46]
PHP message: #23 <#3> AphrontPageView::render() called at [<phabricator>/src/applications/base/controller/PhabricatorController.php:286]
PHP message: #24 <#3> PhabricatorController::willSendResponse(AphrontDialogResponse) called at [<phabricator>/src/aphront/configuration/AphrontApplicationConfiguration.php:300]
PHP message: #25 <#2> AphrontApplicationConfiguration::processRequest(AphrontRequest, PhutilDeferredLog, AphrontPHPHTTPSink, MultimeterControl) called at [<phabricator>/src/aphront/configuration/AphrontApplicationConfiguration.php:204]
PHP message: #26 <#2> AphrontApplicationConfiguration::runHTTPRequest(AphrontPHPHTTPSink) called at [<phabricator>/webroot/index.php:35]
PHP message: #27 phlog(PhutilAggregateException) called at [<phabricator>/src/aphront/response/AphrontUnhandledExceptionResponse.php:32]
PHP message: #28 AphrontUnhandledExceptionResponse::setException(PhutilAggregateException) called at [<phabricator>/webroot/index.php:46]'

I submitted a draft revision for this. It's not quite complete yet, but anyone interested can take a look at it.

I think this task is mostly resolved. The zulip chat is a temporary thing, and it hasn't been used anytime recently. We could bridge the IRC channel to it if we wanted to have a more permanent zulip instance.

In T15043#1618, @20after4 wrote:

I didn't know columns could be deleted... I thought they were only ever hidden.

I didn't know columns could be deleted... I thought they were only ever hidden.

I'd definitely love to see this later. I MIGHT be able to get to this later.

In T15045#1613, @goddenrich wrote:

Is there an update on this? we would love to see this feature soon

Is there an update on this? we would love to see this feature soon

This looks pretty great! - I think T15030 is the general covering task for Extensions

Thanks -- I'm curious as to what makes this not particularly suitable for development, though?

Although there's merit to the "zero, one, infinity" rule, it might not be the best option here. If something goes wrong and $err happens to always be falsy, this will end up in an infinite loop instead of giving a clear error message. There is probably a reasonable finite value (that's greater than 4) which can be chosen as the limit to the number of attempts.

Thanks for the ping, @MacFan4000. I am in and out because this is my last full-time semester, but I do see the room and have been checking in on it.

We had a similar issue with Microsoft email on our own custom mail server. Microsoft delivers mail for several domains from the same email service, so this similarly affects email from outlook.com, hotmail.com, live.com and msn.com. See https://postmaster.live.com/pm/policies.aspx for details.

This is likely related more to the configuration of the email server. Outlook is very picky, and as far as I know, checks the headers for all of the following:

I can confirm as well that I have never received an email from phorge / phabricator on my email which isn't "outlook.com" but is an office 365 email account

Do you have any additional repro steps? Mail config will be specific to the Phab/Phorge install. If this is specific to our Phorge installation, yeah... it's sucky. We self-host our email server and that means we're subject to all of the arcane and mystic requirements there. As far as we can tell, it's set up as correctly as is possible (SPF, DKIM, DMARC all configured correctly; domain is old enough that it doesn't negatively impact our trust scores; etc.). (A current spam test result for reference.)

@valerio.bozzolan Fancy seeing you here. I'm Void from your phabricator instance.

In T15033#1512, @golyalpha wrote:

Yes, that's why I'm saying "yeah, great idea, let's do this, but let's also create a config toggle so that it can be disabled for people and orgs who don't need it".

Please revert this @chris

In T15033#1516, @gadgetsteve wrote:

@golyalpha As my current employer is one of the largish companies, (50,000+ international employees), but not primarily software focused we have all been given GDPR awareness training but do not have a general, all employees, GDPR statement available nor a standard text or set of texts to use.
When I was deploying a Phabricator instance I actually had to come up with the wording myself and then get it approved by the legal & compliance team - my biggest hurdle was convincing them of the required data retention period - they were much more used to systems such as payroll & HR where records are only retained for a fixed number of years after the period of employment as demanded by things like the local tax regulations and the idea that due to legal liability, etc., we needed to retain the information for the full life of the product being developed and possibly beyond if components were reused.

@dcog Just:

In T15033#1516, @gadgetsteve wrote:

@golyalpha As my current employer is one of the largish companies, (50,000+ international employees), but not primarily software focused we have all been given GDPR awareness training but do not have a general, all employees, GDPR statement available nor a standard text or set of texts to use.
When I was deploying a Phabricator instance I actually had to come up with the wording myself and then get it approved by the legal & compliance team - my biggest hurdle was convincing them of the required data retention period - they were much more used to systems such as payroll & HR where records are only retained for a fixed number of years after the period of employment as demanded by things like the local tax regulations and the idea that due to legal liability, etc., we needed to retain the information for the full life of the product being developed and possibly beyond if components were reused.

@golyalpha As my current employer is one of the largish companies, (50,000+ international employees), but not primarily software focused we have all been given GDPR awareness training but do not have a general, all employees, GDPR statement available nor a standard text or set of texts to use.
When I was deploying a Phabricator instance I actually had to come up with the wording myself and then get it approved by the legal & compliance team - my biggest hurdle was convincing them of the required data retention period - they were much more used to systems such as payroll & HR where records are only retained for a fixed number of years after the period of employment as demanded by things like the local tax regulations and the idea that due to legal liability, etc., we needed to retain the information for the full life of the product being developed and possibly beyond if components were reused.

I18n is also fairly important from the point of view that citizens in certain jurisdictions are basically legally immune against documents written in a language different from the official language of their jurisdiction, so, +1 on that.

Would it worth considering having multiple versions available with which is displayed determined by locale & language selection, (I18n & I10n). Then places with specific legislation could display the boilerplate or customised version and places without could, potentially, mention it with a link rather than having a specific sign-off and also linguistic problems could be addressed by the instance maintainer(s).

@Labricator Definitely - as potentially contributors can be from anywhere in the world, including places with GDPR or equivalent legislation. (Note that I am In Wales, UK so would be covered). I am reasonably sure, not a lawyer remember, the legislation is written in such a way that you can't get away with things like "the data is stored somewhere without DGPR so it doesn't apply", etc.

Yes, that's why I'm saying "yeah, great idea, let's do this, but let's also create a config toggle so that it can be disabled for people and orgs who don't need it".

What about the public versions? It still should have a GDPR notification.

Yes, the GDPR notice must inform about each and every purpose specifically. But it must do so only once - that can be at sign up.

The EU & UK GDPR provisions are very specific that each data gathering application must inform the user:

It's not just visual - I'm actually unable to open the individual tasks.

+1 to removing default.pem
/shrug on keeping custom.pem

This is what the README says - And maybe we should remove support for the default.pem altogether? (But, possibly leave support for custom.pem)