February 15, 2022 at 3:49 pm
duplicate
Aus dem Paradies, das Cantor uns geschaffen, soll uns niemand vertreiben können
February 15, 2022 at 3:50 pm
So a lot of folks have written articles where no one has posted to the discussions in well over a year. If someone reads and article and has a question about the article for clarification or whatever, why shouldn't they be able to add a new post the the discussion thread for the article and have folks be notified? Isn't that a part of the purpose here?
Here's a specific example where I revived a thread from 2015 with a question. Ha, it caught Jeff before he had his coffee too. What would've happened if the thread was closed? Honestly I would've created a new thread and linked it to the old one
Aus dem Paradies, das Cantor uns geschaffen, soll uns niemand vertreiben können
February 15, 2022 at 4:41 pm
Keeping open article discussions is a good idea. My initial thought is that we exempt them from closing.
February 15, 2022 at 10:18 pm
It happened to be an article (which I vote yes also to keeping open) but idk it could've been a regular forum post. Those come up in searches. A new thread with a link to the old doesn't seem as simple as just one thread. What if this rule was applied backwards, how many threads would be broken?
Aus dem Paradies, das Cantor uns geschaffen, soll uns niemand vertreiben können
February 16, 2022 at 3:22 pm
Asked the question as part of the triage and planning for this work about how many threads might be affected, or might be exceptions.
February 16, 2022 at 5:05 pm
Asked the question as part of the triage and planning for this work about how many threads might be affected, or might be exceptions.
Perhaps you should read the article here before insisting on such changes. In particular, read the part that says, and I quote...
The last line from the article:
"Write better code and you might be surprised just how scalable your system proves itself to be."
--Jeff Moden
Change is inevitable... Change for the better is not.
February 16, 2022 at 7:33 pm
We haven't had scale issues. You're conflating changes with bugs or errors.
And, yes, I do push the staff to write better code and be accountable for their mistakes.
February 17, 2022 at 5:03 am
If you've not had scale issues, then why all the business about limiting notations and shutting down notifications on old posts?
--Jeff Moden
Change is inevitable... Change for the better is not.
February 17, 2022 at 3:38 pm
If you've not had scale issues, then why all the business about limiting notations and shutting down notifications on old posts?
Perhaps a verbiage issue. Scale, to me, is concurrent users and handling a load there. We've not had that.
We have had a session overload with the processing of the notifications. Given the data model, which is poor in WP and isn't designed well for large filtering, the subscriptions were an issue. That is somewhat scale, but it isn't about writing better code, at least not within the design of the WP data model. It's about reducing the load, or about redesigning how the notification system works. In that case, we would be forking the forum code, which makes upgrades an issue.
We could submit a PR to the software developer, but since an improvement to handle a much larger level of notifications would be a data model change, moving away from how WP architects things, philosophically, I doubt it would be accepted.
As it is, my push is to abandon the WP model in places where we are building our own software in the name of being more efficient with computing resources and working with larger scales of things, but that's few places. Most of the time you are building something that you expect to work with singletons, or a session, in which case the silly JSON-stuff-many-things-into-a-field model works well.
It's a No-SQL/document DB kind of model for WP, which is highly scalable (concurrently) for singletons, less efficient for space usage, poor for data dupe and multi-row operations, but well understood by a class of developers working in that architecture.
February 17, 2022 at 4:04 pm
Thanks for the explanation, Steve. I appreciate it.
But, aren't notifications working "just fine now"?
--Jeff Moden
Change is inevitable... Change for the better is not.
February 22, 2022 at 2:08 pm
This person is in way over their head.
https://www.sqlservercentral.com/forums/user/bruin
Michael L John
If you assassinate a DBA, would you pull a trigger?
To properly post on a forum:
http://www.sqlservercentral.com/articles/61537/
February 22, 2022 at 4:37 pm
This person is in way over their head.
one of those I refuse to help now - ignores suggestions and fails to supply requested information and just wishes for us to do their work for them (for free)
February 22, 2022 at 6:13 pm
Michael L John wrote:This person is in way over their head.
one of those I refuse to help now - ignores suggestions and fails to supply requested information and just wishes for us to do their work for them (for free)
Michael L John wrote:This person is in way over their head.
one of those I refuse to help now - ignores suggestions and fails to supply requested information and just wishes for us to do their work for them (for free)
Just hinted that there might be time to call in an expert.
😎
February 22, 2022 at 6:40 pm
frederico_fonseca wrote:Michael L John wrote:This person is in way over their head.
one of those I refuse to help now - ignores suggestions and fails to supply requested information and just wishes for us to do their work for them (for free)
frederico_fonseca wrote:Michael L John wrote:This person is in way over their head.
one of those I refuse to help now - ignores suggestions and fails to supply requested information and just wishes for us to do their work for them (for free)
Just hinted that there might be time to call in an expert. 😎
I'm not sure they are even capable of understanding what to ask, and worse, what to provide. Their posts have bounced all over the place. I'm betting they are a network admin (or something) that was either thrown into something, or worse, sees a perceived issue.
I think that there is a large language barrier also.
Michael L John
If you assassinate a DBA, would you pull a trigger?
To properly post on a forum:
http://www.sqlservercentral.com/articles/61537/
February 22, 2022 at 7:37 pm
Eirikur Eiriksson wrote:frederico_fonseca wrote:Michael L John wrote:This person is in way over their head.
one of those I refuse to help now - ignores suggestions and fails to supply requested information and just wishes for us to do their work for them (for free)
frederico_fonseca wrote:Michael L John wrote:This person is in way over their head.
one of those I refuse to help now - ignores suggestions and fails to supply requested information and just wishes for us to do their work for them (for free)
Just hinted that there might be time to call in an expert. 😎
I'm not sure they are even capable of understanding what to ask, and worse, what to provide. Their posts have bounced all over the place. I'm betting they are a network admin (or something) that was either thrown into something, or worse, sees a perceived issue.
I think that there is a large language barrier also.
I agree on the observation of language barriers, both human and programming languages
😎
Viewing 15 posts - 65,881 through 65,895 (of 66,712 total)
You must be logged in to reply to this topic. Login to reply