Skip to main content

Home/ @Publish/ Group items tagged Web Development

Rss Feed Group items tagged

Pedro Gonçalves

20 top web design and development trends for 2013 | Feature | .net magazine - 0 views

  • “If you’re designing a website and not thinking about the user experience on mobile and tablets, you’re going to disappoint a lot of users,” he warns. Designer Tom Muller thinks big brands getting on board will lead to agencies “increasingly using responsive design as a major selling point, persuading clients to future-proof digital marketing communications”. When doing so, Clearleft founder Andy Budd believes we’ll see an end to retrofitting RWD into existing products: “Instead, RWD will be a key element for a company’s mobile strategy, baked in from the start.” Because of this, Budd predicts standalone mobile-optimised sites and native apps will go into decline: “This will reduce the number of mobile apps that are website clones, and force companies to design unique mobile experiences targeted towards specific customers and behaviours.”
  • During 2012, the average site size crept over a megabyte, which designer/developer Mat Marquis describes as “pretty gross”, but he reckons there’s a trend towards “leaner, faster, more efficient websites” – and hopes it sticks. He adds: “Loosing a gigantic website onto the web isn’t much different from building a site that requires browser ‘X’: it’s putting the onus on users, for our own sakes.”
  • Designer and writer Stephanie Rieger reckons that although people now know “web design isn’t print,” they’ve “forgotten it’s actually software, and performance is therefore a critical UX factor”.
  • ...6 more annotations...
  • Bluegg studio manager Rob Mills reckons 2013 will see a “further step in the direction of storytelling and personality on the web, achieved through a greater focus on content and an increase in the use of illustration”.
  • Apps remain big business, but some publishers continue to edge to HTML5. Redweb head of innovation David Burton reckons a larger backlash is brewing: “The gold rush is over, and there’s unrest in that apps aren’t all they promised to be. We now live in a just-in-time culture, where Google can answer anything at the drop of a hat, and we no longer need to know the answers. The app model works the old way. Do we need apps for every brand we interact with? Will we even have iPhones in five years’ time? Who knows? But one thing is certain – the internet will remain, and the clever money is on making web apps that work across all platforms, present and future.”
  • Designer/developer Dan Eden says that with “more companies focussing web efforts on mobile,” designers will feel the pressure to brush up on the subject, to the point that in 2013, “designing for desktop might be considered legacy support”. Rowley agrees projects will increasingly “focus on mobile-first regarding design, form, usability and functionality”, and Chris Lake, Econsultancy director of product development, explains this will impact on interaction, with web designers exploring natural user interface design (fingers, not cursors) and utilising gestures.
  • We’re increasingly comfortable using products that aren’t finished. It’s become acceptable to launch a work-in-progress, which is faster to market and simpler to build – and then improve it, add features, and keep people’s attention. It’s a model that works well, especially during recession. As we head into 2013, this beta model of releasing and publicly tweaking could become increasingly prevalent.“
  • “The detail matters, and can be the difference between a good experience and a great experience.” Garrett adds we’ll also see a “trend towards not looking CMS-like”, through clients demanding a site run a specific CMS but that it not look like other sites using the system.
  • “SWD is a methodology for designing websites capable of being displayed on screens with both low and high pixel densities. Like RWD, it’s a collection of ideas, techniques, and web standards.”
Pedro Gonçalves

Web Developers Brace For the MacBook Pro's Retina Display - 0 views

  • The new laptop, which Apple unveiled last week, already has Web designers and developers trying to figure out how they're going to create sites and Web apps that look good on the new machine without leaving the rest of the Web's population behind.
  • One of the key advantages of these high-resolution displays is their crisp, highly readable rendering of text. That particular buck stops with the Web browsers, which are much more varied on the desktop than on mobile devices. Naturally, Safari supports retina-friendly text, but Chrome is still working on it, and other browsers will presumably follow.
  • For image-heavy sites, swapping out higher-resolution images can have a substantial impact on page load, which in turn affects user experience and even search engine rankings. 
  • ...2 more annotations...
  • To deal with this issue, Web developers can borrow from some of their tried-and-true methods. For years, websites have used browser detection to deliver different CSS stylesheets to different browsers. A similar approach is used to craft responsive designs - when sites load different layouts depending on the device being used to view it. Likewise, this sort of tactic could be used to handle graphics
  • That's exactly what they're doing at O3 World, an interactive agency based in Philadelphia. To account for different screen resolutions, they've begun creating multiple sets of graphics, which are delivered dynamically, depending on the user's screen resolution.
