1 |
@sprang
github
is
a
step
in
the
right
direction.
But
it
didn't
change
much.
|
1 |
@sprang
github
is
a
step
in
the
right
direction.
But
it
didn't
change
much.
I
don't
think
a
developer
see
kudos
as
a
reward,
but
maybe
we
can
get
players
to
help
with
finding
a
systematic
way
to
reproduce
a
bug,
maybe
that
would
deserve
kudos
|
2 |
\n
|
|
|
3 |
@spring I don't think a developer see kudos as a reward, but maybe we can get players to help with finding a systematic way to reproduce a bug, maybe that would deserve kudos
|
|
|
4 |
\n
|
2 |
\n
|
5 |
@Yogzototh the exact same thing happened to me... it is not an exception, it is the way #zkdev handle security: blame the messenger. That's why things do not change, and ZKLobby can still be used to deploy trojans anywhere and by anyone, server security is abysmal
|
3 |
@Yogzototh the exact same thing happened to me... it is not an exception, it is the way #zkdev handle security: blame the messenger. That's why things do not change, and ZKLobby can still be used to deploy trojans anywhere and by anyone, server security is abysmal
|
6 |
\n
|
4 |
\n
|
7 |
My point is, can we admit that:
|
5 |
My point is, can we admit that:
|
8 |
- code in repository is dangerous
|
6 |
- code in repository is dangerous
|
9 |
- code is partially unmaintained
|
7 |
- code is partially unmaintained
|
10 |
- authors of the code will not fix it, they expect you to fix it
|
8 |
- authors of the code will not fix it, they expect you to fix it
|
11 |
- nobody is fixing the bugs
|
9 |
- nobody is fixing the bugs
|
12 |
- everyone knows the bug is there (devs, users, trolls, attackers)
|
10 |
- everyone knows the bug is there (devs, users, trolls, attackers)
|
13 |
- some ZK guy pushes the deploy button anyway, he does not feel responsible
|
11 |
- some ZK guy pushes the deploy button anyway, he does not feel responsible
|
14 |
\n
|
12 |
\n
|
15 |
Is this an acceptable state for a release ready product?
|
13 |
Is this an acceptable state for a release ready product?
|
16 |
\n
|
14 |
\n
|