undefined | Better HN

0 pointsh_anna_h5y ago0 comments

I do not see any evidence of this in said quote.

0 comments

7 comments · 2 top-level

ryanlol5y ago· 3 in thread

>2021-02-06 12:00 @DuckSoft sended a pull request that adds the PoC to Signal TLS proxy's repository.

This is inappropriate. Pulling in a random PoC to the repo is not how you’re supposed to use PRs. Issues exist for this purpose, but theirs had already been removed.

>It has since been deleted [...] A repost by @U-v-U was later closed and locked.

Reposting the inappropriate PR is also inappropriate.

h_anna_hOP5y ago

I do not find either of these to be inappropriate.

proactivesvcs5y ago

They are, along with all of the misbehaviour this group is perpetrating. Acting in this way well result in nothing but derision and bans from any organisation (and prospective employer, for that matter) because it is childish and unproductive.

ryanlol5y ago

How is reposting content that was previously removed by maintainers not inappropriate? Signal made it very clear that this stuff should be posted on their community forums, not github.

FDSGSG5y ago· 2 in thread

You don't see why making such a pull request would be inappropriate? Do you understand what pull requests are for?

Does this look like an attempt at productive contribution to you? https://github.com/signalapp/Signal-TLS-Proxy/pull/15

Is this a good patch? It just drops a random file into the repo. https://github.com/signalapp/Signal-TLS-Proxy/commit/40f4d9d...

These people decided to abuse the pull request system after being asked to use https://community.signalusers.org/ instead of GH issues to discuss their concerns.

h_anna_hOP5y ago

This has nothing to do with my post.

FDSGSG5y ago

Of course it does, unless you were replying to the wrong comment in the first place.

What was it you did not see any evidence of?

1 more reply

j / k navigate · click thread line to collapse

0 comments

7 comments · 2 top-level

ryanlol5y ago· 3 in thread

>2021-02-06 12:00 @DuckSoft sended a pull request that adds the PoC to Signal TLS proxy's repository.

This is inappropriate. Pulling in a random PoC to the repo is not how you’re supposed to use PRs. Issues exist for this purpose, but theirs had already been removed.

>It has since been deleted [...] A repost by @U-v-U was later closed and locked.

Reposting the inappropriate PR is also inappropriate.

h_anna_hOP5y ago

I do not find either of these to be inappropriate.

proactivesvcs5y ago

They are, along with all of the misbehaviour this group is perpetrating. Acting in this way well result in nothing but derision and bans from any organisation (and prospective employer, for that matter) because it is childish and unproductive.

ryanlol5y ago

How is reposting content that was previously removed by maintainers not inappropriate? Signal made it very clear that this stuff should be posted on their community forums, not github.

FDSGSG5y ago· 2 in thread

You don't see why making such a pull request would be inappropriate? Do you understand what pull requests are for?

Does this look like an attempt at productive contribution to you? https://github.com/signalapp/Signal-TLS-Proxy/pull/15

Is this a good patch? It just drops a random file into the repo. https://github.com/signalapp/Signal-TLS-Proxy/commit/40f4d9d...

These people decided to abuse the pull request system after being asked to use https://community.signalusers.org/ instead of GH issues to discuss their concerns.

h_anna_hOP5y ago

This has nothing to do with my post.

FDSGSG5y ago

Of course it does, unless you were replying to the wrong comment in the first place.

What was it you did not see any evidence of?

1 more reply

j / k navigate · click thread line to collapse