Quick question to the admins: Which PHP package do you use to talk to the database? Means: Do you use php-pdo? There is currently a pull request that would lay ground for eventually adding PostgreSQL support somewhere in the future. And I suggest that we then possibly support only PDO for both PostgreSQL and MariaDB, since this would simplify stuff a lot.
@apps@marek@marek What about nested replies? Means: When A is a comment to B, which is a comment do C, which commented on D? Should then the object of post A not only contain the post B, but inside the post B there is post C, which also contains post D? This can quickly decrease the performance a lot.
As you might have heard, there are issues with the Twitter API. Several favourite clients stopped working, while others (still) do. By now there hadn't been any word if there is some massive Problem or if this was some deliberate action.
Whatever is causing these issues, at least my connection still works. How about yours? Is the Twitter connector on your systems still running?
@andy@hankg "regularly" is fetching really often, means every few minutes. That's why I recommend to set 'adjust_poll_frequency' => true, in your local.config.php and also to set 'min_poll_interval' => 5, to a minimal poll interval that you feel safe about (like the 5 minutes in the example)
@hypolite I also want to refer to the recurrent laryngeal nerve, that is often cited as evidence of evolution, since it doesn't make sense to route a nerve nearly 5 meters through the body of a giraffe instead of taking the direct path of some centimeters: en.wikipedia.org/wiki/Recurren…
@hypolite From a database perspective it is really bad practice to store data that is already stored. In this case it is especially bad since there are depending tables (like the one with the reported posts) that with each update is deleted and inserted over and over again.
Also when this technique was applied to some other places that have got a higher risk of race conditions we run into nightmare situations where some fields had been reverted to older situations because there had been some other (parallel) task between setting the class variables and saving all the fields. Let's say we had a situation where the one process set the avatar of a contact and a parallel process is setting the date of the last item. With the right (or better: bad) timing, the avatar or the date of last item was reverted when we worked that way.
I do get your point of input validation. But that solution opens up a bunch of other problems that are even worse than the original problem.
Entwickelt Open Source in der Freizeit, hat zu viele Fahrräder und ist Fan des HSVH (Das erste "H" steht für "Handball") und von islieb, Franzbrötchen und guter Schokolade. Wunschliste: alles unter https://www.rausch.de/schokolade/Wer Amazon mag: https://www.amazon.de/hz/wishlist/ls/3VWK0ZL3MN3ZTLiberapay: https://liberapay.com/heluecht/donateBTC: 1AtJ9JVysdhWjSs5qQvp7Xt9xFdjMKSSA7BCH: qpjg2gwgr35fgz3dxy6lcpw3lt4szrfgev90uk3tfv