GitHub ticket #5929 disappeared (official Arch Linux template)

Rusty Bird

unread,

May 10, 2021, 6:27:46 AM5/10/21

to qubes...@googlegroups.com

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

I was trying to check on the status of the Arch Linux template, but
the issue ticket[1] has disappeared ("Page not found"). Maybe it's
caught in a GitHub spam filter?

(archive.org has a single old capture[2] that's definitely missing
some updates.)

Rusty

1. https://github.com/QubesOS/qubes-issues/issues/5929
2. https://web.archive.org/web/20201020010612/https://github.com/QubesOS/qubes-issues/issues/5929
-----BEGIN PGP SIGNATURE-----

iQKTBAEBCgB9FiEEhLWbz8YrEp/hsG0ERp149HqvKt8FAmCZCplfFIAAAAAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDg0
QjU5QkNGQzYyQjEyOUZFMUIwNkQwNDQ2OUQ3OEY0N0FBRjJBREYACgkQRp149Hqv
Kt9unw/+MCFvFppc/iy0icFNP8yiSynwgce8RPBMqs6U2zErIGBbP10zmsakot7f
QmsBTciaabCD/wfV8U4IRI1AD5nJz6ZiLnVlYNJjbI7Nd8/2cyI5qg4rOXtg0Fm4
RMM7mGqajbhl4iJ+DV1jmcfTrqG5hGL8mzkX55UTyE/GheElnLUN0PeI2cYCXnd1
JEUOoo3QC0gjstkRMetWACXKNd/w7VPnR2u/gf2LyxcQsMfQ0YM7d2DDKKUDxzlX
ohELDFJvVNRpFYU5JfiPIwwPtqGn3QlO0qME8sxM+zVn5QANJGy4H0wS9y/vBM3o
Uo91wy+WBoS1eGnnwEKPQT0Xab+wL0Iri4zYf7yEM0a2fBCrCj9XCcSSO+iBfbLo
jqrfpZN8u9/K7ym9jAYQTl11GDRC8bHZH2rYWx8sxOwO9WGMEo4nvxsi9eMnH7l7
c9iHRKtUgUik3OqmrWZ2Toa6/yK5zFziRFgtq3qgpT+/HMSEC06GdkgYiB15DU5n
2WsLRYgUEwavjkR7GMQ4G7iz2BiFSLycOz/YEKpmbpD+lNPG1p554emSew+sb2Mp
AFemSgnYifSsYyNsZ1F/Bk1MdBY3gH95+x++PwuPJKyvp5YtWtUIgFmP2dm+QmAY
SS/QNicKORByaGy+NEIpUUZgYrc5HQwzmIw2+0wJ4hj6LHRcwYc=
=lHm9
-----END PGP SIGNATURE-----

Marek Marczykowski-Górecki

unread,

May 10, 2021, 6:58:25 AM5/10/21

to qubes...@googlegroups.com

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On Mon, May 10, 2021 at 10:27:38AM +0000, Rusty Bird wrote:
> I was trying to check on the status of the Arch Linux template, but
> the issue ticket[1] has disappeared ("Page not found"). Maybe it's
> caught in a GitHub spam filter?

Likely yes, for some weird reason. I've asked github support to restore
it.

- --
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEEhrpukzGPukRmQqkK24/THMrX1ywFAmCZEcoACgkQ24/THMrX
1yx6Mgf/cSsfJuvZFeJQWxUSrSQUBRMa0YZLlojZOIMx16JRpz00ndbAD6IWdKUx
oky6YzesxFiiCgTpI9X5WFZVIuPgSqH6fND8CIc7hTuerabh/NMdGBSNGGBxrw7q
zKQkamLRFR0elLkcCJVAdZStlBUXVZzjZmlk+fRCxFryH6weDtSstdXYtzThGnUo
boTZ1aLF5soMd8vcdTgZCE1qv3kwDGPO9kOtzuhW0ZNpj12gF16KMywyj1vA8DMq
UJ9EQwv8bNPNPLsl/BITd0BgWuhqWrZM8EfesHpNUeZZa0+5r2jfRIhMQ8eT+QPs
XvbbpqQO9plJLbUuhX8WpLEqQz+U8Q==
=wKBV
-----END PGP SIGNATURE-----

Rusty Bird

unread,

May 10, 2021, 8:31:18 AM5/10/21

