@recaptime-dev's working patches + fork for Phorge, a community fork of Phabricator. (Upstream dev and stable branches are at upstream/main and upstream/stable respectively.) hq.recaptime.dev/wiki/Phorge
phorge phabricator
1
fork

Configure Feed

Select the types of activity you want to include in your feed.

Replace random example domains with example.com

Summary:
The example.com domain is intentionally meant for such purposes.
Same game as rPab272edc or rP674ef80b.

Test Plan: None.

Reviewers: O1 Blessed Committers, mainframe98

Reviewed By: O1 Blessed Committers, mainframe98

Subscribers: tobiaswiese, valerio.bozzolan, Matthew, Cigaryno

Differential Revision: https://we.phorge.it/D26729

+4 -4
+1 -1
src/applications/config/option/PhabricatorMetaMTAConfigOptions.php
··· 23 23 $send_as_user_desc = $this->deformat(pht(<<<EODOC 24 24 When a user takes an action which generates an email notification (like 25 25 commenting on a Differential revision), the "From" address can either be set 26 - to the user's email address (like "alincoln@logcabin.com") or the 26 + to the user's email address (like "alincoln@example.com") or the 27 27 "metamta.default-address" address. 28 28 29 29 The user experience is generally better if the user's real address is used as
+2 -2
src/applications/metamta/storage/PhabricatorMetaMTAMail.php
··· 134 134 public function addRawTos(array $raw_email) { 135 135 136 136 // Strip addresses down to bare emails, since the MailAdapter API currently 137 - // requires we pass it just the address (like `alincoln@logcabin.org`), not 138 - // a full string like `"Abraham Lincoln" <alincoln@logcabin.org>`. 137 + // requires we pass it just the address (like `alincoln@example.com`), not 138 + // a full string like `"Abraham Lincoln" <alincoln@example.com>`. 139 139 foreach ($raw_email as $key => $email) { 140 140 $object = new PhutilEmailAddress($email); 141 141 $raw_email[$key] = $object->getAddress();
+1 -1
src/infrastructure/storage/management/PhabricatorStorageManagementAPI.php
··· 368 368 // characters. 369 369 // 370 370 // With "sort", if we use binary we lose case insensitivity (for 371 - // example, "ALincoln@logcabin.com" and "alincoln@logcabin.com" would no 371 + // example, "ALincoln@example.com" and "alincoln@example.com" would no 372 372 // longer be identified as the same email address). This can be very 373 373 // confusing and is far worse overall than not supporting 4-byte unicode 374 374 // characters, so we use 3-byte utf8 and accept limited 4-byte support as