No post body was provided.
TIL: You can access a user’s camera with just HTML
211–220 of 240 posts
Re: TIL: You can access a user’s camera with just HTML
#212Earlier quoted context omitted.
Do you have a link to any of your photographic work?
I'm always too lazy to make an online gallery, and I don't want HN knowing my instagram. But I just made a few snaps of what I had around and put them here. https://golden-taffy-476b64.netlify.app/photos_m/
I really appreciate that you put those up, there's something about the silhouettes of the two figures (2) that I really like.
Re: TIL: You can access a user’s camera with just HTML
#213Earlier quoted context omitted.
I find it incredible that people still think HTML, a spec first published in 1990 when we were using 386s with CGA monitors, shouldn't have evolved to utilise some of the modern features available on today's computers and phones. Why wouldn't we want to be able to do useful things on the web with our devices?
>Why wouldn't we want to be able to [run interactive apps] web with our devices? Because the web is for hypertext, which means static content. Images, text, video and audio clips, tables, code snippets, etc. Of course even that subset it does unimaginably bad, okay? Interactive web apps fucking suck, so that takes care of that 50%. For the other 50%, which is document viewing, why in the hell would I want pages to be…
Because the web is for hypertext, which means static content.
Thats what hypertext meant originally but it's evolved and moved on. The spec is literally called "HTML The Living Standard". You don't get to claim it's fixed and can't change. It just isn't.
Re: TIL: You can access a user’s camera with just HTML
#214We've been using this approach for a long time in a B2B setting. The fallback to a file picker is really elegant for our use cases wherein some users operate on an old-school desktop PC rather than a mobile device. The state of the modern web is pretty incredible now. There really isn't any kind of application that I would feel uncomfortable building this way in 2022. For me, native has evolved into pure overhead (un…
This mindset is exactly why we all have to suffer with slugish electron apps and bloated websites instead of using fast, native apps written in something like Qt.
Re: TIL: You can access a user’s camera with just HTML
#215We've been using this approach for a long time in a B2B setting. The fallback to a file picker is really elegant for our use cases wherein some users operate on an old-school desktop PC rather than a mobile device. The state of the modern web is pretty incredible now. There really isn't any kind of application that I would feel uncomfortable building this way in 2022. For me, native has evolved into pure overhead (un…
This mindset is exactly why we all have to suffer with slugish electron apps and bloated websites instead of using fast, native apps written in something like Qt.
The actual reason is that nobody (probably not even you) wants to pay the substantially higher price of developing native apps, nor do they want the suffer the loads of crash bugs that inevitably come with using lower-level technology.
The mindset of developers is what it is because the requirements demand so.
Re: TIL: You can access a user’s camera with just HTML
#216Earlier quoted context omitted.
I'm getting a cert error. Subject is *.fortinet.com, not nega.radioac.dev. Edit, the second: Disregard. It's definitely a corporate middlebox on my end.
My guess is that some corporate filter blocked it because of the "nega" subdomain. Kind of sounds like the racial slur. Edit: it doesn't help that the domain is `radioac.dev`. So *NEGA.R*adioc.dev
Nah. It's in the Fortiguard category "Newly Observed Domain". So, it hasn't been classified yet, and that person's corporate filter was setup to block those pages.
Re: TIL: You can access a user’s camera with just HTML
#217fine
Re: TIL: You can access a user’s camera with just HTML
#218Earlier quoted context omitted.
What an awesome idea! Was thinking of doing raspi craziness for capturing birds out my window. Why do that when you can duct tape an old phone to the window lol
There are apps for turning old phones into dashcams and security cams, too. Why waste an old phone?
GPS, accellerometors, gsm, battery, usb. A cheap usb breakout board and youre all set. Meanwhile try to by this for your raspi
Re: TIL: You can access a user’s camera with just HTML
#219Earlier quoted context omitted.
Because it's the easiest way to distribute software. The alternative to standards is every browser vendor doing their own thing, and "this website only works on IE". Remember the bad old days of the web where every bank required Windows because their UI was implemented with ActiveX? Standards killed that and now you can view your bank account on Linux. WebRTC has its security downsides, but probably better than runni…
> Because it's the easiest way to distribute software. Not really, webdev is a pain just as much as making a native Windows app or Go binary. Programming is bullshit all the way down. The moment you try to do anything correct in absolutely any modern software stack or framework, you will have to do a bunch of hacks to indirectly force stuff into doing what's needed for your program to be correct. Of course in practic…
> webdev is a pain just as much as making a native Windows app or Go binary
I didn't mean to imply it was easier for the programmer. It's harder! But it's easier for the end user. Click link, app loads. Next best thing to being bundled with the OS.
Re: TIL: You can access a user’s camera with just HTML
#220This and the Web Speech API were quite unexpected things to discover lately. Even quite robust browser support, besides speech recognition missing on Firefox. Didn't expect to have that easy access to TTS/Speech Synthesis. https://developer.mozilla.org/en-US/docs/Web/API/Web_Speech_... https://www.google.com/intl/de/chrome/demos/speech.html
The TTS apis are really fun. They allow pitch control, too:
"twin=75 kill=75 twin=115 kill=115 lit=130 till=130 star=110 how=100 i=100 won=90 dur=90 what=85 you=80=2 are=70".split(" ").map(s=>{u=new SpeechSynthesisUtterance((t=s.split('='))[0]);u.pitch=parseInt(t[1]||100)/100;u.rate=parseFloat(t[2]??1.5);speechSynthesis.speak(u)})