1,488 karma · joined October 25, 2012
Also you can search individual videos by showing transcript and pressing ctrl-f
now we are just moving from trusting a bunch of distinct services to trusting this single broker... just moving the responsibility of trust to a single point of potential failure no?
Also dont credentials have to be passed to secretless broker? how does it know the application has access to the service? isnt that still at risk of being leaked.
i like the idea of not thinking about secrets but it seems to good to be true.
There are still things about brave that confuse me... like the browser feature that allows giving crypto to content providers...
but as someone who loathes AMP... I support this feature.
Unrelated: My treadmill has the absolute worst YT client I've ever used.
I've seen plenty programmer's with CS degrees make terribly dumb mistakes, and some self-taught developers are some of the smartest people I've worked with.
There are more javascript developers, because JS is far and away the most popular programming environment due mainly to its ubiquity on the web. Because of that the JS supply-chain is a much larger attack surface than most languages.
I think that a sanction list would make sense, perhaps https://socket.dev/ could use it as a data point for alerts if they are not already
It's almost like AWS before they expanded to having a mind numbing number of service offerings. Who can keep up with all these? Who, other than people training for cloud architect certifications?
I worry that AWS has lost focus on its core services and instead is trying to market every shiny new thing under the sun... I work in finance, my corp is in us-east region. I think we had like 3 AWS related incidents that caused serious production outages last year... All from use of core AWS services. Now we are looking to support cross-region fault tolerance to defend against this. Supporting such a strategy sounds like it's going to be quite expensive, and technically complex.
I'm not sure the issue here, that sigterm is sent before removal from the load balancer? If you handle the sigterm gracefully doesnt this solve your issue...
I'm no k8s expert so maybe I am misunderstanding the problem
I assume the intent is not to store solely a direct hash of the original video, but also the original file which can be fingerprinted, or the fingerprint itself that will be matched if a later duplicate is uploaded.
Fingerprint differing from hashing in that two non-identical, but similar files (e.g. an original video and deepfake) can have the same fingerprint, but differing checksums.
Providing api access to a signed immutable database makes sense... but I'm not sure how much sense utilizing existing popular cryptocurrencies would make (e.g. bitcoin, etherium)