Personally I love this concept! Looks really well done and I would pay for it once in a heartbeat, but the subscription requirement is an immediate deal breaker for me. This looks like a $2.99 - 9.99 one time purchase. I also don't understand the name.
They're public servants. That footage should be public property.
Just like "this call may be monitored for blah blah", your actions as a cop should be monitored by the public.
Maybe we should have local citizens watching/reviewing body cam footage 24/7 to make sure cops are doing their job correctly. It's also job creation.
Edit: obviously there are some confidentiality issues, so only certain folks should have that clearance. But it feels like we need a better oversight system, whatever that may be.
Yeah, some confidentiality issues.. I'm pretty sure such system would be abused. To leak footages of low situation in peoples' lives. To make sure cops enforce rules by the letter even if situation is objectively silly on the spot. To get dirt on cops by logging mistakes which everybody does.
That's like requiring screensharing + camera on for remote workers 100% of the time. It sucks.
It's not about deadly shooting. In my country bigger problem is police being not bold enough. Here police fires once in few years. As a whole force. Yet we have same issues with body cams. People cry foul over whatever policing is going on.
Policing is hard enough job as it is. Make it even harsher by 24/7 monitoring and even fewer people will show up. Then you'll have to scrap the bottom of the barrel to find any officers. Which is not exactly good for the society.
Looking from afar, US policing issues surrounding gun use is just a reflection of the overall society. US as a whole is overall much more aggressive society. Both police and criminals are more aggressive.
I've been following the project for a bit and this is great, I'm really excited for this to get wider adoption. This is gonna save a lot of headaches and put power in the hands of web devs.
I honestly think 90-95% of Frontend Devs are capable of all this. Maybe not 10 years ago when spaghetti code ruled, but if you got your foot in the door as a FE Dev then you have a portfolio containing examples of almost all this 'wildcard' work.
Totally agree. As a Javascript dev I got functional code pushed on me in 2016.
It's definitely good practice for devs to learn some of the pitfalls that FP prevents and solves, but implementing it on a massive scale front-end application just seems impractical.
Having worked on a large streaming service and considering the author's 3 MONTH struggle after his 40 YEARS experience, I'd estimate that a re-write of our codebase there would have taken our 20 devs over a decade.
Functional programming, and it's degenerate cousin, cramming random functional constructs (array comprehension methods, willy-nilly currying, ...) in Javascript has been the worst thing to happen to web programming.
What that has done is made a whole generation of developers completely detached of the impact on heap allocation and GC. If web programs are slow and bloated, it's partly because of using nuggets from functional programming just for the sake of it.
I'm actually all for the FP things that have been added to imperative languages, which increase their power tremendously and make a lot of tasks a helluva lot easier. But like any tool, it has its place. I'd be equally leery of a pure imperative solution as I would be a pure FP solution.
> implementing it on a massive scale front-end application just seems impractical.
I was using Clojure/ClojureScript around the same time. I’ve since worked primarily in TypeScript/JavaScript. I’m sure the FP experience influenced my opinion, but it seems impractical to me not to use FP techniques for a large scale frontend application. The applications I inherited and maintain now, which were certainly not originally implemented with FP techniques, have been gradually becoming much more maintainable as I’m able to eliminate or at least ruthlessly isolate mutations. Not only because the code itself is easier to reason about, but also because it’s easier to reason about dependencies between different parts of the systems—even parts which haven’t changed.
> implementing it on a massive scale front-end application just seems impractical.
That's true if a team was trying to do so from scratch in js or ts. However React borrows a lot from FP and works at scale. A better example would be Elm.
Anything beats the hundreds of incompatible classical inheritance models rammed on top of proptypes.
Today, functional has won so completely that devs don’t even notice. Using classes is almost entirely antipattern. Factories with object literals and Claire’s reign supreme. Everyone prefers map, filter, reduce, etc over manual looping. Const and copying as a default immutability is preferred to mutation. Nobody thinks twice about higher order functions everywhere.
I feel like the rise of channel subscriptions has caused the recommendation algorithm to act like a dog chasing its tail. You get so silo'd with content on youtube reccs these days, it's really sad.
I don't feel these unavoidable disadvantages are as black and white and you describe. To circumvent the fake title/bait & switch practices, you could allow users to flag videos as misleading, vote them as spam, etc. Put the number of flags next to the video, add the ability to not even see flagged videos.
Further, scripts could be used to report video play statistics to the scrape site. Drawback is users would have to add the script to their own site, but adding analytics scripts is common practice.
>To circumvent the fake title/bait & switch practices, you could allow users to flag videos as misleading, vote them as spam, etc.
And now you've re-created the "Amazon 1-star ratings left by competitors instead of real buyers" and/or the "false DMCA takedown claims of public domain or original music".
E.g. an honest person creates a "How to sew a mask at home to protect from COVID" which is the real content but a bunch of coronavirus deniers falsely flag that video as "child pornography".
Game theory is hard and everybody has to think through all the future chess moves that adversaries will use.
> To circumvent the fake title/bait & switch practices, you could allow users to flag videos as misleading, vote them as spam, etc. Put the number of flags next to the video, add the ability to not even see flagged videos.
And who would flag the bad users?
This just increases slightly the discomfort of bad guys, but does not prevent it at all. Instead they will flag competitive videos and such.
Nobody has solved "decentralized trust" yet, if ever.
"if you can't reliably identify all the intervals within an octave and identify major, minor, diminished and augmented triads, as well as the basic 4-note chords (major 7, minor 7, dominant 7, minor-7-flat-5) by ear..."
I feel this is phrased in a very daunting way. Understanding how the different notes sounds is certainly a building block to soloing/improvisation, but you do NOT need a jazz-pro ear to do that. I certainly can't always recognize 4 note chord types, but while playing I can tell when a flat 3rd would sound tasty in lieu of a major 3rd.
A great exercise I used is playing piano in C major and getting used to using the black keys, which will all be sharp or flat notes in that key. Get used to how a flat 3rd sounds compared to a major, the same with flat 7ths, sharp 5ths, etc...learn how to add those notes in ways that work.
I improved a LOT from a VERY short course by Youtuber Jeff Schneider that teaches this in a structured manner. It's 25 short & tasty blues licks in C major, so every time something 'tasty' is played, it's either a flat/sharp note and/or a fun rhythm, like a triplet. It made so many things click for my lead playing.
I'm in no way affiliated with Jeff but I can't recommend the course enough, best 15$ I've probably ever spent. It's also now been transcribed to all keys, but I think C is probably all you need. https://jeffschneidermusic.com/store/tastiest-blues-licks
