recentpopularlog in

mikael : standards   232

« earlier  
O.L.D. (Over-Locknut Dimension)
O.L.D. stands for Over-Locknut Dimension. This is the width of the hub measured from outside of locknut to outside of locknut. It is not to be confused with the axle length, as the axle extends into or beyond the frame dropouts. The O.L.D. needs to match the available space in the frame between the fork or frame tips. Rear hubs vary in width (but most new ones are 130mm for road or 135mm for mountain). The hub width (over-locknut dimension) needs to match the space between the rear wheel dropouts in the frame in order for things to line up as they should.
bikes  cycling  wheels  standards  frames 
6 weeks ago by mikael
The specification for native image lazy-loading is merged into HTML standard
Huge thanks to @domfarolino for making this happen and everyone who gave feedback and helped out along the way! Looking forward to faster page loads.
html  css  webdev  graphics  development  standards 
7 weeks ago by mikael M-gänga
Gänga: M5. Stigning P (mm): 0,8.
swedish  standards  hardware  wiki 
12 weeks ago by mikael
Thread Size on Older Bike's Rack/Fender Mount
Close to 100% of threaded fender/rack mount eyes are 5x. 8mm, the same as the water bottle screw. If you have brazed on WB mount, you might borrow that screw and confirm. Close to 100% of modern rack mount eyes are M5 threads (a 10-32 will also work).
standards  bikes  cycling  forum-posts 
12 weeks ago by mikael
Google's Chrome Becomes Web `Gatekeeper' and Rivals Complain
Chrome is so ascendant these days that web developers often don’t bother to test their sites on competing browsers. Google services including YouTube, Docs and Gmail sometimes don’t work as well on rival browsers, sending frustrated users to Chrome. Instead of just another ship slicing through the sea of the web, Chrome is becoming the ocean. “Whatever Chrome does is what the standard is, everyone else has to follow,” said Andreas Gal, the former chief technology officer of Mozilla. Google didn’t target Mozilla in overt ways during Gal’s seven years at the company. Instead, he described it as death by a thousand cuts: Google would update Docs, or Gmail, and suddenly those services wouldn’t work on Mozilla. “There were dozens and dozens of ‘oopsies,’ where Google ships something and, ‘oops,’ it doesn’t work in Firefox,’’ Gal said. “They say oh we’re going to fix it right away, in two months, and in the meantime every time the user goes to these sites, they think, ‘oh, Firefox is broken.’’’
chrome  browser  firefox  articles  business  asshole  standards 
may 2019 by mikael
European Standards for Bicycles
EN 14766:2005 for mountain bicycles.
eu  standards  bikes  cycling 
december 2018 by mikael
Nicer CSS underlines with text-decoration-skip: ink;
The use of text-decoration-skip: ink; has been deprecated. One should use text-decoration-skip-ink: auto; instead.
typography  css  blog-posts  standards  webdev 
october 2018 by mikael
bit of a silly question but where do I find the rel="me” in the Mastodon profile?
metadata  standards  microblogging  mastodon  identity 
august 2018 by mikael
ActivityPub could be the future
I think the growing ActivityPub federation has a good chance. No one interacts with my tweets anymore. Meanwhile, I get response on Mastodon that reminds me of the early days of Twitter, before they betrayed their developer community and hired a legion of people to cut ad deals. [ ]
blog-posts  standards  socialmedia  protocols 
july 2018 by mikael
Slack's bait and switch
We all know the real reason Slack has closed off their gateways. Their business model dictates that they should. Slack's business model is to record everything said in a workspace and then to sell you access to their record of your conversations. They're a typical walled garden, information silo or Siren Server. So they have to close everything off, to make sure that people can't extract their conversations out of the silo. We saw it with Google, who built Gtalk on XMPP and even federated with other XMPP servers, only to later stop federation and XMPP support in favour of trying to herd the digital cattle into the Google+ enclosure. Facebook, who also built their chat app on XMPP at first allowed 3rd party XMPP clients to connect and then later dropped interoperability.

