At the moment, I don’t need a new laptop. But should I ever need one (which will probably be someday), it will be the Framework Laptop.It really is the best and most sustainable laptop concept I’ve ever seen.Agree 100%. I’ve been looking for excuses to buy one since I’ve heard of them. Buying one would be my first non-Mac since 2003. Maybe once my 2014 mbp dies on me.
The only thing that gives me pause is the intel chips and how they compare to the M1 / AMD chips. But who knows how things will develop until then, it’s mostly a moot point.
For so long, it felt like I could only tell half the story of how we make software for the web at Basecamp. Too many of the chapters about our front-end approach were missing key pages. Sure, we had some of it out there. Turbolinks, for example, hark back to 2012, when I was inspired by Chris Wanstrath's ideas in pjax, and took them fu...I’m using Hotwire for parts of Tanzawa and I’ve enjoyed it. I really should spend the time to fully flesh it out so it’s smooth as butter everywhere.
Taken together, the collections of servers around the world that push bits to us, both for business and for our pleasure, suck up more energy than is used by a nation with a population of over 65 million. That was five years ago. You can bet that the situation is even worse in 2021.Originally linked to by Jamie. A good reminder that digital isn't green. It still takes power to run the servers, AC to cool them, and countless switches and hubs between us and any given sever for this all to work.
Gaining control of my digital footprint was a large factor in deciding to build Tanzawa, though it's been less of a focus for these past months as I add more fun features.
I'd donate to you for a theme decoupling. This is high on my list! :)I appreciate the sentiment 😃. It's not money that's preventing me, it's time.
I've been thinking about how to handle theming for Tanzawa properly. It's a big task, but not impossible. There's 2 different ways to think of theming: 1) css only changes theme support, 2) complete theme support (i.e. colors and layout). The move from css only changes wouldn't be much less work than allowing full customization.
Roughly here's what I think would be required:
- Extract all mentions of tailwind colors from templates/public (e.g. bg-negroni-700 ) and replace them with a common name – perhaps role based?
- Create a record / setting somewhere ( django-admin?) to track the active theme.
- Create a custom template loader (or other shim) that will prioritize rendering with the selected theme's public themes.
- Set Tanzawa to only include the css of the selected theme.
- Document how to make a custom theme.
Curating a set of RSS feeds is like stepping away from the agoras and finding a little café, somewhere to sit and watch from a distance, to gather the words of the other patrons. Somewhere familiar where we recognise the regulars. We might never interact beyond a nod of appreciation but, in our own way, we come to know these people or, at least, what they allow us to know.This is such a good way to think of RSS. Your RSS reader is your neighborhood coffee shop.
There really is something magical about being able to connect with people over time on the web that's separate from the noise machines.
The more I think and write about tech, the more I'm convinced that the tech doesn't really matter all that much without the correct mindset. If people are not having more interesting and profound interactions online, it is not for lack of tools. It's for lack of good intentions.For as long as there's been the internet there's been "poor" interactions online. Humans, at least part of the time, find a way to argue some of the time.
The correct mindset can help you have better interactions online. But keeping the correct mindset is quite difficult when you're up against an algorithm that optimizes to keep you enraged and anxious.
The tech absolutely matters, but only in so much as it allows unadulterated communications and community. You can't find that on the big social networks without really trying hard, but you can find that on the IndieWeb.
Then improve it.
Then write something else.
Repeat this process until you have a post.
Then post it.Exactly what I needed to hear about a post I've been drafting slowly.
Deeper interactions require time. The indie web has to be slow in order to be effective. No one is going to browse through the last 10 years of your Twitter timeline but I often end up reading 10+ years old blog posts on personal websites. That's the power of the indie web in my opinion.This was exactly what I was thinking when I wrote The Slow Web. The Indieweb is slow-food for the web.
Leon Paternoster wrote of the IndieWeb:
"I’m nearly convinced that the possibility of a decentralised network of websites talking to each other through comments sections and pingbacks (known as the web) has probably passed."
"WordPress may have all of the building blocks available but it's still not native. Plugins, themes, tweaks to get just so and working properly. Micro.blog is the closest we have but it's still a platform with its own way of doing things."I agree with Leon and Colin. There's a lot to unpack in both of these posts and I agree with all of it. But I'll chime in my 2.2 yen anyways.
The masses aren't going to adopt their own websites instead of visiting and posting on one of the large social networks. That's a feature, not a bug.
An interconnected IndieWeb the size of Twitter would present each user with the opportunity to filter and moderate the dregs of internet. That's something I'm not interested in and I doubt many on the IndieWeb today would be either.
The utility of the IndieWeb technology is that it helps us find and connect to like minded people in a decentralized matter. But still, discovery is still not solved. Without micro.blog (and perhaps the IndieWeb WebRing ) we'd all be blogging alone. And without the IndieWeb community, I'm not sure if I'd even be blogging, let alone building my own engine.
We should do everything we can to lower the barrier of entry to participate in the IndieWeb. Getting started with Wordpress is confusing because, as Colin says, it's not native. There's Wordpress Post Kinds and there's IndieWeb Post Kinds. How do they interact? Why's there two? You need to select one of a couple of microformatted themes and hope you don't break the formats if you try to customize it. Plugins conflict and break randomly (more of a general Wordpress issue). Data's stored in opaque formats (do you own the data if you can't really re-use it?).
The standards for UX have risen a lot over the past decade. Being able to participate with a single click in software that is native to the IndieWeb is table-stakes for growing the community beyond it's current size or rate. And it needs to be hosted, because most people aren't capable of or have interest in maintaining their own server.
That hooks into my dilemma with Tanzawa. My goal is to make an IndieWeb native blogging engine that's easy to use is achievable. Provide people with clean apis and transparent / logical data formats so they can use their data how they want. I can do that. I'll get there one step at a time.
But hosting? I want people to use my software, but I'm not sure I want to start a niche hosting company just to improve the UX of being on the IndieWeb.
Richard Sapper may not be a household name, but he's on the same level of greats like Dieter Rams and Jonathan Ive.Look at that Thinkpad that has the keyboard that slides together when you open it. :chef-kiss: