Better devices like Jabra headsets integrate directly with Teams and will actually synchronize mute status between the headset and Teams!
106 karma · joined February 14, 2017
Better devices like Jabra headsets integrate directly with Teams and will actually synchronize mute status between the headset and Teams!
But what is it?
Ideally, I would like to be able to point at some RSS feed of torrents of relevant archive.org collections (whatever the curators believe popular enough to benefit from peer-to-peer distribution). I could then set a torrent client to donwload and seed everything on this feed.
DRM is often seen as some sort of dark art. A lot of this comes from the proprietary nature of it, with NDAs on every corner and technology licensing processes that require months of effort to get access to even the basic documentation.
Over the past decade, ever-increasing standardization in the media industry has opened up DRM to a great degree, though much remains in the proprietary domain for legacy reasons. Even though standardization has helped a great deal, it is hard to find human-readable information about DRM. ISO/IEC 23001-7:2016 does not make for easy bedtime reading!
I have worked in the field for 12 years and was recently motivated to share my knowledge and remove some of the unwarranted mystery from the field. I am currently writing up a new series of articles, to be published starting May, opening up the topic of DRM for a wider audience. You will find them at my website, though right now there are only a few old articles from ancient history there.
If you make solutions that aim to provide Hollywood grade content or just think this topic sounds interesting, this upcoming series might be a good introduction to the necessary content security universe for you. I might also post other digital media topics there from time to time.
I could try think of why but in practice, it just seems to work out the best. Are there reasons? Sure. But coming up with a detailed rationale would take some days of thinking. It just works very well.
This means on my service side I expose SaveWidget(id, body) ReadWidget(id) PatchWidget(id, changes) QueryForWidgetsByFoo(foo) QueryForWidgetsByFooBarAndSomeOtherSTuff(foo, bar, otherstuff) and on the client side I just call them as if they were local (but rather slow performing) functions.
Lots of little ifs and buts but this has proven the superior approach in all scenarios where I control both client and server. I might go for REST for wide-audience APIs just for the recognizability.
That seems like a huge amount of customers, no? The income from 2% of customers is enough to pay for several employees' salaries, I bet.
In contrast, VeraCrypt developers did not seem to understand what a TPM is when I tried to discuss the topic with them.
This meant you could keep scrolling and what do you see - a few pages after the blurred out answers were the real answers!
This is a tiny shade of background in the story, not the main story, but read the books if you like this kind of tale.
There is a CO2 sensor on my desk for 10 years already. Generally it is around 650 ppm during a working day but occasionally the building's ventilation system's power trips and air movement suddenly decreases. This causes CO2 levels to rise fast - once they hit 900-1000 ppm, I can definitely feel a decrease in my ability to focus and think clearly (and yes, I feel it even before looking at the numbers, ha!).
Obviously silly single anecdote but subjectively the link is very strong for me!
PS. On a sad note is that I remember the days when coming to work in the morning meant the CO2 level was at 350 ppm. These days clean air is 450 ppm in this city!
I would be interested how RTX compares to the other Quake2 renderers that it originally came with.