Pedro Gonçalves

Snow Fail: Do Readers Really Prefer Parallax Web Design? | Co.Design | business + design - 0 views

  • The parallax style has excited web developers and inspired any number of hype lists. It's also triggered a backlash among critics who feel its bells-and-whistles approach detracts from actual content. Pitchfork creative director Michael Renaud recently told the Atlantic Wire he expects people to "tire" of the trend within a year or two.
  • the parallax site was only superior in one sense--fun. None of the other survey measures indicated a significant difference in user experience between the two sites. Parallax didn't even edge the standard site in questions about visual appeal (although participants did think it looked slightly more "professional"). Frederick also discovered one critical disadvantage of parallax: test participants who suffered from motion sickness found the style disorienting.
  • Sobering as this first careful study of parallax might be to web designers, Frederick still believes it's a fad with a future. He cautions developers to think more carefully about the context in which parallax is applied. Text-heavy sites that employ parallax scrolling seem more likely to disorient users, he says. Sites that emphasize visual elements--images, infographics, or data visualizations, in particular--are probably a better fit for the style.
Pedro Gonçalves

How Website Speed Actually Impacts Search Ranking - Moz - 0 views

  • in 2010, Google did something very different. Google announced website speed would begin having an impact on search ranking. Now, the speed at which someone could view the content from a search result would be a factor.
  • Google's Matt Cutts announced that slow-performing mobile sites would soon be penalized in search rankings as well.
  • While Google has been intentionally unclear in which particular aspect of page speed impacts search ranking, they have been quite clear in stating that content relevancy remains king.
  • ...13 more annotations...
  • When people say"page load time" for a website, they usually mean one of two measurements: "document complete" time or "fully rendered" time. Think of document complete time as the time it takes a page to load before you can start clicking or entering data. All the content might not be there yet, but you can interact with the page. Think of fully rendered time as the time it takes to download and display all images, advertisements, and analytic trackers. This is all the "background stuff" you see fill in as you're scrolling through a page.
  • Since Google was not clear on what page load time means, we examined both the effects of both document complete and fully rendered on search rankings. However our biggest surprise came from the lack of correlation of two key metrics! We expected, if anything, these 2 metrics would clearly have an impact on search ranking. However, our data shows no clear correlation between document complete or fully rendered times with search engine rank, as you can see in the graph below:
  • With no correlation between search ranking and what is traditionally thought of a "page load time" we expanded our search to the Time to First Byte (TTFB). This metric captures how long it takes your browser to receive the first byte of a response from a web server when you request a particular URL. In other words, this metric encompasses the network latency of sending your request to the web server, the amount of time the web server spent processing and generating a response, and amount of time it took to send the first byte of that response back from the server to your browser.
  • The TTFB result was surprising in a clear correlation was identified between decreasing search rank and increasing time to first byte. Sites that have a lower TTFB respond faster and have higher search result rankings than slower sites with a higher TTFB. Of all the data we captured, the TTFB metric had the strongest correlation effect, implying a high likelihood of some level of influence on search ranking.
  • The surprising result here was with the the median size of each web page, in bytes, relative to the search ranking position. By "page size," we mean all of the bytes that were downloaded to fully render the page, including all the images, ads, third party widgets, and fonts. When we graphed the median page size for each search rank position, we found a counterintuitive correlation of decreasing page size to decreasing page rank, with an anomalous dip in the top 3 ranks.
  • We suspect over time, though, that page rendering time will also factor into rankings due to the high indication of the importance of user experience.
  • our data shows there is a correlation between lower time-to-first-byte (TTFB) metrics and higher search engine rankings. Websites with servers and back-end infrastructure that could quickly deliver web content had a higher search ranking than those that were slower. This means that, despite conventional wisdom, it is back-end website performance and not front-end website performance that directly impacts a website's search engine ranking.
  • Our data shows there is no correlation between "page load time" (either document complete or fully rendered) and ranking on Google's search results page. This is true not only for generic searches (one or two keywords) but also for "long tail" searches (4 or 5 keywords) as well. We did not see websites with faster page load times ranking higher than websites with slower page load times in any consistent fashion. If Page Load Time is a factor in search engine rankings, it is being lost in the noise of other factors. We had hoped to see some correlation especially for generic one- or two-word queries. Our belief was that the high competition for generic searches would make smaller factors like page speed stand out more.
  • TTFB is affected by 3 factors: The network latency between a visitor and the server. How heavily loaded the web server is. How quickly the website's back end can generate the content.
  • Websites can lower network latency by utilizing Content Distribution Networks (CDNs). CDNs can quickly deliver content to all visitors, often regardless of geographic location, in a greatly accelerated manner.
  • Do these websites rank highly because they have better back-end infrastructure than other sites? Or do they need better back-end infrastructure to handle the load of ALREADY being ranked higher? While both are possible, our conclusion is that sites with faster back ends receive a higher rank, and not the other way around.
  • The back-end performance of a website directly impacts search engine ranking. The back end includes the web servers, their network connections, the use of CDNs, and the back-end application and database servers. Website owners should explore ways to improve their TTFB. This includes using CDNs, optimizing your application code, optimizing database queries, and ensuring you have fast and responsive web servers.
  • Fast websites have more visitors, who visit more pages, for longer period of times, who come back more often, and are more likely to purchase products or click ads. In short, faster websites make users happy, and happy users promote your website through linking and sharing. All of these things contribute to improving search engine rankings.