Twitter, although not using or supporting XMPP, had a vibrant 3rd party client ecosystem which they killed off once they felt big enough. Slack, like so many others before them, pretend to care about interoperability, opening up just so slightly, so that they can lure in people with the promise of "openness", before eventually closing the gate once they've achieved sufficient size and lock-in.
chat  irc  xmpp  standards  instant-messaging  blog-posts  business 
march 2018 by mikael Avid DNxHD
DNxHD is intended to be an open standard, but as of March 2008, has remained effectively a proprietary Avid format. The source code for the Avid DNxHD codec is freely available from Avid for internal evaluation and review, although commercial use requires Avid licensing approval. It has been commercially licensed to a number of companies including Ikegami, FilmLight, Harris Corporation, JVC, Seachange, EVS Broadcast Equipment.
video  standards  preservation  wiki 
december 2017 by mikael
Boring, complex and important: a recipe for the web's dire future
The Electronic Frontier Foundation has resigned from the W3C, the body responsible for governance of web standards. Cory Doctorow explains why.
standards  internet  articles  drm 
september 2017 by mikael
Netflix, Microsoft, and Google just quietly changed how the web works
The organization that sets standards for the web just failed to beat back a stupid, greedy technology.
drm  standards  internet  copyright  articles 
september 2017 by mikael Videotape format war
The videotape format war was a period of intense competition or "format war" of incompatible models of consumer-level analog video videocassette and video cassette recorders (VCR) in the late 1970s and the 1980s, mainly involving the Betamax and Video Home System (VHS) formats. VHS ultimately emerged as the preeminent format.
standards  video  movies  history  business  wiki 
august 2017 by mikael
Tim Berners-Lee approves Web DRM, but W3C member organizations have two weeks to appeal
Yesterday Tim Berners-Lee, the chief arbiter of Web standards, approved the controversial proposed Digital Restrictions Management (DRM) standard for the Web, Encrypted Media Extensions (EME).
drm  standards  internet  video  audio 
july 2017 by mikael
Why the Emoji Was Inevitable
Emojis are the body language of the digital age.
emoji  culture  internet  standards  articles 
july 2017 by mikael Standard (warez)
Standards in the warez scene are defined by groups of people who have been involved in its activities for several years and have established connections to large groups. These people form a committee, which creates drafts for approval of the large groups. Outside the warez scene, often referred to as p2p, there are no global rules similar to the scene, although some groups and individuals could have their own internal guidelines they follow.
piracy  filesharing  standards  wiki  video  audio  fileformats  scene 
june 2017 by mikael
USB Type-C and power delivery 101 – Ports and connections
USB Type-C is the newly introduced and powerful interconnect standard for USB. When paired with the new Power Delivery (PD) specification, Type-C offers enhancements to the existing USB 3.1 interconnect that lower the cost and simplify the implementation of power delivery over USB. From a form factor perspective, the USB Type-C connector combines multiple USB connectors – Micro-B, Type-A, and Type-B – in a reversible connector measuring only 2.4 mm in height (see Figure 1). Type-C allows developers to also combine multiple protocols in a single cable, including DisplayPort, PCIe or Thunderbolt. Bandwidth is double that of USB 3.0, increasing to 10 Gbps with SuperSpeed+ USB3.1. Finally, the USB Type-C connector can deliver up to 100 W. This enables a wider range of applications to operate using USB (see Figure 2). For more details, watch An Introduction to USB Type-C video and Type-C Basics.
hardware  cables  usb  standards  references 
may 2017 by mikael Standardisering - Grafiska symboler - SIS/TK 493
Användande av enhetliga och funktionella grafiska symboler gör olika platser i samhället tillgängliga för alla människor. I Sverige, Europa och även globalt pågår arbete inom standardiseringen som syftar till att förbättra och skapa publika informationssymboler för ökad tillgänglighet utifrån konceptet Design för alla.
standards  swedish  accessibility 
may 2017 by mikael Maildir
The Maildir e-mail format is a common way of storing e-mail messages, where each message is kept in a separate file with a unique name, and each folder is a directory. The local filesystem handles file locking as messages are added, moved and deleted. A major design goal of Maildir is to eliminate program code having to handle locking, which is often difficult.
email  standards  software  open-source  backup  wiki 
april 2017 by mikael
Digitization at the Smithsonian Institution Archives
* 6,000 pixels on the long axis of the image (600 pixels per inch (ppi) for an image 10 inches long)
* Minimum value is 600 ppi, increasing resolution in intervals of 25 ppi as necessary to achieve a minimum of 6,000 pixels along the long axis