to Marek Marczykowski-Górecki, qubes...@googlegroups.com

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Marek Marczykowski-Górecki:

> On Mon, May 10, 2021 at 10:27:38AM +0000, Rusty Bird wrote:
> > I was trying to check on the status of the Arch Linux template, but
> > the issue ticket[1] has disappeared ("Page not found"). Maybe it's
> > caught in a GitHub spam filter?
>
> Likely yes, for some weird reason. I've asked github support to restore
> it.

Marek Marczykowski-Górecki

unread,

May 10, 2021, 9:42:17 AM5/10/21

to qubes...@googlegroups.com

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On Mon, May 10, 2021 at 11:56:51AM +0000, Rusty Bird wrote:
> Marek Marczykowski-Górecki:
> > On Mon, May 10, 2021 at 10:27:38AM +0000, Rusty Bird wrote:
> > > I was trying to check on the status of the Arch Linux template, but
> > > the issue ticket[1] has disappeared ("Page not found"). Maybe it's
> > > caught in a GitHub spam filter?
> >
> > Likely yes, for some weird reason. I've asked github support to restore
> > it.
>
> After a couple of GitHub API requests, it looks like they're currently
> memory-holing 43 issues:
>

Thanks for the list. Based on it, I've searched the github export I do
from time to time, and I can confirm most of them are not spam (at least
looking at the title, haven't checked the body).
Specifically this list:

https://github.com/QubesOS/qubes-issues/issues/3119
https://github.com/QubesOS/qubes-issues/issues/3272

https://github.com/QubesOS/qubes-issues/issues/5928
https://github.com/QubesOS/qubes-issues/issues/5929
https://github.com/QubesOS/qubes-issues/issues/6415
https://github.com/QubesOS/qubes-issues/issues/6422 (dupplicate of 6415)
https://github.com/QubesOS/qubes-issues/issues/6451
https://github.com/QubesOS/qubes-issues/issues/6452 (dupplicate of 6451)

That said, many of them are misplaced and were immediately closed as
"invalid" as they should be rather posted to forum or ML.

I'll add them to the list in github support request...

- --
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEEhrpukzGPukRmQqkK24/THMrX1ywFAmCZODAACgkQ24/THMrX
1ywp2Qf+Km1AKKPvsC4lUx9Lra0MfpJAiSMVm8dccQWyWrokO+VjDqF+mB5wrBvX
6j4hBxngg1BfWlPwLblC1oX8S+GtEjc9CHrGI3vpYYB1acl4p48KTK5wTQorv3um
niYJCcQWEQNj0EYRSW0pGgnSMq7hm4/a6N44sLyyveOV9RwX96J9UnM+sCBF1WyT
OjL7RAqbVtrl7qdXJKxByG2M0TVCw391QhOQosFsjdJMdWL6soG+0Fm361sa4JfV
LaA3SMhEEpHcxyzzQo3y5U4royGLBiUDRh683hzW6X9IyFTb9w2c1rwoypG4CqJT
4tYHj8jxFg2CRR86KY8biTw2Mlagzg==
=VMuG
-----END PGP SIGNATURE-----

Rusty Bird

unread,

Apr 20, 2022, 8:43:03 AM4/20/22

to Marek Marczykowski-Górecki, qubes...@googlegroups.com

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Did you ever hear back from them?

I just read something disturbing that might be relevant:

| Apparently, “suspending an account” on GitHub actually means *deleting
| all activity for a user* — which results in (1) every pull request
| from the suspended account being *deleted*, (2) every issue opened by
| the suspended account being *deleted*, (3) every comment or discussion
| from the suspended account being *deleted*. In effect, the user’s
| entire activity and history is evaporated.

| All of a sudden, I was seeing pull requests, issues, and comments
| disappear from users who were actively contributing to the project.
| *We lost valuable contributions, information, context, and discussion
| history* on issues and pull requests. We even lost pull requests that
| were open and under active review. That work is now entirely lost.
| Gone forever. For pull requests that _did_ merge, we have the raw
| commit history — but that is not a substitute for a full code review
| and discussion.

https://www.jessesquires.com/blog/2022/04/19/github-suspending-russian-accounts/

Rusty
-----BEGIN PGP SIGNATURE-----

iQKTBAEBCgB9FiEEhLWbz8YrEp/hsG0ERp149HqvKt8FAmJf/XhfFIAAAAAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDg0
QjU5QkNGQzYyQjEyOUZFMUIwNkQwNDQ2OUQ3OEY0N0FBRjJBREYACgkQRp149Hqv
Kt+xcA//ceynKL9MVTNmGtkeDMT0rqRUBBMAY242ZPnNp5MrXKd4/mJZql1rARdT
l/fdHX4/i/sts5zvd14xa277MbwFbqAAO9kT7HDahojf3FZGEY8OIoFDCdZ+jkdb
zU5YWjtlFqFGbSgJyhSn2zMoIFjkYn3W62ecGAZxtJgbxaHpmpnejuTYvEyTqRPl
JvSLFKHt9uFw/VROamLG2euG8MvR0o8jySlUWMtj5ro/60sRD6hQ3qq3Uyu+9prW
c+NO560QhcbR9ddtoPuM3H3B/Gj4g8L6YU9oOBzK0euWhgdXbDI8pQuO/4vZqJK1
8JTxI5jFwWvqOqs/C2TzlxSVsSK3kD48x/jj/KbatKstmS8aMOuX7iHuazCBx/LY
YSPg7ZWRoWheYqRw+IJY79kCIkVxMfvI4NeD1aoLjkUG2xpP51S9OCcc2k7CTDfh
eEqo+RK/jD9b8sjNyFmXdEiSqCof3PUyrRmv8G54CHOC9mTkkv0juXaWEA208+jx
Ae4pIQ/1u4ndTzpo+rUP/anSYK6opZG137eUs2FmkpoDkPZF2g9ZgOVJAfB5zm+s
omdGHk1bvi9aqCdRbQWU3wc/0HN49QJPWDTn7gTTpRX2vqvesHocatKixX/AIN4n
y/p/o62xhg5525HNiK5dyBktJjnEpxA8l0WDx4JtRKyzu6udoA8=
=3OP2
-----END PGP SIGNATURE-----

Marek Marczykowski-Górecki

unread,

Apr 20, 2022, 9:46:13 AM4/20/22

to Rusty Bird, qubes...@googlegroups.com

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Yes, a month later, and it's not very optimistic one:

It appears that these issues are currently hidden for reasons relating
to the accounts that opened them.

I'm unable to provide any further information about this for privacy and
security reasons however if the account holders reach out to us we may
be able to assist them directly.

Unfortunately we're unable to re-show these issues until such times as
we can work with those account holders.

Sorry it's perhaps not the news you were hoping for but please let me
know if you have any other questions.

> I just read something disturbing that might be relevant:
>
> | Apparently, “suspending an account” on GitHub actually means *deleting
> | all activity for a user* — which results in (1) every pull request
> | from the suspended account being *deleted*, (2) every issue opened by
> | the suspended account being *deleted*, (3) every comment or discussion
> | from the suspended account being *deleted*. In effect, the user’s
> | entire activity and history is evaporated.
>
> | All of a sudden, I was seeing pull requests, issues, and comments
> | disappear from users who were actively contributing to the project.
> | *We lost valuable contributions, information, context, and discussion
> | history* on issues and pull requests. We even lost pull requests that
> | were open and under active review. That work is now entirely lost.
> | Gone forever. For pull requests that _did_ merge, we have the raw
> | commit history — but that is not a substitute for a full code review
> | and discussion.
>
> https://www.jessesquires.com/blog/2022/04/19/github-suspending-russian-accounts/

Indeed, we've seen this happening. But also, we've seen comments
associated to ghost user when original author's account is no longer
accessible. I'm not sure how the method of suspending an account is
chosen.

Technically, the historical aspect of it isn't huge issue for us, as we
try to not trust github too much (which includes having enough context
in commit messages, having backups of issues, having notification email
history etc). And honestly, I find searching through email notifications
way more reliable than github's built in search. But that's still
inconvenience, especially for current ongoing work.

PS I have used gitlab.com recently in another project, for about 2
years. The project was _much_ smaller, in terms of number of issues,
repositories count, contributions count, length of discussions and
pretty much any other metric. And the subjective feeling was: gitlab is
incredibly slower than github and much less stable. There weren't a week
without "oh no, I need to type this long comment again, because
something went wrong and it wasn't saved", or "something didn't load,
try refresh few times until all the content loads". Since I (try to) not
trust web services for keeping code reviews, I have them always written
in a file first, so when this happens for a review comment, I just need
to paste it again. But that's still inconvenient.
So, while gitlab.com is an alternative, using it will cost us a lot of
frustration... I guess self-hosted instance won't be much better, but it
will require noticeable effort to maintain it (gitlab server
specifically has quite complex environment with several services
involved).

- --
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEEhrpukzGPukRmQqkK24/THMrX1ywFAmJgDp0ACgkQ24/THMrX
1yzCxAf/SeByCfn0CBzac6rmlIXyvZGTcF2oClKEF2C94U0ip9I8tHZJZaaiblBF
y2L+Vh7lziga+jHdT9nhIRwYpUDyVFgH92lDlV2rFZA7K1WhWV61IuSKEK5ug9lC
uU0D5Oa4+lkjKESCgQ/GLCtTpjCB6+OIhlJqn4R9nunxuN6llBTmJFw/kclW9mZ5
/2XjUSz+m5EKx6eVWS9d8FJgP7sNTdeWVGhoVp3rd3ML/4JIpbNg4ynW7Vu1xXJJ
YtG7rshsuJhxEG3KCe8n7bjSc6bKc80mefiDlw6KxXyLFQbjGd0cBwx8QY0BjGDz
4q4TlkDEEXMfYzXmPPLU7Q9Yf0NnLQ==
=YgfV
-----END PGP SIGNATURE-----

Rusty Bird

unread,

Apr 20, 2022, 11:51:20 AM4/20/22

to Marek Marczykowski-Górecki, qubes...@googlegroups.com

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Marek Marczykowski-Górecki:

> On Wed, Apr 20, 2022 at 12:32:56PM +0000, Rusty Bird wrote:
> > Did you ever hear back from them?
>
> Yes, a month later, and it's not very optimistic one:

> I'm unable to provide any further information about this for privacy and

> security reasons [...]

Classic

> Technically, the historical aspect of it isn't huge issue for us, as we
> try to not trust github too much (which includes having enough context
> in commit messages, having backups of issues, having notification email
> history etc). And honestly, I find searching through email notifications
> way more reliable than github's built in search.

Email notifications include the comment ID:

| Message-ID: <QubesOS/qubes-issues/issues/7359/10866...@github.com>
| [...]
| Reply to this email directly or view it on GitHub:
| https://github.com/QubesOS/qubes-issues/issues/7359#issuecomment-1086681239

Maybe GitHub's GraphQL could be queried to list all comment IDs etc.
for comparison - and to monitor if things are getting worse.

> PS I have used gitlab.com recently in another project, for about 2
> years. The project was _much_ smaller, in terms of number of issues,
> repositories count, contributions count, length of discussions and
> pretty much any other metric. And the subjective feeling was: gitlab is
> incredibly slower than github and much less stable.

Also: gitlab.com often blocks me (or probably Tor users in general)
from even seeing CI results unless I log in, boooooo

Rusty
-----BEGIN PGP SIGNATURE-----

iQKTBAEBCgB9FiEEhLWbz8YrEp/hsG0ERp149HqvKt8FAmJgKttfFIAAAAAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDg0
QjU5QkNGQzYyQjEyOUZFMUIwNkQwNDQ2OUQ3OEY0N0FBRjJBREYACgkQRp149Hqv
Kt/NCg//V2/jxthTm6pGlddelA6THfA31xPSvb6aIzrRGk6NVq6avAo2d5J55e0n
5eMUnxxJ44yRk0C6jgzlyUw//Ag4BMreggbe23QoQx4Z+AW/xKBL9FZnnE+jvRB+
i+oJ4Hpv49KGm+5X3FvwwrXYAo603lS0GYDpgUbqCJm9jkju2R1HGum42kiTs2b5
qODphhGEKmC1aaljmdEW2y4ptbLdo/zNnZX+OKXjwS0vtPAg8DDx6NzOxvhnZl8q
8xw9ns0jW0a77qOHqDbn6T5kyawV9KDbck3IBLO+bQeiOU6wQ1OlosYFEnn1w7BH
OdPp1EuFQr2dfAJzknh6MLULUSciovHKgABQ+KovCv/sLgP84Wci5dR6HAZJLhip
1c3RZdLE/2prgPEnDohp4aJ+IozAiXYJhhT44WFn/es/vI2ddnqoo/nE3v0sCokc
Ukuvn3pyj0iXqCiZxmawGJkJ661DIYmSBIs6o/JZHTl2GGx/SG/2TEgRcqMnMP0n
S6vOMSYmH8bmkkiAimmvXa8hQGDP49uwGexeoHU9VAvRGUfqnxxp/OvId1XpDuuJ
DnkcxPvdha3kRGRRAz62x0G0aPKU6LexX1PU6kz15qgFJppiHDOlGikiadfWJSe5
4dFWAR+RDWfiEmAZ3w1+vJimiMcLLOfIftO8cPjchy8/lewG56A=
=lyS3
-----END PGP SIGNATURE-----

Jinoh Kang

unread,

Apr 20, 2022, 12:01:52 PM4/20/22

to Marek Marczykowski-Górecki, Rusty Bird, qubes...@googlegroups.com

Among the disappeared ones is the PCIe hotplug issue I reported.
I don't remember the exact issue ID, though.
Also, I never recall hearing anything from GitHub, let alone being banned.

FYI: https://github.com/QubesOS/qubes-issues/issues/6620#issuecomment-850410223.

>
> I'm unable to provide any further information about this for privacy and
> security reasons however if the account holders reach out to us we may
> be able to assist them directly.

Would I be able to reach them even if I don't have the issue ID?

>
> Unfortunately we're unable to re-show these issues until such times as
> we can work with those account holders.
>
> Sorry it's perhaps not the news you were hoping for but please let me
> know if you have any other questions.

--
Sincerely,
Jinoh Kang

OpenPGP_0x4319538160EBD2E6.asc

OpenPGP_signature

Demi Marie Obenour

unread,

Apr 20, 2022, 7:26:31 PM4/20/22

to Marek Marczykowski-Górecki, Rusty Bird, Frédéric Pierret, qubes...@googlegroups.com

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

My response would be something like, “Would it be possible to show
comments not made by the account that opened the issue?”.

Indeed it is, and a good reason to consider a different platform, such
as GitLab or other self-hosted services.

> PS I have used gitlab.com recently in another project, for about 2
> years. The project was _much_ smaller, in terms of number of issues,
> repositories count, contributions count, length of discussions and
> pretty much any other metric. And the subjective feeling was: gitlab is
> incredibly slower than github and much less stable. There weren't a week
> without "oh no, I need to type this long comment again, because
> something went wrong and it wasn't saved", or "something didn't load,
> try refresh few times until all the content loads". Since I (try to) not
> trust web services for keeping code reviews, I have them always written
> in a file first, so when this happens for a review comment, I just need
> to paste it again. But that's still inconvenient.
> So, while gitlab.com is an alternative, using it will cost us a lot of
> frustration... I guess self-hosted instance won't be much better, but it
> will require noticeable effort to maintain it (gitlab server
> specifically has quite complex environment with several services
> involved).

Frédéric Pierret is already maintaining a GitLab instance, so I don’t
think it would be too difficult for us to host one.

- --
Sincerely,
Demi Marie Obenour (she/her/hers)

Invisible Things Lab
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEdodNnxM2uiJZBxxxsoi1X/+cIsEFAmJglp8ACgkQsoi1X/+c
IsHzyBAAknQGSfc7M2NgoAvFvRry2m+qkxVxG9Kyp41wPNzKVwJrUjMSl2xwwv25
vqK92r3pNtr9DexsLsfKmKug7moSKgoj2HruuDv9RCaV+xdd+fhHj+ZP40pMYr9T
CNQ3YU3aYbTiYxoo42K2DRgVAbMud3pY/U/g0VUQkhzCgd0/CetewunSjdGbPgV5
07KRcyZQCDWR/4Y9RTKx9RKO3G/oaVBHIXijwv6GFBroGP9ukvpPVCBp27/kixeg
H9yvebYZXbpKLFrlrczKLKH0JYK8UK/UoJlOG2B9He+8H61EOI11XOWTySX6+/BS
Qcuatz1pA4hw/5QOJTjYq8A9rOiYs1lTZy47Q5Jgw6frK/iT6EEBvDdn8BDdVA35
V7dE54DWwakGePNwPnvvRd9I8FnXbPMcD1JkekuME6qFvQBWnIrC9KWOfynkU/rE
QFGFqhzTdk1NrXGcR+/A99gJQfMYCxPgaUHzsUsErjLVOrMP+hmBU3z6wW4vg8o8
0/9QzaMQVTn+p3l0X3R3kQPF/is2RE1SG5/ZbNJf6d/432WwYTWgve+oGBZ0z3s/
XzX7duoewO7e5Mi0cGuXse7Bh11RXt6lrEj1FKXooDowt0Ap6X3PStvTNQaxFK3C
Q1hOSwhZQrsFjC0MlnAbQ1v8cPncbHniumGcIS/8BXjv1kf9V2k=
=yx5i
-----END PGP SIGNATURE-----

Demi Marie Obenour

unread,

Apr 20, 2022, 7:34:43 PM4/20/22

to Rusty Bird, Marek Marczykowski-Górecki, Qubes OS Development Mailing List

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On Wed, Apr 20, 2022 at 03:46:35PM +0000, Rusty Bird wrote:
> Marek Marczykowski-Górecki:
> > On Wed, Apr 20, 2022 at 12:32:56PM +0000, Rusty Bird wrote:
> > > Did you ever hear back from them?
> >
> > Yes, a month later, and it's not very optimistic one:
>
> > I'm unable to provide any further information about this for privacy and
> > security reasons [...]
>
> Classic
>
> > Technically, the historical aspect of it isn't huge issue for us, as we
> > try to not trust github too much (which includes having enough context
> > in commit messages, having backups of issues, having notification email
> > history etc). And honestly, I find searching through email notifications
> > way more reliable than github's built in search.
>
> Email notifications include the comment ID:
>
> | Message-ID: <QubesOS/qubes-issues/issues/7359/10866...@github.com>
> | [...]
> | Reply to this email directly or view it on GitHub:
> | https://github.com/QubesOS/qubes-issues/issues/7359#issuecomment-1086681239
>
> Maybe GitHub's GraphQL could be queried to list all comment IDs etc.
> for comparison - and to monitor if things are getting worse.

That is a good idea.

> > PS I have used gitlab.com recently in another project, for about 2
> > years. The project was _much_ smaller, in terms of number of issues,
> > repositories count, contributions count, length of discussions and
> > pretty much any other metric. And the subjective feeling was: gitlab is
> > incredibly slower than github and much less stable.
>
> Also: gitlab.com often blocks me (or probably Tor users in general)
> from even seeing CI results unless I log in, boooooo

I suggest submitting a ticket about this. I would not be surprised if
it is to prevent DDoS attacks.

- --
Sincerely,
Demi Marie Obenour (she/her/hers)

Invisible Things Lab
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEdodNnxM2uiJZBxxxsoi1X/+cIsEFAmJgmIsACgkQsoi1X/+c
IsEo6hAAixpd+oj+LB0chfyj67qjfnxlf6rsWVpPEqiIOVzPtmfW9xZrs/ILXZAJ
dx0xxcY59dfZDPYd3mAU0drX7OGF+VyW7gKlGto6lnQWS0jBMoGNw1Hydxjsdz1n
v8gOuPJxrhdvl1t69xgBD/YA0kIA66sH0niRtVWQ7XL8Mnd5IDXUg1hiqummLy42
k48FBD2icNnaqGKAcxgSz3RPXXmIWQryQQjFj6Zgw2N2dRXih1pmp3dHJnHef+oP
9jAkQGGC9sB0ng+oLuCFzn13frxl3/xMLLN2GESI8xky7KwuJCG0MJsfx1YfYiQl
InUrn5RecNocRZDq0VEa6MeabDqYEXgqXMRd0FGBWKZYX5wQ1ACT2WiFm0d2XeXY
I++qB40a8KSI75uJIPQv9DVAcHCyRYbVVfrnZdK10wskc3DzflZLsWUBu+IU3HnL
9lb9aTVBX/0iAXUQzkzibxiI580E4sGK8dUIN9+Tne7y8aHiHs6TbLCz8fQupE44
hIHJcsMhMRcY7iIPCtoppbJg49T+tZ1va8KzEQ3gJkaMe2hH4/F87WhGZFu8Wlnm
UTapu+k/yVf+aww33JHT8Mm74OF62w8Rtlvsw4YcImotX6tFb9SJnobnHVhTWEJc
3CkCh2iNEEerShK48LOPY03rermE15MaWu0qkpguZYGF/wu4XME=
=mliS
-----END PGP SIGNATURE-----

Reply all

Reply to author

Forward