Pedro Gonçalves

Survey: Tablet Owners Prefer Browsers to Native Apps - 0 views

  • Among tablet owners, at least, reading on the mobile Web is preferable to using native apps, according to a recent survey from the Online Publishers Association. 
  • Forty-one percent of tablet-bound readers prefer reading on the Web, compared to the 30% who would rather launch a standalone app from a specific publisher. Aggregated news-reading apps like Flipboard and Zite rated surprisingly low on the list. 
  • Last month, Jason Pontin, editor of MIT Technology Review, wrote a widely read takedown of native apps, citing Apple's steep revenue share and the technical and design challenges associated with producing such apps.  "But the real problem with apps was more profound," Pontin wrote. "When people read news and features on electronic media, they expect stories to possess the linky-ness of the Web, but stories in apps didn’t really link."
  • ...4 more annotations...
  • Apple's infamous 30% subscription revenue cut prompted the Financial Times to abandon its iOS apps and instead focus on developing a cross-platform Web app written in HTML5. 
  • Evidently, the native-app approach is not working for readers, either - at least, not as well as the Web. FT has seen an increase in readership and paid subscriptions since going the HTML5 route, Grimshaw said. 
  • Native apps do offer potential advantages in terms of the reader's experience. They can be more immersive and lack some of the design limitations of the Web. Still, in far too many cases, apps created by publishers end up being little more than digital reproductions of the print product with a few bells and whistles tacked on. 
  • From the reader's standpoint, it makes sense that the Web would be a popular option for tablet reading. After all, there's much more content there, and it's intricately linked together. A digital magazine can offer a refreshing escape from the anarchy of the Web, but it's only a matter of time before readers find it necessary to return to a browser. 
Pedro Gonçalves

