I saw @freshhome‘s retweet of CityLab’s post about this. Looks exactly the thing Julie & I would go to see in London when we lived back in the UK. You can read more about this “floating building” on CityLab.
ELI is a leader in experiential-based entrepreneurship education for ordinary people, from all walks of life. It’s run by some very knowledgable folks, providing a framework for understanding and implementing an entrepreneurial mindset regardless of limitations or constraints.
I’m happy to show support for ELI by voting for them in Chase’s $3M Mission Main StreetSM Grants program. You can vote too, by visiting http://shar.es/1m0PUh.
While I’m still on the fence of moving (if I can) fully over to Known as my blogging platform, one thing that is swaying me over WordPress is their bookmarklet.
Whilst chatting, Tantek summed up my issues like this:
It’s a great add-on to your browser that takes you from the URL that you’re on and lets you share, reply, bookmark it. That’s incredibly powerful and highlights one of the huge hurdles the indieweb has to jump.
URL’s are the nervous system of the web. They connect everything together, passing information along with them and let us do a ton of the fantastic stuff we can do today. But the problem with silos like Facebook and Twitter is that a lot of people still don’t use the web interfaces. They use the apps on their devices. This makes it incredibly easy for you to create content in these silos. Problem is they don’t create or expose URLs in the same way that working on the web does. This means, as far as I can see, pretty much forsaking the use of these apps to have 100% of your content on your site.
Now this isn’t too much of an issue as a lot of social media have pretty good “responsive” sites that work well on all devices. Downside is that Chrome (and I suspect other device browsers) doesn’t let us use bookmarklets. So it’s now down to you to copy and paste all manner of URLs, content and tags onto multiple tabs on your device. Tricky at the best of times.
If we can get these bookmarklets to run on those mobile browsers, or even create OS-specific indieweb apps that sit as a background service and let you share via them such as Evernote or Instapaper does, then I can see the friction diminishing for those of a wider audience.
As I explore more ways of implementing the #indieweb, the more I come across the reasons why we need it. Content is getting increasingly difficult to reach within the silos that is Google, Twitter, Facebook, Instagram etc.
One thing that I’ve been stuck on is replies. How can we reply continually across these silos? It’s something like what we’ve been grappling with in the UX community for a while now. There we call it ‘cross-channel‘, moving between “mobile”, “web” and “physical” channels in an experience.
But keeping a continuos reply thread going, across silos, while posting on your own site breaks and falls down, at least for me, a lot of the time when you reply to a reply.
2. I answer on my blog (in this case I’m trying out Known) and link to the URL of his tweet
So the conversation is taking place across Twitter and two different blogs. On my blog I can see all of it laid out chronologically with links to each piece. But this is where everything breaks. How do I now reply to him and keep this chronology?
Well I tried adding a reply on my blog. But that doesn’t connect to anything. He won’t see it as there’s nothing to notify his blog about my reply.
And this is the same on WordPress, not just Known. The chain has now been broken.
I’ve rambled on too long, but what I’m hoping for soon is a way to keep the whole conversation going across the silos.
I love my Nexus 4 phone. It’s the first smartphone I really felt comfortable with, especially as you get the latest build direct from Google. Now there’s the rumoured specs of the Nexus 6, and we’ll see soon enough, but if those rumours are true I’ll probably be getting a Nexus 5.
You see the one thing I don’t want is a huge phone. I’ve held & tried a couple of the Samsung monsters and it’s not for me. The iPhone 6+ just seems like a “we can do that too” play. I have a tablet so I don’t need another, slightly smaller one, to carry around with me.
I’m not really bothered who builds it, and don’t get me wrong, I’d love a phone with a 13-megapixel rear camera with optical image stabilization and better battery life, but not for the sake of screen size.
So if the Nexus 6 does end up coming in just a large version, my next phone may well be the Nexus 5.
Test from WP web and Social plugin
Test using WP app & Social plugin