Welcome to planet Fintlewoodlewix - SmashingConf Oxford 2014

This document contains a list of 22 URLs for various web2.0 services and applications including file sharing sites like kiko.com and send-large-files.com, online office suites like zoho.com and thinkfree.com, diagramming tools like gliffy.com, social bookmarking sites like mystrands.com, and more general web2.0 sites like netvibes.com and mobzz.com.

The original vision for TB-L was to create a collaborative medium and place where people could meet, read and write together. However, with the rise of the internet and technologies like searchability, persistence of information, replicability of content, and invisible audiences, the ability to control how information is shared and with whom has diminished greatly over time. As these technologies developed, users lost more and more control over the data they put online and how it could potentially be accessed and used by others.

Sabemos o quão importante é representar com as imagens aquilo que queremos compartilhar, então reuni 12 bancos de imagens free que podem ser utilizados em diversos projetos na Web. #ClickLuna www.kaboompics.com www.unsplash.com www.freerangestock.com www.isorepublic.com www.raumrot.com www.picography.co www.publicdomainarchive.com www.pexels.com www.freepik.com www.foodiesfeed.com www.4freephotos.com www.imcreator.com

We're past the honeymoon period of HTML5 by now. The excitement of inflated promises is over and we start wondering what to do – use HTML5 or just build an iOS app instead? In this talk Chris Heilmann of Mozilla will show what HTML5 is really good for, what its problems are, what causes a lot of these problems and how new operating systems like Firefox OS work and conversion tools like PhoneGap work around these issues. You'll see the now of HTML5 and what is cooking in the kitchens of browser makers and standards bodies that will developing and deploying apps cross-platform much easier than it is now. We have a lot of tools at our disposal, we simply need to dare to use them.

This document discusses social media and its impact on society. It begins with an introduction to a course on digital citizenship and protecting well-being in the digital age. It then presents several short videos and links related to the history and rise of technology and social media. It poses several poll questions about technology ownership and usage. It quotes a teenager discussing how their social media usage changed over time. Finally, it shares a statistic about growth on Instagram. The overarching topic is how social media has become integrated into modern society.

A flipbook for FILM260 (Digital Media Studies) at Queen's University. By Catherine Owsik. May 2013.

This document provides a step-by-step guide for becoming a graphic design expert using Canva in 90 minutes. It outlines the 5 steps to get started which include signing up for a free Canva account, choosing a template, editing the template by adding images, text, and other elements. The document also provides tips on using images from Canva or other free sites like Pixabay, and formatting text. With patience, experimentation and drag and drop, one can create professional looking designs using Canva.

- Does the word "Mosaic" conjure up fond memories of pages upon pages with grey background and blue links, rather than fancy glass pictures? - Did you use AOL diskettes as coasters? - Did you last touch JavaScript back when

The web has become saturated with design trends that follow the same patterns, and use the same design systems. If we were to leverage ideas from other mediums, the web would be a much more interesting place.

Dégooglisons Internet (Ungooglize Internet) is a project by Framasoft, a non-profit promoting free and open source software and culture. Degooglisons Internet has 3 goals: * Rise the level of awareness among mainstream Internet users about the risks of excessive centralization of the web by corporate giants such as Google, Apple, Facebook, Amazon and Microsoft. * Provide a proof of concept that free and open source software is a sustainable solution to the problem. Framasoft launched a campaign to provide and promote free and libre alternatives, respecting data and user privacy. For every service mass-collecting user data (eg. Facebook,Google Docs, Dropbox, Skype, etc.), Framasoft is offering free/libre, ethic and decentralized alternatives. * Spread knowledge, practice and services with tutorials and federate alternate independent hosting services. The more free/libre services will be provided, the more decentralized the internet will remain.

The document provides instructions for logging into a Bloomberg Terminal located at the Robert W. Woodruff Library at AUC. It states that the user name must be "bloomberg" and the password and log on location must also be "bloomberg". It instructs to double click the Bloomberg icon, enter the login credentials at the sign in screen, and then confirms that the user is logged into the Bloomberg Terminal upon completion.

Best Job Search Websites in World Best Job Search Websites in World Best Job Search Websites in World, Best Job Search Websites, Job Search Websites, Best Job

CRU Blogging--Advice for Ministry Bloggers this is from a webinar hosted on October 12, 2009 on using a blog effectively for ministry.

This document discusses whether the reader is a "digital native" who is comfortable with technology like iPods. It includes images and asks the reader questions about being a "digital native" and their favorite digital device, with Michael Jackson referenced throughout.

The document summarizes key points from a presentation given by Chris Heilmann at SmashingConf NYC in June 2015. Some of the main ideas discussed include: - The web has become overly complex with too many frameworks, tools, libraries, and content being produced. - As developers, we tend to build for ourselves and our peers rather than for general users, focusing more on recognition than usability. - The assumptions we have about users' knowledge and engagement levels with technology often do not match reality. - Despite advances, the modern web experience can be cluttered, slow, and difficult for many users. - There are opportunities to simplify and improve the web by removing unnecessary code and technologies.

