cyberpunk007

joined 1 year ago
[–] [email protected] 18 points 5 months ago

I'm really annoyed how everyone is pushing AI. It's so far not as big a deal as they make it out to be.

[–] [email protected] 10 points 5 months ago
[–] [email protected] 7 points 5 months ago

If years of using a case has taught me, once you get some sand or something in it, it will practically scratch itself.

[–] [email protected] 13 points 5 months ago

$1500? Unlikely. Probably 2,000 or 2,500 💀

[–] [email protected] 0 points 5 months ago (1 children)

Let's pretend it's 50/50 humans drive ng cars and self driving cars. The numbers would be a lot higher. It's not really a fair comparison.

[–] [email protected] 8 points 6 months ago (8 children)

"new" concerns lol. There are so many of these articles with self driving cars crashing.

[–] [email protected] 33 points 6 months ago

But ads do not, so don't worry!

[–] [email protected] 1 points 6 months ago (1 children)

How do you do that? Do you narrow it down to a timeframe?

When a user edits a comment, they submit a response. When they submit a response, they trigger an action. An action can do validation steps and call methods, just like I said above, for example. When the edit action is triggered, check the timestamp against the previously edited comment's timestamp. If the previous - or previous 5 are less than a given timeframe, flag it. "Shadowban" the user. Make it look like they've updated their comments to them, but in reality they're the same.

We've had detection methods for this sort of thing for a long time. Thing about how spam filtering works. If you're using some tool to scramble your data, they likely have patterns. To think reddit doesn't have some means to protect itself against this is naive. It's their whole business. All these user submitted comments are worth money.

Now you need to parse billions upon billions upon billions of records. And yes, it’s billions because you need the system to search through all the records to know which record fits the parameters. And you need to do that across multiple backups for each deleted profile/comment.

This makes me thing you don't understand my meaning. I think you're talking about one day reddit decides to search for an restore obfuscated and deleted comments. Yes, that would be a large undertaking. This is not what I'm suggesting at all. Stop it while it's happening, not later. Patterns and trends can easily identify when a user is doing something like shreddit or the like, then the code can act on it.

It’s a lot of work. And what’s the payoff? A few good comments and a ton of “yes this ^” comments.

this

[–] [email protected] 1 points 6 months ago (3 children)

The words of every junior dev right before I have to spend a weekend undoing their crap.

There are so many ways this can be done that I think you are not thinking of. Say a user goes to "shreddit" (or some other similar app) their comments. They likely have thousands. On every comment edit, it's quite easy to check the last time the users edited one of their comments. All they need is some check like checking if the last 10 consecutive comments were edited in hours or milliseconds/seconds. After that, reddit could easily just tell the user it's editing their comments but it's not. Like a shadowban kind of method. Another way would be at the data structure level. We don't know what their databases and hardware are like, but I can speculate. What if each user edited comment is not an update query on a database, but an add/insert. Then all you need to do is update the live comments where the date is before the malicious date where the username=$username. Not to mention when you start talking Nimble storage and stuff like that, the storage is extremely quick to respond. Hell I would wager it didn't even hit storage yet, probably still on some all flash cache or in memory. Another way could be at the filesystem level. Ever heard of zfs? What if each user had their own dataset or something, it's extremely easy and quick to roll back a snapshot, or to clone the previous snapshot. There are so many ways.

At the end of the day a user is triggering this action, so we don't necessarily need to parse "billions" of records. Just the records for a single user.

[–] [email protected] 7 points 6 months ago

Ah, finally. Now we will stop talking about, hearing about, and shoving "AI" in everything and the next new thing will be "quantum internet enabled" things.

[–] [email protected] 2 points 6 months ago

This is it exactly. Edits to use are "changed". To the back end it's just an iteration while the rest still exist.

[–] [email protected] 1 points 6 months ago (5 children)

It's a piece of cake. Some code along the lines of:

If ($user.modifyCommentRecentlyCount > 50){

Print "user is nuking comments" $comment = $previousComment }

Or some shit. It can be done quite easily, trust me.

view more: ‹ prev next ›