ksarw
Joined 5 years ago
Joined 5 years ago
I did make the mistake though of clicking "+ expand source", and after seeing the (remarkable) abomination I can sympathize with ChatGPT's "SQL is not suitable for implementing large language model..." :)
I think given the cost advantage for s3 for storage, it seems almost better to pull from R2 into s3 for long-term storage (some inverse slurper).
It's good to hear though that R2 can singlehandedly match s3+cloudfront; that being said, video delivery is a bit different I'd imagine, even s3+cloudfront is finnicky with range requests etc.
https://community.cloudflare.com/t/can-we-serve-video-with-r...
Please correct me if I am mistaken; also R2 is not a CDN, and more like s3 in terms of delivering from the edge
No issue with your comment specifically, just wondering if you know. currently using s3+cloudfront for mp4 storage+delivery, and would like to move to something better if possible.
There are a couple different clients for it on GitHub
I agree with you on that, as well as taking an ML approach. Querying the hooks and symbols directly can lead to the false positive vs spam tradeoff that TheDong is referring to elsewhere in this comment section (to be fair, so can the ML approach but its more avoidable). It is possible that the scale of it makes the minor shortcomings not so minor.
I'm also generally interested in the comment moderation problem myself, and have been working on it myself for some time. I guess my judgement is clouded by my hope that there is a reasonable excuse for the team(s) at Google to not have solved it by now.
Perhaps it is naive of me to think this way; if it really is as simple as "this does not affect advertising revenue" then that would be quite nearsighted of Google. And, as I mentioned earlier, I am of the opinion that quality comment sections would increase engagement (and revenue as a result), so it doesn't make sense to me.
So assuming they care, I can think of two main reasons as to why it is not solved yet, both related to scale as Marques mentioned:
1.) Scale of the problem - It might be that they are already catching 99% of the stuff and we just see what falls through the cracks
2.) Scale of the solving - It could be that the teams and infrastructure are so large that they can't make the rapid adjustments needed compete in such an arms race
On a separate note, I imagine a higher quality comment section would increase engagement more than any "appealing" scam.
On a side note, I am pleased though that you find him entertaining to watch regardless. I find it disappointing when people take speakers like Zizek too seriously; I think even if 80% of what is said is not insightful/intelligible, the occasional grain of truth can be very much worth it.
We're committed to maintaining civil discussion, and you can get a sense of what we're on watch for by checking out our content policy: https://www.netvyne.com/content-policy
The platform has no favorites, which you'll see for yourself in time.
I do think Netvyne addresses the need to interact with others on a website as mentioned. In fact, this particular need-gap was something we've thought about, and we do already have a live chat section built into the extension itself in order to address it.
Thanks for the invitation, I'll go a head and post a comment there!
There's also an automated component that will be scaled up as time goes on; while moderation will not be fully automated in the near future, the realistic target is for a AI-assisted system that will greatly increase not only throughput but consistency/correctness as well.
There is a lot of uncertainty here that we'll have to manage moving forward. My background is in deep learning (mostly CV), and there are some parallels between these challenges. Because of this, I do believe these problems can be solved over time.
Curating civil discussion is our goal. Personally, I found the quote on dang's profile quite beautiful in putting into words a noble target that we ourselves will be working towards with our content moderation.
Email: khalil@<insert above domain>
Hello!
Be the change :)