In 2014, The Mobile Web Will Die-And Other Mobile Predictions - ReadWrite - 0 views

  • In 2014, the mobile Web will die. That’s right, that bastardized version of the normal Web will crawl into a shallow grave and leave us all in peace. No more websites crippled with horrible “mobile.yourawfulwebsite.com” URLs. No more reading janky websites that display way too much fine print or omit crucial features when viewed on your smartphone or tablet. 
  • The mobile Web will die because the companies that make the engines it ran upon are killing their mobile browsers and replacing them with fully functional versions that run on any device. In 2014, these browsers will be updated to put the final nail in its coffin. In turn, developers will continue to build websites that can work across any screen size. Responsive design (what we do at ReadWrite to make the site look pretty everywhere) will continue to grow in 2014 as people realize that their old websites are losing them a lot of traffic from mobile devices.
  • Location-based consumer apps didn't let me down; as predicted, they remained stagnant this year. Foursquare and its kindred just are not hot anymore, even if Foursquare did just raise a funding round this week.
  • ...2 more annotations...
  • HTML5 Takes Over The Mobile Web
  • Combined with CSS and JavaScript, HTML5 is what the Web will be built on in the future. And it will just be the Web, mobile or otherwise.
Pedro Gonçalves

Standards and benchmarks - 0 views

  • The average top 1,000 web page is 1575 KB.
  • Page growth is a major reason why we keep finding, quarter after quarter, that pages are getting slower. And faster networks are not a cure-all for the challenges of page bloat.
  • According to Akamai’s most recent quarterly State of the Internet report, the global average connection speed among the top 50 internet-using countries is 3.3 Mbps — a 5.2% increase over the previous quarter. But when we’re seeing year-over-year page growth ranging from 45-50%, it’s easy to see that the gap is widening.
  • ...16 more annotations...
  • A whopping 804 KB per page is comprised of images. Three years ago, images comprised just 372 KB of a page’s total payload.
  • images are one of the single greatest impediments to front-end performance. All too often, they’re either in the wrong format or they’re uncompressed or they’re not optimized to load progressively — or all of the above.
  • Today, 38% of pages use Flash, compared to 52% in 2010. This is a good thing. Nothing against Flash, per se, but if Apple has no plans ever to support it, its obsolescence is inevitable in our increasingly mobile-first world.
  • use of custom fonts has exploded — from 1% in 2010 to 33% today.
  • But custom fonts have a dark side: they can incur a significant performance penalty.
  • These days, images on the web have to work hard. They need to be high-res enough to satisfy users with retina displays, and they also need to be small enough in size that they don’t blow your mobile data cap in one fell swoop. Responsive web design attempts to navigate this tricky terrain, with varying degrees of success.
  • Move scripts to the bottom of the page
  • Here at Strangeloop/Radware, we’ve found the opposite. Using WebPagetest, we’ve been testing the same 2,000 top Alexa-ranked ecommerce sites since 2010, and our data tells us that top ecommerce pages have gotten 22% slower in the past year.
  • This quick-and-dirty case study illustrates how network speed doesn’t directly correlate to load time. For example, download bandwidth increases 333% from DSL (1.5Mbps) to cable (5Mbps), yet the performance gain is only 12%.
  • Google published findings, based on Google Analytics data, which suggest that load times have gotten marginally faster for desktop users, and up to 30% faster for mobile users.
  • It’s better to move scripts from the top to as low in the page as possible. One reason is to enable progressive rendering, but another is to achieve greater download parallelization.
  • Make JavaScript and CSS external
  • If users on your site have multiple page views per session and many of your pages re-use the same scripts and stylesheets, you could potentially benefit from cached external files. Pages that have few (perhaps only one) page view per session may find that inlining JavaScript and CSS results in faster end-user response times.
  • Reduce DNS lookups
  • Minify JavaScript
  • In addition to minifying external scripts, you can also minify inlined script blocks. Even if you’re already gzipping your scripts, minifying them will still reduce the size by at least 5%.
Pedro Gonçalves