Digital File Format
* Tagged Image File Format (TIFF) using Windows (PC) byte orientation.
* For color images, a 24 bit RGB setting is used, yielding 8 bits per color channel.
* For black and white images, a 24 bit RGB setting is used. Note: for images from microfilm, a resolution of 300 ppi grayscale is acceptable.

File Compression
* None
digitization  standards  scanning  preservation  archiving 
april 2017 by mikael
Explanation: message synchronization between clients
Some systems like Apple's Messages or Google Hangouts support syncing of incoming and outgoing messages between a few connected clients with the same username. [...] XMPP has a XEP covering synchronization of the outgoing and incoming messages between several clients logged in with the same username (XEP-0280: Message Carbons). [...] Both server and a client must support this. [...] Note: this only works when both (or more) clients are online. If client1 sends a message, but client2 was offline during that moment, client2 won't have this sent message in his history. There is no history synchronization like in Google Hangouts. [...] There are also two XEPs covering history storing on the server and history synchronization between devices. Older and more broad XEP-0136: Message Archiving and still in experimental state XEP-0313: Message Archive Management.
xmpp  jabber  instant-messaging  standards 
april 2017 by mikael XEP-0384: OMEMO Encryption
This specification defines a protocol for end-to-end encryption in one-on-one chats that may have multiple clients per account.
instant-messaging  standards  xmpp  jabber  encryption 
april 2017 by mikael imaginator on XEP-0280: Message Carbons (2013)
Background: XEPs are the protocol building blocks of XMPP.

