Okak, so, here's what I think:
The problem with GG is with how they've defined their SLOs - the 'happy
user experience'. They think that being able to post 1000s of times an
hour to a discussion formum is a good thing: it only matters that
nothing fails to post - because that would be a negative user
experience. If that happens then it'd automatically scale up (but, >1000s/hour is nothing to GG - they could scale up; the reality is that
they don't need to).
Even if they did need to scale up, no alert will be generated, becuase
that would be an interruption, and they've engineered that away, becuase >dealing with tickets is a waste of an engineers time. There will be no >dashboard at GG that has gone amber, let alone red. It's all green and
happy at GG.
So, fundamentally: The issue is that being able to post 1000s of
times/hour to a forum, be it usenet or an GG 'group', is not a good
thing at all: no discussion/debate can possibly happen that fast. So,
their SLO is fundamentally wrong.
Not that that helps at all. It just explains why GG has done, and will
do, nothing about it.
Okak, so, here's what I think:
The problem with GG is with how they've defined their SLOs - the 'happy
user experience'. They think that being able to post 1000s of times an
hour to a discussion formum is a good thing: it only matters that
nothing fails to post - because that would be a negative user
experience. If that happens then it'd automatically scale up (but, >1000s/hour is nothing to GG - they could scale up; the reality is that
they don't need to).
Even if they did need to scale up, no alert will be generated, becuase
that would be an interruption, and they've engineered that away, becuase >dealing with tickets is a waste of an engineers time. There will be no >dashboard at GG that has gone amber, let alone red. It's all green and
happy at GG.
So, fundamentally: The issue is that being able to post 1000s of
times/hour to a forum, be it usenet or an GG 'group', is not a good
thing at all: no discussion/debate can possibly happen that fast. So,
their SLO is fundamentally wrong.
Not that that helps at all. It just explains why GG has done, and will
do, nothing about it.
So, fundamentally: The issue is that being able to post 1000s of
times/hour to a forum, be it usenet or an GG 'group', is not a good
thing at all: no discussion/debate can possibly happen that fast. So,
their SLO is fundamentally wrong.
Not that that helps at all. It just explains why GG has done, and will
do, nothing about it.
There's no way a news client would refresh fast enough to sustain that.
On 10/22/23 12:49, Richard Harnden wrote:
So, fundamentally: The issue is that being able to post 1000s of
times/hour to a forum, be it usenet or an GG 'group', is not a good
thing at all: no discussion/debate can possibly happen that fast. So,
their SLO is fundamentally wrong.
Not that that helps at all. It just explains why GG has done, and will
do, nothing about it.
There's no way a news client would refresh fast enough to sustain that.
--
user <candycane> is generated from /dev/urandom
Le 23/10/2023 à 14:26, candycanearter07 a écrit :
There's no way a news client would refresh fast enough to sustain that.
There always has been non-Google spammers, with scripts or whatever.
On Mon, 23 Oct 2023 14:04:08 +0000, The Doctor wrote:
Not that that helps at all. It just explains why GG has done, and
will do, nothing about it.
There's no way a news client would refresh fast enough to sustain that.
Exactly why a UDP no GG is being called for!
Blocked google a week or so ago now, our usenet-abuse-desk email has
fallen so silent, I sent a test message last night to make sure it still >worked :)
ahhhhhhhhhh peace and quiet.
Not that that helps at all. It just explains why GG has done, and
will do, nothing about it.
There's no way a news client would refresh fast enough to sustain that.
Exactly why a UDP no GG is being called for!
Not that that helps at all. It just explains why GG has done, and
will do, nothing about it.
There's no way a news client would refresh fast enough to sustain that.
Exactly why a UDP no GG is being called for!
Blocked google a week or so ago now, our usenet-abuse-desk email has
fallen so silent, I sent a test message last night to make sure it still >worked :)
ahhhhhhhhhh peace and quiet.
On 28 Oct 2023 11:48:52 +1000, noel <deletethis@invalid.lan> wrote:
On Mon, 23 Oct 2023 14:04:08 +0000, The Doctor wrote:
Not that that helps at all. It just explains why GG has done, and
will do, nothing about it.
There's no way a news client would refresh fast enough to sustain that.
Exactly why a UDP no GG is being called for!
Blocked google a week or so ago now, our usenet-abuse-desk email has
fallen so silent, I sent a test message last night to make sure it still >>worked :)
ahhhhhhhhhh peace and quiet.
if this keeps up, little old me will have to find some other line of
work, they say basket weaving can be quite relaxing ... or gardening
On 28 Oct 2023 11:48:52 +1000, noel <deletethis@invalid.lan> wrote:
On Mon, 23 Oct 2023 14:04:08 +0000, The Doctor wrote:
Not that that helps at all. It just explains why GG has done, and
will do, nothing about it.
There's no way a news client would refresh fast enough to sustain
that.
Exactly why a UDP no GG is being called for!
Blocked google a week or so ago now, our usenet-abuse-desk email has
fallen so silent, I sent a test message last night to make sure it still >>worked :)
ahhhhhhhhhh peace and quiet.
if this keeps up, little old me will have to find some other line of
work, they say basket weaving can be quite relaxing ... or gardening
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 299 |
| Nodes: | 16 (2 / 14) |
| Uptime: | 59:37:37 |
| Calls: | 6,690 |
| Files: | 12,225 |
| Messages: | 5,345,376 |