Moulin Rouge. Captures a lot of the cinematography you see in Snatch, and it’s a musical. Great story, great writing, and great performances curtain to curtain.

I expect it is natural that there is a tipping point, where there is enough content that it becomes engaging for others. It’s like going to a house party. The first few people to arrive at the party awkwardly stand around and might leave early. Once there is the right number of people, the group dynamic shifts and the entire energy of the party is elevated. The Exodus brought a lot of curious visitors, but everyone was standing around. Now there’s engaging content and comments are growing. Some of those who stopped by in June will likely come back at some point if they left early – I did the same thing in the early days of Reddit. I think there’s been a large enough influx to kick things off and I expect things to continue to grow, but the active user count was probably inflated significantly over the past couple of months and will be resetting to more reasonable numbers.

What are a set of tools I can recommend to my employer, which increase productivity of office workers, and which provide greater value than a hybrid office policy?

You could argue that place was a copy. Before that you had The Million Dollar Homepage (https://en.wikipedia.org/wiki/The_Million_Dollar_Homepage?wprov=sfla1) in 2005, where companies could buy a pixel for a dollar. I have a hard time believing that it didn’t have some influence over the creation of place.

The video cable does a similar trick with how it supports color. This is why S-Video was superior to composite video until component came along. S-Video split the intensity and color into two signals and then component split the color further into a blue difference and a red difference. If you only wanted black and white, you didn’t need to use the color signals and the image would degrade to a monochrome representation.

The composite video, with only one video signal wire, was similar to what was received over the antenna, with the broadcast signal separated from the carrier signal and the audio sub bands removed. It was the video signal with the color signal still combined. The progression from Antenna -> Composite -> S-Video -> Component -> DVI-I -> DVI-D -> HDMI -> Display Port has been an interesting one. The changes in the digital realm have been less about the image quality, the digital signal can either be read or not, and more about the bandwidth and how much data can be sent, aka resolution and framerate. Those first four transitions in particular had significant impact on the image quality.

They are different as you and I have both described, but when the sink device can support different streams, it has a significant advantage, because it automatically can support sinking frames from the broadcasting device and it removes the overhead of decompressing and then recompressing with practically assured data loss. It is yet another example of how patents, especially software patents, work against the original intent of the patent process.

I read what you said and completely missed it. It’s there, but pretty hidden. Might not even be known. I’m not sure that makes it bold.

I selected “was” simply because I don’t have enough understanding of the current situation to argue it from that standpoint.

In many ways, Chromecast is superior. Removing the rendering task from the tablet or phone, and letting the receiver manage that, it’s significantly better than making the mobile device decompress the source stream and then decompress it for a Miracast receiver. The only real advantage Miracast has in this is that it doesn’t need to receive firmware updates to keep it up to date with newer protocols. With Miracast being built in to TVs, and possibly implemented in an ASIC, it should be a universal fallback. With Android 4.2 it was a built in protocol to AOSP. What I didn’t know was that it was actually stripped back out with Android 6. I thought dropping support was specific to Google devices only.

What really needs to be implemented is a non-proprietary extension to Miracast which goes back to the early Chromecast days when it was based on the DIAL protocol. It’s incredible that we have to deal with so many proprietary standards from Airplay and Chromecast, and then also support the wifi alliance standard for Miracast.

Those glares from the others should resolve your confusion.

I think it’s closer to 75% (75.25% precisely). 55% because of the attack and 55% trying to figure out what the picture is. Stacking those stats, of those who weren’t confused at first, those 45% remaining were subjected to the effect of the attack. Only 25% remained unaffected.

Considering I’ve enjoyed some of the “old” videos the algorithm sometimes sends my way, I’m not always disappointed when I find one I hadn’t seen before.

But that wire has to end at a WiFi transmitter at some point, it won’t work purely over ethernet wire, for example.

Yeah, not sure about that since those devices in question, where I’ve used it, have some Wi-Fi somewhere. I just remembered that there has been something done to provide it over a wired connection, but the device would have been wired to an access point. My specific use case was an Xbox wired to an AP and casting wirelessly from my laptop. So there is a wireless hop in the mix.

Very few vendors have bothered to include it, mostly the Chinese low and mid-tier device manufacturers. But it is not widely supported since, I want to say, circa 2017.

It was standard in Android. The only time I had ran into a situation where I haven’t had it was Google Nexus 6+. I haven’t tried a lot of different OEMs, but OnePlus and Microsoft have (had) it for sure. Samsung I have used their Smart View service, but I thought it was Miracast with Samsung specific extensions. Meta Quest 2, I was surprised seems to only work with Chromecast. However that suggests that you may be right. Most of my devices have support, but not all do.

Miracast is plagued by latency problems, but it is still alive. Android itself still has support, it is the Nexus 6 that Google dropped support, to only support their Chromecast. Microsoft Xbox can be used as a Miracast receiver and there is support for Miracast built into Windows 10+, both as a receiver and transmitter. While Miracast was built upon Wi-Fi Direct, (Wi-Di, I believe), it has been extended to work over a wired network too. The biggest difference is that Miracast is transmitting the frames over the network, so that the device transmitting needs to render the content, whereas DIAL and Chromecast are sending steam URLs, authentication, and transport messages to the Chromecast, which then is the device actually rendering. Chromecast is better for mobile device batteries, but I loath the proprietary nature of it.

Might be thinking about DLMA? That wasn’t just a Samsung thing but predates this.

You might say extra redundant?