Channeling Anna Wintour: When Creating Branded Content, Think Like An Editor-In-Chief |... - 0 views

  • These days, developing a successful online presence requires approaching traditional digital efforts like link-building, web traffic, lead generation, and sales from a decidedly more editorial, content-rich approach: a hybrid marketing and storytelling strategy that drives customer actions by creating, documenting, distributing, and optimizing content. Some companies have created their own internal content development departments or are working with agencies to create everything from infographics to documentaries that highlight where the values, interests, and personality of brand and customer overlap. Coca Cola believes so strongly in the power of content that they are relying on this approach to help them double the size of their business by 2020.
  • While your office probably looks a lot different than a newsroom, approaching content strategy by thinking like a magazine publisher or a television producer is an effective way to approach content development and promotion. Utilizing influential voices to develop and promote content can help ensure that you meet the first requirement of securing readership and viewers--be interesting.
  • The people who already create for you: We often hear “write about what you know” because it comes easiest. Identify the talented storytellers within your own walls. Those with an intimate knowledge of company activities are primed to create impactful content, even on a tight deadline. Identify employees who are weekend filmmakers, amateur photographers, poets, and guitar players and invite them to bring these talents to the table.
  • ...3 more annotations...
  • The people who use your product or service: The voice of the customer is the most influential of all. Provide loyal consumers with an opportunity to get involved by sharing their stories. Identify digital influencers that fit your brand aesthetic and explore partnership opportunities. This approach is heavily evident in the fashion industry, where brands routinely work with fashion bloggers on everything from Twitter chats to advertising campaigns.
  • The people who support you: Why not collaborate on content development with partners or vendors? By working together, budgets become more manageable and both parties can benefit from the potential PR story. By working together, you can deliver deeper impact and cast a wider net. 
  • With more brands developing more and more content, we will naturally reach a point of over-saturation where only the very best stories will make an impact. As such, it is absolutely crucial to begin to refine and optimize current content marketing practices. Also, with the line blurring between marketing or brand managers and content developers, it’s worth noting that those best suited for positions in content marketing have a rare combination of business and marketing acumen, digital savvy, as well as journalism, public relations, film, and even creative writing. For those with this mega-mix, employment opportunities abound.
Pedro Gonçalves

Mozilla's First Peak Of Firefox OS Smartphones - ReadWrite - 0 views

  • Firefox OS is of the Web, for the Web. There is no such thing as a “native” app to Firefox OS. If an object exists as a web page, it can easily be turned into an app for Firefox OS by essentially turning it into a shortcut for the browser-based operating system to access. Instead of having to develop specifically for mobile platforms like iOS, Android or Windows Phone, the Web is the platform for Firefox OS. 
  • If you are a developer, you can build an app for Firefox OS by making some small changes to your website. You can then test the app by downloading the Aurora Marketplace onto your Android or using the browser-based Firefox OS Simulator. 
Pedro Gonçalves

Latency: The New Web Performance Bottleneck - igvita.com - 0 views

  • Upgrading your connection from 1Mbps to 2Mbps halves the PLT, but quickly thereafter we are into diminishing returns. In fact, upgrading from 5Mbps to 10Mbps results in a mere 5% improvement in page loading times!
  • For every 20ms improvement in latency, we have a linear improvement in page loading times.
  • Latency on the other hand affords no such "easy" wins. Yes, the equipment can be improved to shave off a few milliseconds, but if you want significant improvements, then the answer is simple: you need new, shorter cables to reduce the propagation delay.
  • ...6 more annotations...
  • In 2012, the average worldwide RTT to Google is still ~100ms, and ~50-60ms within the US.
  • Fiber-to-the-home services provided 17 milliseconds (ms) round-trip latency on average, while cable-based
  • That's 17-44ms of latency just to the closest measuring node within your ISP, before your packet hits any internet backbone.
  • depending on your network, quality of signal, and time of day, then just traversing your way to the internet backbone can take anywhere from 50 to 200ms+. From there, add backbone time and multiply by two: we are looking at 100-1000ms RTT range on mobile.
  • the only way to improve the situation is to move the bits closer: place your servers closers to your users, leverage CDN's, reuse connections where possible (TCP slow start), and of course, no bit is faster than no bit - send fewer bits.
  • "High speed" connectivity is not all about bandwidth, unlike what many of our ISPs would like to promote.
