mynameislegion

21 ms·

241.
JPEG 101: How does JPEG work?(arjunsreedharan.org)
4 points by mynameislegion 10y ago|0 comments
242.
by mynameislegion 10y ago
ok, whatever you say boss hog
243.
by mynameislegion 10y ago
I use option and control all the time for muscle memory keybindings, but every time I see "⌥" or "^" as a shortcut in a menu, I need to check which is which. After all the time I've spent on cli, you'd think I&
244.
by mynameislegion 10y ago
In the same vein, see this comment from the same article a few days ago: https://news.ycombinator.com/item?id=11826855
245.
by mynameislegion 10y ago
Sorry, you haven't thought this through. As long as XMPP exists in a state where there are public servers with varying XEP support then adoption rates will always languish. A user would actually have to do considerable research to un
246.
by mynameislegion 10y ago
You need to think about this from a non-technical user perspective. They'll be using the Conversations server, guaranteed. Because 1) They're not going to run their own server. 2) They're not going to bother researching whi
247.
by mynameislegion 10y ago
I think you missed the thrust of my argument which is that XMPP sucks from a _user_ perspective. A non-technical user perspective which is 90% of the users in the real world. > False. XMPP has excellent feature negotiation capabilities.
248.
by mynameislegion 10y ago
> XMPP just works everywhere. You only need one account to cater to all your instant messaging needs. If your workflow changes you just pick a different client. AFAIK, this is painfully wrong and one of the main reasons XMPP struggles.
249.
by mynameislegion 10y ago
> Your logic would justify every vendor-lock-in attempt from Apple & Microsoft; it would support the idea that all the Internet's IE. Except in this case the "vendors" are the makers of every popular browser and the st
250.
by mynameislegion 10y ago
> Firefox with NoScript cannot display Blogger pages; the Tor Browser with high security cannot display Blogger pages. These configurations disable universal features, so the premise holds. > The Web is, fundamentally, about resources
251.
by mynameislegion 10y ago
I agree. Before the prevalence of JS you could simply download the text. But now, much of the text interpreted. So if you wish to get all the text, you must also do the interpretation step. Which essentially means running a headless brow
252.
by mynameislegion 10y ago
> the web is about webs of interlinked documents If this is true, and my browser can follow a link to a Blogger page, displaying the intended document using universal browser features, then the Web is not broken. This kind of evangelism
253.
by mynameislegion 10y ago
Comparable equipment has traditionally cost in the 10s of thousands. Only in the last two or three years has it been in the home hobbyist range.You don't need a SDR anyways.. unless you want to monitor multiple frequencies at once whic
254.
by mynameislegion 10y ago
I don't see how this will make any difference to performance. I'll try but really ondemand cpu scaling should be just as fast.
255.
by mynameislegion 10y ago
Thank you, bzbarsky. Please help us (me) understand the situation a bit better if you have the time. 1. Could you please describe a bit more about the browser-CDM interaction and what is implemented there? 2. Why do you think the browser-C
256.
by mynameislegion 10y ago
So then, the only way CDMs are acceptable IMO is if they're never given enough information to know where they're running. This should be a critical part of the standard and I'm surprised I haven't heard the EFF pushing f
257.
by mynameislegion 10y ago
The common API is called "EME". Chrome and Firefox's API's are different because they're unfinished.
258.
by mynameislegion 10y ago
That assumption may indeed be false. See here[0] in the FAQ "What does this mean for downstream users of the Firefox code base?" >>> The solution consists of three parts: the browser, the CDM host and the CDM. >>&g
259.
by mynameislegion 10y ago
The CDM API is called "EME" and it is a standard. That's why Widevine can be made to work with Firefox ( https://github.com/i-rinat/gmp-widevine ). EDIT: Firefox now supports Widevine > Beginning in v
260.
by mynameislegion 10y ago
The specification is called EME. > Beginning in version 47, Firefox desktop also supports the Google Widevine CDM. https://support.mozilla.org/en-US/kb/enable-drm
261.
by mynameislegion 10y ago
In the assumption I'm describing, it's irrelevant which CDM a publisher chooses. The reason being that the CDM must operate via EME, an open standard that can be implemented by any browser. Therefore, CDMs are inherently browser
262.
by mynameislegion 10y ago
I've read many articles critical of EME and this is the first time I've heard this information. If true, as you said, it is THE issue. It was always my assumption that EME represented a standard way for CDM's to interact wit