My closing talk for this year's Fronteers conference in Amsterdam, the Netherlands about just how cool it is to be someone who builds things for the web.

The document summarizes key points from a talk given by Chris Heilmann at SmashingConf NYC in June 2015. Some of the main ideas discussed include: how developers have created an echo chamber focused on tools and recognition rather than users; how the web has become cluttered and broken despite new technologies; and how detecting users through user-agent sniffing and reliance on non-standard features has perpetuated problems. The talk calls for a renewed focus on users, standards compliance, and cleaning up old and unnecessary code to improve the web.

The document discusses how developers have become disconnected from users as technology has advanced. It argues that developers should focus on building interfaces that are simple, human-centered, and empower users rather than just improving tools. Machine learning and AI can be used to build helpful interfaces, but developers must focus on the human experience and inclusive design. The talk aims to inspire developers to use their skills to improve people's lives rather than just profit or automation.

This document discusses issues with modern web development and provides suggestions for improvement. It notes that web pages have become bloated with dependencies, frameworks hinder interoperability, and desktop and mobile solutions are disappointing. Conferences provide conflicting messages about tools and standards. JavaScript intolerance causes problems, and browsers spend resources fixing developers' code. The document advocates focusing on usability over new features, embracing limitations, using existing browser capabilities, and fixing baseline issues rather than trying to control everything. It suggests the next users will not demand native-like experiences and that growth is happening outside tech hubs with different rules. The document encourages contributing to the web in many ways and embracing imperfections.

This document discusses progressing web development and applications. It talks about some common criticisms of the web, including that browsers differ too much and the web is too flexible. However, it argues that browser differences allow for innovation and flexibility is one of the web's strengths. It promotes an approach of focusing on capabilities rather than browsers. The document also discusses progressing technologies like service workers and progressive web apps that can make applications work offline and feel more like native apps while still being web-based. It concludes by arguing the web is not going away and is a great platform to build upon.

In the last year or so things changed drastically. Everybody uses an iPhone6, is connected 24/7 at high-speed without data caps, is healthy, has shiny teeth and loves spending money on your products. All you need to do is constantly innovate and you'll be a major success. The term for this is "the modern web". Another word for it is nonsense. There is a web people want and there is one that people use. We should start thinking about upgrading the one people use and stop chasing our own tail trying to mimick other environments.

A talk about future technologies of the web, and how our time is equally well spent cleaning up the web of now.

A presentation questioning why we keep fighting the same fights as web developers when there are a lot more important things to worry about.

The document discusses the evolution of the web from progressive web apps to native mobile apps and back again to progressive web apps. It notes that early mobile web faced issues like small screens, poor connectivity and unreliable browsers, leading to the rise of native apps. However, app distribution issues like slow updates and the "walled garden" approach of app stores have led to a renewed interest in progressive web apps that work offline but do not require app stores, allowing for more open distribution like the original web.

As developers, we always have to battle people and media overselling what we do. Just because we use things other people don't understand doesn't mean we use magic. Yet if you look at any "near future" video of cool technology everything is incredibly smooth. We, on the other hand, seem to be far too excited about things breaking and trying to find solutions for any problem - no matter how unlikely it is to happen. In this keynote Chris Heilmann wants to remind us about what we have, what we can do and just how amazing our work really is. And what we can do to keep it like that.

A quick reminder of how we make it too complex for ourselves as web developers these days, and how changes in the browser world mean mainly one thing: build to standards.

The document discusses several topics related to social networks and web technologies: 1. It discusses various conferences focused on social networking, web applications, and related topics. 2. It covers issues around social network portability and how users can access their social graph data across different services. Both lightweight and heavyweight approaches are mentioned. 3. Trends in the roles of users, designers, and developers are discussed in the context of changes in technologies and how people use the web. The impact on the culture of education and startups is also summarized.

The document discusses how digital networks are unlocking passion and enabling deeper relationships and value creation. It addresses how to discover, nurture and amplify passion through connection and by providing access to information and people. It also discusses how barriers to access are eroding, the new scarcities in a world of increased access, and how to provide premium experiences and context to command attention in this environment. Key questions addressed include how to help customers accomplish their goals, be highly relevant and present on their channels, and journey further into niche areas.

This document is an introduction to "The Little Red Book", which discusses using old technologies like printed books to share new ideas. It contains definitions for internet terminology like "ad space", "AJAX", "applet", and "avatar". The definitions are intended to explain technical terms in an accessible way using everyday language and examples. The overall document serves as a glossary for internet-related words and concepts.

A talk about innovation and impostor syndrome. A talk about the next web that's coming and the technology we have, but forgot.