Pedro Gonçalves

A Primer on Responsive Design | UX Magazine - 0 views

  • According to IDC, mobile web browsing will soon eclipse desktop browsing in the U.S. and worldwide. This consumption of mobile content isn’t just happening on the go; 93% of people are now using their mobile devices to browse the Web from their homes, according to a study from Google.
  • The main development methodology behind responsive design is the use of media query functionality in CSS3. Media queries target not only certain device types (e.g., Android vs. iPhone), but actually inspect the physical characteristics of the device that renders the page. For example, the code below “asks” the device if its max horizontal resolution is equal to 480px: <link rel="stylesheet" type="text/css", media="screen and (max-device-width: 480px)", href="http://uxmag.com/iphone.css" /> If it is 480px, the device will load iphone.css. If not, the link is ignored. You can also include media queries in CSS as part of an @media rule:
  • a responsive design approach does not involve putting all of your content in front of the reader. Responsive design is about putting the right content in users’ hands according to the context of their interaction.
Pedro Gonçalves

The Numbers Are Clear: Mobile Is Taking Over The World - ReadWrite - 0 views

  • According to the ITU's "facts and figures" publication, mobile penetration rates (pdf) are now about equal to the global population - including an 89% penetration rate in "developing countries," which currently have the highest mobile growth rates.
  • nearly everyone on the planet has a mobile phone - or will have one soon enough.
  • "mobile broadband" subscriptions have grown from 278 million in 2007 - when the iPhone was first introduced - to 2.1 billion in 2013 - an annual growth rate of 40%. 
  • ...3 more annotations...
  • While larger still in the developed world, since 2010, mobile broadband adoption has grown fastest in developing countries - with rates hitting 82% in Africa and 55% in the Arab states.
  • mobile broadband is often cheaper than wired-broadband in developing countries. 
  • There are already, she noted, more than 1 billion smartphone subscribers worldwide. In addition, since the fourth quarter of 2010, smartphone and tablet sales have exceeded PC sales - and the growth trends continue to favor these newer devices. Mobile devices now account for 13% of global Internet traffic - and rising. 
Pedro Gonçalves

Forrester: Responsive Design Represents Future of Multi-Touchpoint Web Design - 0 views

  • the usage of a single URL improves site analytics and SEO performance, and sites can easily be resized for new viewing formats.
  • These include longer time required to develop individual responsive pages, the need for code workarounds to account for older legacy browsers, the need for live device testing, non-compatibility with many existing e-commerce and CMS platforms, the need for a front-end rewrite, the need for a phased development approach in large enterprises, and the extra effort required to provide unique experiences for each form factor.
Pedro Gonçalves

The Average Web Page Loads in 2.45 Seconds Google Reveals - 0 views

  • The median page load time  for desktop websites, as measured by Google Analytics, is about 2.45 seconds. That means that half the pages measured were faster than this, while the other half were slower. The mean page load is about 6.4 seconds.
  • On mobile, things are significantly slower, the median page load is about 4.4 seconds, while the mean is above 10 seconds.
Pedro Gonçalves

Official Google Webmaster Central Blog: Using site speed in web search ranking - 0 views

  • today we're including a new signal in our search ranking algorithms: site speed. Site speed reflects how quickly a website responds to web requests.
  • While site speed is a new signal, it doesn't carry as much weight as the relevance of a page. Currently, fewer than 1% of search queries are affected by the site speed signal in our implementation and the signal for site speed only applies for visitors searching in English on Google.com at this point.
Pedro Gonçalves

