first thing that came to mind, lmao. the number of devices with absolutely zero consideration for how the cert will get refreshed is astonishing. embedded SSL stacks tend to be a complete pain in the ass to deal with, but it's still no excuse for not at least thinking about it in the product stage. (just as likely someone DID think about it and it got pushed off and pushed off until the first gen product was EoL'd, though...)This was a certificate wasn't it?
Which current chromecasts have been abandoned?ok, but why don't they work on fixing current devices,
and improving them.
fixing old devices is a very tiny drop compared to what they have,
and they'll abandon them anyway at some point.
ok, but why don't they work on fixing current devices,
and improving them.
fixing old devices is a very tiny drop compared to what they have,
and they'll abandon them anyway at some point.
It shouldn't, but all you have to do is look back on the Y2K crisis to see that failure to look far enough ahead is always a problem.Why should a device literally ever cease to be able to do the function it could do when it rolled off the production line, barring hardware failure?
Because that's not how CCs work. You're not streaming from the controlling device to the CC. You're essentially giving the CC a link to media and the CC streams the content directly.Why does any device other than the chromecast and the casting device need to be involved? I always assumed, given they are on the same network or in the same room, they could find each other and share the video without any other devices being involved.
And this always struck me as a elegant, efficient solution: the video stream gets from the remote service that has it, to the display adapter that needs it - why should it tunnel through my phone to the CC using double the bandwidth on my network?Because that's not how CCs work. You're streaming from the controlling device to the CC. You're essentially giving the CC a link to media and the CC streams the content directly.
There's quite a collection of music streamers that support multiple platforms and multiroom audio that could replace a Chromecast Audio, while also offering more functionality:I'm glad my ChromeCast Audios still work. I'm dreading the day I have to figure out a replacement for them to keep all my old amps around the house playing the same thing in sync.
And to the OP's situation, I'm pretty sure the WIIM stuff support the actual ChromeCast Audio protocol too, so they could conceivable replace failing units one at a time is needed without shifting to a whole new system.There's quite a collection of music streamers that support multiple platforms and multiroom audio that could replace a Chromecast Audio, while also offering more functionality:
And for anyone only needing an Apple Airplay receiver, similar to the old Apple Airport Express devices: https://www.belkin.com/p/audio-adapter-with-airplay-2/AUZ002ttBK.html I personally have one and it works wonderfully.
- https://www.wiimhome.com/wiimmini/overview
- https://www.arylic.com/products/s10-wireless-preamplifier
- https://www.evehome.com/en-us/eve-play
But why can't the CC have its own server that can be paired with your device and receive those links directly from it? Why does it HAVE to go through Google's servers?Because that's not how CCs work. You're not streaming from the controlling device to the CC. You're essentially giving the CC a link to media and the CC streams the content directly.
E: forgot a word
WiiM products support Chromecast audio (called Google Cast in WiiM): https://faq.wiimhome.com/en/support...-enable-or-disable-google-cast-on-wiim-deviceAnd to the OP's situation, I'm pretty sure the WIIM stuff support the actual ChromeCast Audio protocol too, so they could conceivable replace failing units one at a time is needed without shifting to a whole new system.
That depends if you consider "be secure" as a function. This is a device that needs access to the internet.Why should a device literally ever cease to be able to do the function it could do when it rolled off the production line, barring hardware failure?
Yeah. Its also way harder to go into "audio only" mode.I've also noticed the casting button disappeared from YouTube and only appears once a video is actually playing. I suspect Google would prefer it if we used something that shoved more advertising at us .
Because thats how it was made, thats how it was marketed, and thats how it has always worked?But why can't the CC have its own server that can be paired with your device and receive those links directly from it? Why does it HAVE to go through Google's servers?
Because how else is Google going to complete their profile of you by getting a record of everything you've ever cast?But why can't the CC have its own server that can be paired with your device and receive those links directly from it? Why does it HAVE to go through Google's servers?
Still using a Squeezebox Radio. Loving the open, community firmware and server. How is it my Squeezebox works 15 years later and nothing else that old still does?As a weirdo that loves the functionality of Squeezebox/now-Lyrion server, I expecting WIIM gear for this sort of migration by attrition - the wide range of protocols seems like good future proofing.
Modern WIFI routers can be (and sometimes default to) a mode where devices on the same network can only communicate out to the internet and not each other. This adds more security to a network where a compromised device on the network cannot try to spread to or hack into other devices on the same network.Why does any device other than the chromecast and the casting device need to be involved? I always assumed, given they are on the same network or in the same room, they could find each other and share the video without any other devices being involved.
This is also not how Chromecasts works. You don't reach out to Google to control a Chromecast. If that was the case, how would you discover Chromecasts on the network you were on that weren't set up by you, for example?Modern WIFI routers can be (and sometimes default to) a mode where devices on the same network can only communicate out to the internet and not each other. This adds more security to a network where a compromised device on the network cannot try to spread to or hack into other devices on the same network.
In general this makes it easier (for "consumer" oriented tech) to rely on a public internet intermediary for cases where 2 devices need to communicate with each other. It has the added benefit of allowing the 2 devices to communicate even when they are not on the same network.
Given that my two 2nd gen Chromecasts both still work perfectly, get security updates and fulfil my casting needs, exactly why is it "time for me to move on"?I had a 2nd gen Chromecast. You can replace it for a few bucks it's time to move on.
Why should any device or tool work perpetually?Why should a device literally ever cease to be able to do the function it could do when it rolled off the production line, barring hardware failure?