Directed by David Dobkin. With Owen Wilson, Vince Vaughn, Rachel McAdams, Christopher Walken. John Beckwith and Jeremy Grey, a pair of committed womanizers who sneak into weddings to take advantage of the romantic tinge in the air, find themselves at odds with one another when John meets and falls for Claire Cleary.
Something in this neighborhood about tummellers might be interesting.
To respond on your own website, enter the URL of your response which should contain a link to this post’s permalink URL. Your response will then appear (possibly after moderation) on this page. Want to update or remove your response? Update or delete your post and re-enter your post’s URL again.
If there’s the ability to hook into whether or not comments are moderated, one could simplify it slightly with an if/then statement based on the site’s moderation policy to either include, or not, the part about moderation.
In the early ’90s, Hank Rowan gave $100 million to a university in New Jersey, an act of extraordinary generosity that helped launch the greatest explosion in educational philanthropy since the days of Andrew Carnegie and the Rockefellers. But Rowan gave his money to Glassboro State University, a tiny, almost bankrupt school in South Jersey, while almost all of the philanthropists who followed his lead made their donations to elite schools such as Harvard and Yale. Why did no one follow Rowan’s example?
“My Little Hundred Million” is the third part of Revisionist History’s educational miniseries. It looks at the hidden ideologies behind giving and how a strange set of ideas has hijacked educational philanthropy.
I’m generally flabbergasted by the general idea proposed here and will have to do some more research in the near future to play around further with the ideas presented. Fortunately, in addition to the education specific idea presented, Gladwell also comes up with an additional few examples in sports by using the differences between soccer and basketball to show the subtle differences.
If he and his lab aren’t aware of the general concept, I would recommend this particular podcast and the concept of strong and weak links to César Hidalgo (t) who might actually have some troves of economics data to use to play around with some general modeling to expand upon these ideas. I’ve been generally enamored of Hidalgo’s general thesis about the overall value of links as expressed in Why Information Grows: The Evolution of Order, from Atoms to Economies1. I often think of it with relation to political economies and how the current administration seems to be (often quietly) destroying large amounts of value by breaking down a variety of economic, social, and political links within the United States as well as between our country and others.
I wonder if the additional ideas about the differences between strong and weak links might further improve these broader ideas. The general ideas behind statistical mechanics and statistics make me think that Gladwell, like Hidalgo, is certainly onto a strong idea which can be continued to be refined to improve billions of lives. I’ll have to start some literature searches now…
Here is my shameless shameful plug. More than two years ago a colleague I respect emailed and started a back and forth exchange. He strongly urged me to set up a donation campaign so I could be supported to do more tool and resource building. I gave it some thought, but then landed a good long term contract, so shelved it. Recently a few others have asked me why I am not patreon-ing, and my answer was more or less a shrug.
I’m going to use what works and is easy but focus on my content. When it doesn’t work; when it’s not easy. I’ll move on. Try another time.
Next week, we are going to relicense our open source projects React, Jest, Flow, and Immutable.js under the MIT license. We're relicensing these projects because React is the foundation of a broad ecosystem of open source software for the web, and we don't want to hold back forward progress for nontechnical reasons. This decision comes after several weeks of disappointment and uncertainty for our community. Although we still believe our BSD + Patents license provides some benefits to users of our projects, we acknowledge that we failed to decisively convince this community.
Accelerated Mobile Pages
I’ve been following most of the (Google) Accelerated Mobile Pages (AMP) discussion (most would say debate) through episodes of This Week in Google where Leo Laporte plays an interesting foil to Jeff Jarvis over the issue. The other day I came across a bookmark from Jeremy Keith entitled Need to Catch Up on the AMP Debate? which is a good catch up by CSS-Tricks. It got me thinking about creating a bookmarklet to strip out the canonical URL for AMP pages (the spec requires them to exist in markup) to make them easier to bookmark and share across social media. In addition to social sites wrapping their URLs with short URLs (which often die or disappear as the result of linkrot) or needing to physically exit platforms (I’m looking at you Facebook with your three extra life-sucking clicks meant to protect your walled garden) to properly bookmark canonical URLs for later consumption, I’ve run across several Google prepended URLs which I’d rather not share in lieu of the real ones.
Clean and Simple URLs
As an example, his canonical bookmarklet will take something ugly like
and strip it down to its most basic
so that if you want to share it, it will remove all of the tracking cruft that comes along for the ride.
Even worse offenders like
suddenly become cleaner and clearer
These examples almost remind me of the days of forwarding chain letter emails where friends couldn’t be bothered to cut out the 10 pages of all the blockquoted portions of forwards or the annoying
> > >> >>
> > >> >>
> > >> >>
nonesense before they sent it to you… The only person who gets a pass on this anymore is Grandpa, and even he’s skating on thin ice.
Remember, friends don’t let friends share ridiculous URLs…
So in that spirit, here are the three bookmarklets that you can easily drag and drop into the bookmark bar on your browser:
The code for the three follow respectively for those who prefer to view the code prior to use, or who wish to fashion their own bookmarklets:
As a bonus tip, Kevin Marks’ post briefly describes how one can use their Chrome browser on mobile to utilize these synced bookmarklets more readily.
Of course, if you want the AMP version of pages just for their clean appearance, then perhaps you may appreciate the Mercury Reader for Chrome. There isn’t a bookmarklet for it (yet?), but it’ll do roughly the same job, but without the mobile view sizing on desktop. And then while looking that link up, I also notice Mercury also has a one line of code AMP solution too, though I recommend you brush up on what AMP is, what it does, and do you really want it before adding it.
Sage makes you a better developer. Modern build tooling, live reloading, modern PHP & requirements, DRY templates with template inheritance and more.
If Underscores is a “1,000 hour head start”, Sage is a 10,000 hour head start.
Last week, a friend asked me what I thought of IndieWebify.Me, a movement intended to allow people to publish on the web without relying on the tools and storage of the giant corporations that currently control the majority of the social web. I’m the kind of person who gladly supports her local independent bookstores and farmers’ markets and food purveyors, links to IndieBound.org instead of Amazon to buy books, and admires the ideals of Open Source Software. So, I’m biased towards an independent and open experience.
IndieWebCamp, the conference devoted to strengthening the Indie Web, describes the concept of the “Indie Web” thus: “We should all own the content we’re creating, rather than just posting to third-party content silos. Publish on your own domain, and syndicate out to silos. This is the basis of the ‘Indie Web’ movement.” You’d think I’d be all over a movement aimed at bringing back more of that feeling to the modern internet.
I’d love to be, but I can’t just yet. IndieWebify’s an ideal with some pretty serious barriers to implementation; key among them, the base level of knowledge necessary for the average citizen of the internet to “Indie Webify” themselves.
Okay, clearly, I’ve got some reading to do, so I click through to learn about microformats2. The general idea isn’t too difficult for someone accustomed to writing HTML and CSS – microformats2 is a collection of standardized class names that should be applied to web content to help computers contextualize things like blog posts and comments. But this leads me to a lot of questions: Can I make my existing installation of WordPress automatically include the microformats2 markup when I write blog posts? (No.) Do I need to manually mark up my content every time I write a post? (Maybe, but that’s a long list of class names to memorize or be constantly referring to.) What is an h-card in this context? Why does it seem to represent multiple opposing standards? … and who do I know that knows how to use the existing “implementations” (which are actual code libraries to be imported and implemented, rather than more user-friendly plugins)?
Talk about jargon-filled! The amount of technobabble here depends on any users possessing a fairly high baseline of coding knowledge. Though I’m willing to click on the links to learn more, this process is nowhere near as quick and simple as joining an existing social site. And this is just step 3 of 6 – we haven’t even gotten to implementing the technology to have the federated (whoops, more technobabble) cross-site conversations that are the core that would allow for you to properly “own” and attribute all of your words to you in the context of your personal domain. Compare this to the existing Corporate Web options, like Facebook and Twitter and Google, where the only thing you need to know how to do is type the natural language words you want to share.
Even assuming you have the motivation to learn, this is not an easy proposition. Buzzfeed’s Charlie Warzel wrote of Twitter: “Ask a longtime user to tell you about their first experience with Twitter and they’ll probably lead with some variation of, “Somebody showed me how to use it…” The idea [is] that, unlike most social networks [today], you didn’t usually just discover and use Twitter – you are taught, or at least climb a fairly steep learning curve.” He then goes on to explain that this isn’t good enough anymore; that for Twitter to continue growing, they need to cater to the mainstream, and make it easier to understand. IndieWebify’s version of this is so far from that point of being accessible to the mainstream that even early adopters are barely on the horizon.
Noted tech evangelist Anil Dash has pointed out how this technical insularity burned the development of the Open Web in the past: “We took it as a self-evident and obvious goal that people would even want to participate in this medium, instead of doing the hard work necessary to make it a welcoming and rewarding place for the rest of the world. We favored obscure internecine battles about technical minutia over the hard, humbling work of engaging a billion people in connecting online, and setting the stage for the billions to come.” Right now, IndieWebify.Me feels like it’s a lot of technical minutia. Maybe that’s how it starts, but it needs to get beyond that for broader adoption.
So, if you’re one of the few who actually knows how to implement these new Open Web tools and want to see the Open Web succeed, what can you do to spread this? As I mentioned above, “somebody showed me how to use it” doesn’t scale, so new tools require accessible design and/or tutorials. The challenge is that IndieWebify.Me currently has a simplified set of instructions, but these still need to be translated further to the technical capabilities of the early adopters, not all of whom are programmers. In comparison, most new social apps and websites come with engaging tutorials that do not require learning a complex set of standards or platform protocols, or being tied to a dictionary of these terms. This is the opportunity for evangelists who are serious about the development of the Indie Web as a competitive and viable alternative: create tools that will let users add these capabilities to existing publishing platforms as easily as I installed Facebook and Twitter on my phone. Heck, WordPress itself is already Open Source. I’d love to be able to install a WordPress plugin that would IndieWebify this blog; there are some plugins out there for older microformats standards, but none fully supporting the microformats2 standard as far as I can tell. I don’t want to have to write my own CMS just to connect this blog to the Indie Web communications mechanisms.
Despite my idealism and my honest desire for an Open Web, I am concerned about IndieWebify’s ability to support this dream; it can’t be just a niche for techies. They need better outreach targeted to idealists like me whose desires outweigh their current coding capabilities, and they need to make the process itself much simpler. I hope the current model of IndieWebify is an intermediate step towards a simpler adoption pattern that will compete with Apple and Google from a usability perspective. In today’s computing world, usability has proven to be the ultimate judge of adoption as social tools such as Tumblr and WhatsApp have proven. By bridging the knowledge gap, the IndieWebify movement can go a long way towards building the next generation of the Open Web.