The XSF (XMPP Standards Foundation) are working hard to make XMPP more mobile friendly. (disclaimer: I'm an XMPP board member).

There are three problems to solve:

1. knowing when to retrieve messages (push notifications)

2. retrieving messages (message archive management)

3. synchronising messages between devices (what this solves)

More background: XMPP is designed around keeping a connection open to the client and pushing through updates and new messages. These assumptions worked well in a desktop environment on a solid TCP connection. But for power, intermittent network, and mobile OS design reason, holding open a socket isn't ideal.

Push notification work because the OS provider (Apple, Google, Mozilla etc.) keep one socket open and then push through important notifications. This keeps the phone's radio from powering up for silly things like "contact came online/went offline" type messages.

A push notification might be "xyz posted ... ". Your phone needs to now come online and synchronise messages that might have been posted on your tablet or desktop client. Hence XEP-0280. It helps resync messages from other clients.

The XSF is also writing up a push notification XEP that makes it easy for mobile apps to use XMPP as a signalling channel and throw out push notification where necessary.
standards  xmpp  jabber  mobile  instant-messaging  hackernews  forum-posts 
april 2017 by mikael XEP-0280: Message Carbons
In order to keep all IM clients for a user engaged in a conversation, outbound messages are carbon-copied to all interested resources.
xmpp  jabber  standards  instant-messaging 
april 2017 by mikael RFC 1855 - Netiquette Guidelines
This document provides a minimum set of guidelines for Network Etiquette (Netiquette) which organizations may take and adapt for their own use. As such, it is deliberately written in a bulleted format to make adaptation easier and to make any particular item easy (or easier) to find. It also functions as a minimum set of guidelines for individuals, both users and administrators. This memo is the product of the Responsible Use of the Network (RUN) Working Group of the IETF.
history  internet  netiquette  education  standards  culture 
march 2017 by mikael Signature block
The Usenet standard RFC 3676 specify that a signature block should be displayed as plain text in a fixed-width font (no HTML, images, or other rich text), and should be delimited from the body of the message by a single line consisting of exactly two hyphens, followed by a space, followed by the end of line (i.e., in C-notation: "-- \n"). This latter prescription, which goes by many names, including "sig dashes", "signature cut line", "sig-marker", "sig separator" and "signature delimiter", allows software to automatically mark or remove the sig block as the receiver desires.
netiquette  internet  history  email  wiki  plaintext  standards 
march 2017 by mikael
Sir Tim Berners-Lee refuses to be King Canute, approves DRM as Web standard
Many of the comments on Berners-Lee's post are also strongly critical of his position. Most of the arguments put forward are ideological rather than pragmatic, and do not address his counter-points about DRM being a simple reality with EME offering a standard that ultimately provides better protection for the Web as a whole. There is, however, one serious argument over why EME may not be a good idea, and that is whether it will result in companies, from Netflix to Google, effectively requiring you to use a particular browser to view video content. It has been at least five years since the "best viewed with browser X" message on websites was a common occurrence, largely because Microsoft lost its dominance of the browser market and browsers such as Firefox and Chrome – which try to adhere to standards much more closely – became the new norm (last year Firefox overtook Internet Explorer on the desktop for the first time with roughly 15 per cent of the market; Chrome has a whopping 60 per cent). However, due to the way EME is structured, the "standard" will include a critical element that will likely be different from browser to browser.
articles  standards  drm  internet 
march 2017 by mikael
Response to Tim Berners-Lee's defeatist post about DRM in Web standards
On Monday, he published a blog post defending his recent decision to override objections to streaming and browser companies' plan to enshrine insecure, freedom-defying DRM (Digital Restrictions Management) in the technical standards that underly the Web. The plan, known as EME (Encrypted Media Extensions), would grant perceived legitimacy to these digital handcuffs and energize the long-standing campaign to incorporate them ever deeper into the digital world. As director of the W3C (World Wide Web Consortium), Berners-Lee has the ability to block EME from ratification as an official Web standard. Nevertheless, he defended his decision not to do so, arguing that "[i]f the Director Of The Consortium made a Decree that there would be No More DRM in fact nothing would change. Because W3C does not have any power to forbid anything."
standards  drm  internet  blog-posts 
march 2017 by mikael Oxitendwe's comment on I invented the web. Here are three things we need to change to save it
>>>>>>> If Tim Berners-Lee really wanted to save the web, he wouldn't support DRM in our web standards.[1] It's absolutely disgusting as well that they would argue that "fake news" is somehow a threat to the internet, provide no evidence whatsoever to explain why, and then link to a panel run by a media company considered untrustworthy by about half of American voters.[2]

>>>>>> Yes, and he wouldn't endorse WebAssembly either (which is just a different, and even worse avenue towards DRM).

>>>>> Isn't WA rather easy to reverse engineer? The VM it runs in isn't overly complicated, and is open to the public. Whereas EME is more, trust this native code please, and give it all the access it asks for?

>>>> WA makes it possible to replace entire browser runtimes with proprietary stuff. For example, you can compile WebKit to WA, with typography rendering and flow layout on a Web Canvas, and "Save as HTML" and other basic functionality disabled. I find it very irritating that TBL/W3C is promoting this and EME. I think W3C should be seen as what it is - a self-proclaimed standardization company acting in the interest of whoever pays the hefty membership bills struggling to keep relevant.

>>> But still, you can inspect that WA code, and WA doesn't have access to the DOM. Inspecting the EME packet is a crime in many jurisdictions, and designed to be difficult. WA makes sense as what it is intended to do: give a memory efficient alternative to JavaScript in circumstances that warrant it.

>> What are circumstances that warrant it in a web browser? The things it makes possible can be had with native apps. What it does make possible is a new model for software and content sales. Which is precisely why I find it has no place in a web spec.

> I wish you were right, but the market has decided that the web is the next cross-platform framework.

If this has to happen, let's make it work in a way that doesn't let the stupidest ideas survive. Using WA still requires JS to interact with the user. Which is far better than the monstrosities that JS is being forced to perform at the moment.
Some simple, relatively sane things that WA can do, but JS is a bad choice for:
* Client-side encryption/decryption
* Socket management
hackernews  forum-posts  webassembly  drm  standards  programming  internet 
march 2017 by mikael
News Genius wants to annotate the entire Web. At what cost?
A new tool wants to annotate everything on the Internet. But at what cost?
webdev  standards  webannotations  articles 
march 2017 by mikael Two days with the shadowy emoji overlords
What’s more, I learned, this is capitalism. The Emoji Subcommittee decides which emoji live and which die by making recommendations to the Unicode Technical Committee. In typical woo-woo California style, the committee makes decisions based on consensus voting, but you have pay your way into voting rights: full members pay $18,000 a year for the right to vote. As a result, the membership is comprised of corporations like Apple, Facebook, Google, IBM, and, less predictably, the Ministry of Endowment and Religious Affairs of the Sultanate of Oman. And this is nation building. India joined the Unicode Consortium in 2000; afterwards, the Indian state of Tamil Nadu joined independently as a polite Eff you to India and to add fuel to a dispute they were having over whether to encode Tamil as a syllabary language (as was commonly being taught to schoolchildren in the state) or with the Brahmi-based encoding model of greater India.
emoji  unicode  standards  articles 
december 2016 by mikael
The World Wide Web Consortium at a Crossroads: Arms-Dealers or Standards-Setters?
The World Wide Web Consortium (W3C) has a hard decision to make: a coalition including the world's top research institutions; organizations supporting blind users on three continents; security firms; blockchain startups; browser vendors and user rights groups have asked it not to hand control over web video to some of the biggest companies in the world. For their part, those multinational companies have asked the W3C to hand them a legal weapon they can use to shut down any use of online video they don't like, even lawful fair use.
standards  articles  webdev  internet 
december 2016 by mikael SmashingConf Barcelona 2016 - Jeremy Keith on Resilience
Web browsers have become so powerful that developers are now treating them as if they were a runtime environment as predictable as any other. But the truth is that we still need to deal with many unknown factors that torpedo our assumptions. The web is where Postel’s Law meets Murphy’s Law, so we can’t treat web development as if it were just another flavor of software. Instead we must work with the grain of the web. There are tried and tested approaches to building for the web that will result in experiences that are robust, flexible, and resilient.
html  videos  presentation  standards  history  internet  browser 
november 2016 by mikael – Vägledning för webbutveckling från PTS (förr E-delegationen)
De officiella riktlinjerna för hur man bör arbeta med webbplatser i offentlig sektor.
accessibility  swedish  standards  webdev 
november 2016 by mikael
IEEE sets new Ethernet standard that brings 5X the speed without disruptive cable changes
As expected the IEEE has ratified a new Ethernet specification -- IEEE P802.3bz – that defines 2.5GBASE-T and 5GBASE-T, boosting the current top speed of traditional Ethernet five-times without requiring the tearing out of current cabling. The Ethernet Alliance wrote that the IEEE 802.3bz Standard for Ethernet Amendment sets Media Access Control Parameters, Physical Layers and Management Parameters for 2.5G and 5Gbps Operation lets access layer bandwidth evolve incrementally beyond 1Gbps, it will help address emerging needs in a variety of settings and applications, including enterprise, wireless networks.
network  standards  articles 
october 2016 by mikael
IRC is a networked protocol for group chat, tested and proven for over 20 years. The IRCv3 Working Group is a collection of IRC client and server software authors working to enhance, maintain and standardize the IRC protocol using backwards-compatible extensions.
irc  standards  chat 
june 2016 by mikael DSM: The Decentralized Systems Map
This paper reviews the various technologies which make up the decentralized web movement and classifies them in terms of their responsibilities within an OSI-style conceptual model called DSM: the Decentralized Systems Map. The desired outcome of this paper is six-fold. (1) To promote collaboration, cooperation, and mutual-understanding between those parties creating decentralized web technologies, (2) to clarify the purpose, statuses, and relationships of decentralized web technologies, (3) to better inform and educate the general public, (4) to obtain a more hollistic understanding of which necessary decentralization components are present and which are missing, (5) to conduct a meta experiment of producing a decentralized, reproducible research document and, above all (6) bringing the decentralized web movement closer to solidarity and to becoming an official w3c working group.
decentralization  standards  internet  development 
june 2016 by mikael
Apple’s actual role in podcasting: be careful what you wish for
Podcasts are just MP3s. Podcast players are just MP3 players, not platforms to execute arbitrary code from publishers. Publishers can see which IP addresses are downloading the MP3s, which can give them a rough idea of audience size, their approximate locations, and which apps they use. That’s about it.

They can’t know exactly who you are, whether you searched for a new refrigerator yesterday, whether you listened to the ads in their podcasts, or even whether you listened to it at all after downloading it.

Big publishers think this is barbaric. I think it’s beautiful.
podcasting  apple  blog-posts  standards  rss  decentralization 
may 2016 by mikael
Google EID is encryption for beacons
Google is open sourcing an encryption framework for its Eddystone beacon platform, and making it available on GitHub.
bluetooth  google  standards  encryption  beacons 
april 2016 by mikael Graphics display resolution — WQHD
WQHD (Wide Quad HD),[2] or 1440p,[3] is a display resolution of 2560x1440 pixels in a 16:9 aspect ratio. It has four times as many pixels as the 720p HDTV video standard, hence the name. It is also called QHD, which is more consistent with the naming convention in use, but it is more commonly called "WQHD" to avoid confusion with qHD with a small q (960x540).

This resolution was under consideration by the ATSC in the late 1980s to become the standard HDTV format, because it is exactly 4 times the width and 3 times the height of VGA, which has the same number of lines as NTSC signals at the SDTV 4:3 aspect ratio. Pragmatic technical constraints made them choose the now well-known 16:9 formats with twice (HD) and thrice (FHD) the VGA width instead.
graphics  wiki  monitor  standards 
april 2016 by mikael
Avid® High-Resolution Workflows Guide
An. ARRI 3K image is 2880 x 1620 pixels, whereas a RED 3K image is 3072 x 1728 pixels.
video  standards 
april 2016 by mikael
What does the 5k, 4k, 3k...etc. mean?????
And, to throw a total monkey wrench into the understanding: video formats are referred to by their VERTICAL (y-axis) resolution, whereas the 2K/3K/4K digital cinema formats are referred to by their HORIZONTAL resolution.

So, in video, you'll hear about 480i, 480p, 720p, 1080p, and 1080i. Those correspond, of course, to:
480i/480p: 720 x 480
720p: 1280x720
1080p/i: 1920 x 1080

But, in the digital cinema notations of 2K/3K/4K, it's talking about the horizontal (x-axis) res. So:

2K = 2048 wide (2 x 1024, 1024 = 1K) so it's 2048 x 1152.
3K = 3072 wide (3 x 1024) for 3072 x 1728
4K = 4096 wide (4 x 1024) for 4096 x 2304.

Using these numbers, we can see that 2K is only slightly bigger than 1080P, even though "2K" (2048) sounds like a lot more than 1080, right? It's because the 2K refers to the horizontal, whereas the 1080P refers to the vertical. But once you do the math, you find it's 2048x1152, vs. 1920x1080. So 2K is about 14% larger than 1080P.

On the other hand, people sometimes think that 4K is twice the res of 2K, when in fact it's 4x as much. 4K is twice as many horizontal pixels, and it's also twice as many vertical, so you could fit four full 2K frames inside one 4K frame.
video  standards  forum-posts 
april 2016 by mikael
A strongly defined, highly compatible specification of Markdown.
standards  markdown 
march 2016 by mikael RFC 7763 - The text/markdown Media Type
This document registers the text/markdown media type for use with Markdown, a family of plain-text formatting syntaxes that optionally can be converted to formal markup languages such as HTML.
standards  markdown  html 
march 2016 by mikael
This document specifies a Hypertext Transfer Protocol (HTTP) status code for use when resource access is denied as a consequence of legal demands.
standards  http  www 
december 2015 by mikael A pause to refresh the Web?
After years of racing, the Web may finally be slowing to breathe.
internet  standards  history 
december 2015 by mikael Next Unit of Computing
Next Unit of Computing (NUC) is a small form factor PC designed by Intel. Its first generation is based on the Sandy Bridge Celeron CPU. Its second generation CPU is based on the Ivy Bridge Core i3 and Core i5 processors. Its third generation is based on the Haswell architecture. Its motherboard measures 4 × 4 inches (10.16 × 10.16 cm).
standards  hardware  computers  wiki 
november 2015 by mikael Understanding Openness
The choice between closed versus open innovation is not always simple.
open-source  standards  articles 
october 2015 by mikael Webmention
Webmention is a simple way to notify any URL when you link to it on your site. From the receiver's perspective, it's a way to request notifications when other sites link to it. Webmention is a modern update to Pingback, using only HTTP and x-www-urlencoded content rather than XMLRPC requests. Webmention supersedes Pingback.
blogging  standards  http  webdev 
october 2015 by mikael Meet Google’s “Eddystone”—a flexible, open source iBeacon fighter
Google's cross-platform standard combines the best of iBeacon and The Physical Web.
bluetooth  google  open-source  standards 
july 2015 by mikael
TIFF/A Standard Initiative launched!
The versatility of the TIFF format has made it very attractive for memory institutions for long term archival of their digital images. However, since the TIFF format offers such a great flexibility, it is not guaranteed that in the future a standard TIFF reader will be able to read some TIFF images.The limitations of the baseline TIFF are too severe for many applications in digital archiving. In this sense, TIFF/A is not a new file format but a version of the TIFF format that is suitable for long term archival.
digital-imaging  preservation  fileformats  photography  standards 
july 2015 by mikael
Youtube Ditches Flash, and it Hardly Matters: Meet the New Boss, Same as the Old Boss
In spring 2013, the World Wide Web Consortium (W3C) abandoned its long-term role as the guardian of the open Web, and threw its support at the highest level behind EME, an attempt to standardize Flash-style locks on browsers. They did this after the big three commercial browser companies revealed that they had engaged in closed-door meetings with Netflix to create back-doors in their browsers to lock users out of their own computers while streaming video. The W3C agreed to work to standardize browsers that treat their owners as untrusted adversaries and take steps to countermand user-actions (like saving videos).
blog-posts  flash  video  standards  html5  webdev 
february 2015 by mikael
You either get it or you don’t
[...] there is a major issue with DNG: As far as I know, DNGs usually (i.e. by default) store the data as it came from the sensor. That means the application that reads the files needs to support the native format of the sensor pixel pattern. It is quite likely that some software vendors in the distant future will choose not to implement support for exotic historic sensors that do not use a conventional Bayer pattern (like Sigma’s Foveon, the rumored Fuji X-Trans and the like). While it is indeed possible to activate demosaicing in the conversion options inside the Adobe products, that will obviously no longer store the original sensor data and makes it impossible to benefit from improved future demosaicing algorithms unless you accept the storage overhead of embedding the original RAW file. Plus, most people don’t even know the demosaicing option is there, let alone what it does, and it will probably result in larger files as well since the red and blue channel hast to contain the additional interpolated values. Don’t get me wrong, DNG is great and I wish it was more universally supported, but it is quite dangerous in that it tricks people into thinking all DNG files are 100% future-proof without restrictions.
dng  forum-posts  standards  preservation  raw  photography  digital-imaging  blog-posts 
november 2014 by mikael E.123
E.123 is standards-based recommendation by the International Telecommunications Union sector ITU-T, and is entitled Notation for national and international telephone numbers, e-mail addresses and Web addresses. It provides guidelines for the presentation of telephone numbers, email addresses, and web addresses in print, on letterheads, and similar purposes.
wiki  telephony  standards 
august 2014 by mikael
As Mobile Roars Ahead, It’s Time To Finally Admit The Web Is Dying
While discussions about tech bubbles have been heated, few commentators seem to be targeting their invective at the real underlying bubble: the World Wide Web itself is crumbling. Like any outmoded technology, the Web is rapidly losing users as it fails to adapt to disruption from mobile apps and continues to perform poorly – despite incredible optimization efforts – due to a bloated software architecture built of hacks on top of hacks. It had an unbelievable 25-year run, but I think it’s time to admit that the product is reaching its last throes. [...] mobile web apps have little hope of ever competing since mobile hardware is fundamentally resource-constrained, and JavaScript’s interpretive nature can never be optimized to match native performance.
history  internet  standards  blog-posts  netcritique 
may 2014 by mikael Lowering Your Standards: DRM and the Future of the W3C
On Monday, the W3C announced that its Director, Tim Berners-Lee, had determined that the "playback of protected content" was in scope for the W3C HTML Working Group's new charter, overriding EFF's formal objection against its inclusion. This means the controversial Encrypted Media Extension (EME) proposal will continue to be part of that group's work product, and may be included in the W3C's HTML5.1 standard. If EME goes through to become part of a W3C recommendation, you can expect to hear DRM vendors, DRM-locked content providers like Netflix, and browser makers like Microsoft, Opera, and Google stating that they can now offer W3C standards compliant "content protection" for Web video. [ ]
standards  html  html5  drm 
october 2013 by mikael
How Google pulled the plug on the public Jabber Network
I know I'm late but I still can't see this part of the deal showing up... So, it's no news that Google first disallowed new s2s connections, then started their own protocol, which has no s2s connections at all. With that, the largest node of the public Jabber network went down, incorporating the largest share of its users. They're pointing to spam.
jabber  xmpp  google  standards 
july 2013 by mikael Flexplay
Flexplay is a trademark for a DVD-compatible optical video disc format with a time-limited (usually 48-hour) playback time. They are often described as "self-destructing" although the disc merely turns black and does not physically disintegrate. The same technology was used by Disney's Buena Vista Home Entertainment under the name ez-D. The Flexplay concept was invented by two professors, Yannis Bakos and Erik Brynjolfsson, who founded Flexplay Technologies in 1999. The technology was developed by Flexplay Technologies and General Electric.
dvd  standards  wiki 
july 2013 by mikael Google Abandons Open Standards for Instant Messaging
In the midst of the major press blitz surrounding its annual I/O Conference, Google dropped some unfortunate news about its instant messaging plans. In several places around the web, the company is replacing the existing "Talk" platform with a new one called "Hangouts" that sharply diminishes support for the open messaging protocol known as XMPP (or sometimes informally Jabber), and also removes the option to disable the archiving of all chat communications. These changes represent a switch from open protocols to proprietary ones, and a clear step backward for many users. [ ]
standards  xmpp  blog-posts  google 
may 2013 by mikael
« earlier      
per page:    204080120160

Copy this bookmark:

to read