Google Launches Content Recommendation Engine For Mobile Sites, Powered By Google+ | Te... - 0 views

  • Google’s launch partner for this service is Forbes, but others can implement these recommendations by just adding a single line of code to their mobile sites.
  • These recommendations, Sternberg told me, are based on social recommendations on the site from your friends on Google+ (only if you are signed in, of course), what the story you just read was about, the story’s author and some of Google’s “secret sauce.”
  • The new Google+-based recommendations, interestingly, only appear once a reader slides back up on a page. This, Google’s analytics show, is a pretty good indicator that a user has finished reading a post (even if there is still more text left on the page). The recommendation widget then slides up from the bottom and one extra click brings up more relevant items for the page. The other option is to show the widget after a user scrolls past a configurable CSS entity.
  • ...1 more annotation...
  • Publishers will be able to manage the recommendations widget from their Google+ publisher accounts. From there, they can decide when exactly the widget should appear and manage a list of pages where the widget shouldn’t appear, as well as a list of pages that should never appear in recommendations.
Pedro Gonçalves

10 Developer Tips To Build A Responsive Website [Infographic] - ReadWrite - 0 views

  • “We are now looking at how we display and order content differently from screen size to screen size,” said Jeff Moriarty, Boston Globe VP of digital properties in an interview last year. “This ‘responsive content’ concept is emerging and we are starting to see in data that users want different types of content depending on their context and the device they are on. We have to now think about how content performs differently from the biggest screens to the smallest, how that content is organized and even how headlines are written from platform to platform.”
  • The first thing to think of when building a responsive site is simplicity.
  • some website builders may over-design for the desktop, making some websites fun to play with but absolutely impossible to navigate.
  • ...1 more annotation...
  • focus around content and avoid the pitfalls that certain aspects of websites can create.
Pedro Gonçalves

Make Mobile Work - 0 views

  • To guarantee the ads you pay for actually appear and look great on all screens, you should insist to your ad agencies that your advertising creative be developed in a mobile-compatible format.  And the one open, industry-standard, universal format for building mobile-ready creative is HTML5.
  • Your opportunity has never been greater. Nearly half of the US population has a mobile phone with internet access*, and one out of five pageviews on the web happen on a mobile device - a number that is growing every month.**
Pedro Gonçalves

Waiting For Prometheus | TechCrunch - 0 views

  • What matters is that they are even capable of viewing and collecting our personal, private data in this way. Why is it even possible that Verizon has this level of data to disclose? Why is it even possible that Apple can infer and cache our locations based on metadata? Why is it even possible that our emails can be skimmed for advertising opportunities? If we did not explicitly permit these things, then we have implicitly done so by choosing to go ahead and use the Internet this way either because the pros outweighed the cons. But now the cons are starting to add up.
  • we use the Internet as a sort of phantom extension of our own computers, putting things where they are accessible to us but we are not responsible for them. This was the so-called web 2.0: every personal computer and device, vastly more powerful and connected than ever before, yet acting as a thin client. Clearly, this is where we began to lose touch with reality.
  • How did we decide we were in control of the data we sent Google or Facebook? Why would we submit to such an obvious delusion? Does anyone really believe that these companies have our best interests in mind to any greater a degree than a dairy farmer and his cows? We submitted because they were the only option
  • ...6 more annotations...
  • And now, after we voluntarily put all our data in someone else’s keeping, alternately trusting and ignoring them when they told us how they can read it but wouldn’t dare, could sell it but don’t need to, might disclose it to the government but only if they have to, we’re finding out they’ve been doing all this and more the whole time. We’ve been pouring our data into the river for years and just pretending there was no one downstream.
  • Here, then, is the real question: where is the breakthrough device or software that decouples our data from the oppressive web 2.0 superstructure with no loss to functionality? One might ask: where is the Napster for privacy?
  • In a way, we want the opposite of Pandora’s box. Something that, once shut, no one can open but us: Pandora’s lockbox.
  • the direction of development in the tech sector really does seem geared towards trivialities.
  • I believe we are going to decentralize and cellularize once we realize how needlessly dependent on distant and dubiously beneficial third parties.
  • The networks that we have come to rely on were once only possible through powerful intermediaries. But what was once symbiotic has become parasitic, and those intermediaries have now outlasted their usefulness and squandered whatever trust they conned out of us when we were given the choice between tainted privilege and safe obsolescence. We did it their way. It’s time to take the highway.
1 - 20 of 43 Next › Last »
Showing 20 items per page