The way people experience the web will see dramatic change in response to new tools, expectations and constraints in the coming years. This session will highlight some major forces shaping our medium and lead us in thinking about how we should expect to evolve what we deliver in light of changes in hardware, mobile, wearable, data, and software among others. We will look to parallels in architecture, aircraft and other technologies and suggest future trends that will evolve. Attendees will gain a better understanding of the changing nature of our environment and the impact of all of these forces and is appropriate for anyone working in this field who is interested in what the future may bring. Attendees will leave ready to make their own decisions about how best to embrace these forces in their own work.

KEYNOTE: Nullcon 2021 - Security Research and Disclosure - The Unauthorized Biography How did we get here? What is my opportunity? How can I seize it?

It is easy to think what we have as developers is what people use and that lead us to make the web bloated.

The document discusses issues with the current state of the web including slow page load times and large file sizes. It suggests that overuse of third-party scripts and advertisements have degraded the user experience. The author calls for simplifying web pages, prioritizing users over technology, and increased collaboration between browser makers and web developers to rebuild the web. Simplifying code, updating outdated libraries, and assuming unknown browsers are capable instead of limited can help improve the web.

We are obsessed with coding and creating automated workflows and optimisations. And yet our final products aren't making it easy for people to use them. Somewhere, we lost empathy for our end users and other developers. Maybe it is time to change that. Here are some ideas.

This document discusses ways to improve how web developers learn best practices through browser and tooling improvements. It suggests that linting and inline insights directly in code editors could help prevent mistakes by flagging issues early. A tool called webhint is highlighted that provides one-stop checking and explanations of hints related to performance, accessibility, security and more. The document advocates for customizing hints based on a project's specific needs and environment. Overall, it argues for accelerated learning through context-sensitive, customizable best practices integrated into development workflows.

This document discusses privilege in the context of social media and the internet. It acknowledges privileges like internet access, the ability to communicate, and supportive online communities. It warns that machine learning and algorithms risk creating echo chambers and guided messaging if they are not kept in check by human curation. The document advocates taking back the web for decent, thinking and loving humans and using privileges to help others gain access to learning, communication, and communities.

JavaScript is a bigger world than a language these days. Time to take stock and find happiness in that world.

This document discusses artificial intelligence and how it can help humans. It covers that AI is not new, having originated in the 1950s, and is now more advanced due to increased computing power. It also discusses how AI utilizes pattern recognition and machine learning. The document then covers several applications of AI including computer vision, natural language processing, sentiment analysis, speech recognition/conversion and moderation. It notes both the benefits of AI in automating tasks and preventing errors, as well as the responsibilities of ensuring transparency and allowing people to opt-in to algorithms.

The document discusses concerns about the perception and realities of coding careers. It expresses worry that coding is seen solely as a way to get a job rather than as a means of problem-solving. While coding can provide fulfilling work, the document cautions that the need for coders may decrease with automation and that the role may evolve from coding to engineering. It suggests a future where machines assist with repetitive coding tasks and people focus on delivering maintainable, secure products with attention to privacy and user experience.

PWA are a hot topic and it is important to understand that they are a different approach to apps than the traditional way of packaging something and letting the user install it. In this keynote you'll see some of the differences.

This document discusses privilege in technology and perceptions of technology workers. It acknowledges the privileges that tech workers enjoy, such as access to resources and high demand in the job market. However, it also notes problems like peer pressure, lack of work-life balance, and imposter syndrome. Both tech workers and the public have skewed perceptions of each other - tech workers feel others do not appreciate or understand their work, while the public sees tech workers as antisocial or caring only about profit. The document encourages taking small steps to improve the situation, such as being kind to oneself, considering others, sharing knowledge, and focusing on quality over quantity of work.

The document provides five ways for JavaScript developers to be happier: 1) Concentrate on the present and focus on creating rather than worrying about the past or future. 2) Limit distractions by streamlining your development environment and using an editor like VS Code that consolidates features. 3) Make mistakes less likely by using linters to catch errors as you code. 4) Get to know your tools better like debuggers to avoid console.log and gain insights to build better solutions. 5) Give back to others in the community by being helpful rather than causing drama.

The document discusses progressive web apps (PWAs) and provides suggestions for improving them. It notes that while PWAs aim to have engaging, fast, integrated, and reliable experiences like native apps, they still have room for improvement in areas like speed, integration, and reliability. It emphasizes that PWAs should adhere to web best practices and provide actually useful experiences rather than just focusing on technical features. The document encourages helping the PWA effort by providing feedback, using and contributing to tools, keeping messaging up-to-date, and promoting high-quality examples.

Chris Heilmann gave a talk at BTConf in Munich in January 2018 about machine learning, automation worries, and coding. He discussed how coding used to refer to creative programming within technical limitations but now often refers to programming for work. He addressed common worries about new technologies and dependencies, and argued that abstractions are not inherently bad and help more people build products together through consensus. The talk focused on using tools to be more productive and enabling rather than seeing them as dangers, and creating solutions for users rather than fighting old approaches.