pull down to refresh
If this is the item you fat fingered, it was caused by a bug that was since fixed.
And thanks for the advice! I think you’re right about letting it ride
A conman enters your peaceful village, he cons you and many people you know. Your village has no formal judicial system, so how do you prevent the conman from conning everyone?
Our prior ranking system would remember conmen and communicate it. Our current system has no such mechanism.
Yes. If they consistently produced outlawed content, they would become an outlaw, and new comments and posts would start out as outlawed.
hmmmm we need a new solution for these LLM catfishers. Before the ranking changes someone producing lots of outlawed content made themselves a bit of a gravity well. There's no easy way to port that to the new system.
Hablamos de esto en nuestra reunión de ayer.
Tenemos una idea para resolverlo, pero primero debemos probarla.
We discussed this in our meeting yesterday.
We have an idea for solving it but need to test it first.
https://shopstr.store/ maybe?
I love information trees so I think the goal is worthy.
afaict the main issue is that in an environment where finding a single note is not guaranteed, finding note that depends on other notes that depends on other notes and so on is going to provide even worse guarantees.
I didn't want to confuse the post much but, from the graphic, it's shocking how blunted serum melatonin is in both autism and schizophrenia relative to controls.
BTW is there a bug in the SN keyboard because if I make a spelling mistake, I can't delete it, it just keeps running through the suggested words
If you're on Android @sox is working on a fix.
I've always though that philosophically what should be aimed for is the most coherent and easily expressible data model that minimizes redunancy, but with a syntax and subroutine library that allows for quick retrieval of even highly nested relational structures.
That is the aim. We call this database normalization. It's the right way to design these systems. In practice, you often denormalize data for performance reasons because there are limits to how fast a computer can access and process data especially when it is spread around.
When you're joining tables, which are each a collection of files on your harddrive, you are randomly accessing another collection of files for each join. Indices can help the database know exactly which file it needs to read to get a particular row, but any file read is slower than none.
I try to keep our data "normal," so we always know what is "true," whether I end up also denormalizing the data or not.
I think the SQL standard should evolve to address polymorphism like this directly though. It's incredibly common and has no direct solution afaict.
I'm chopping up some LED strips for my office and I bought a 12V power supply when I need a 24V. Much sad.
Seriously I'm not sure. It sounds like doing it right requires a lot of maintenance.
I just wanted a cool fish that I can nod to when I get into work or imagine is cheering me on when I'm troubleshooting a bug.
Can these be chained? If so, won't I have to wait for all the hedgehogs on a route to come online?