Checked in at MOKICHI CRAFT BEER. ビール
Checked in at MOKICHI CRAFT BEER. ビール
It’s been almost 5 years since I wrote Slow is not a Dirty Word. Reflecting on the sentiment in that article, that the best things in life take time and we needn’t rush as society tries to force us, didn’t quite go far enough. The concept of Slow should also be applied to the web.
What is the slow web? At it’s core it’s the idea that we shouldn’t fill our mind with junk and we should connect with those around us. Social media is fast food for the mind. Consuming it feels in the moment, but when you look back you’re not left with anything memorable. Moreover, because of the lack of nuance afforded by platforms, such as Twitter, it encourages behavior based on dopamine and adrenaline impulses.
For most people the slow web is best manifested as a blog. This could be a simple WordPress blog, a micro.blog, a bunch of static files on a server somewhere, anything that works for you. The important part is that you have control of your content. That you can control how and when it appears.
So much of sharing on the web these days is based on these social media platforms. So how do you get the word out about your new latest pieces in the slow web?
Knowing the number of visits to your website or article only serves to feed disappointment when one article doesn’t match your expectations. Avoiding that sense of failure will inevitability lead to a habit of not writing and only consuming.
The common methods of tracking visits can not only break your site, it also invites an invasion of privacy for your readers. Are there more privacy-minded ways to collect visitor statistics? Yes. Do you even need to collect the information in the first place? Probably not.
As technologies it’s often easy to get caught up in nuts and bolts. We’re want to build our websites to handle all the traffic the world can throw at it, so we setup database servers, build servers, deploy servers, proxy servers, and CDN caches. And for what? A trickle of traffic? All of this could be easily served off a single server, reducing operational complexity and reducing the places where things can break when you really just want to publish a blog.
Making the jump to the slow web doesn’t mean you cannot participate in the social networks, you’re just changing the terms of engagement. Instead of being the default place to collect your thoughts and ideas, it simply becomes another channel to link back to your site.
Because you no longer tweet every clever thought you have into the void, you’re able to slow down your mind, formulate your thoughts, and take back control.
Early walk with Sophie along the river. Gotta get out while it’s still cool.
Thinking it might be fun to setup a [Homebrew Website Club](https://indieweb.org/Homebrew_Website_Club) meetup in #Yokohama. Bi-weekly is too much for me right now. Anyone else interested? [@RickCogley](https://micro.blog/RickCogley) ?
Checked in at 東京入国管理局 横浜支局. Hopefully the last time at immigration for a while (7 years?). Picking up my permanent residence. Y’all’re are stuck with me. 🙂
Just saw this pop up on HN. What a nastolgia trip back to my teenage years staying up until 3am every night on irc and chatting with people from around the world and downloading all the software I could get my hands on.
Without those years I wouldn’t be where I am today.
Checked in at Starbucks Coffee 藤沢菖蒲沢店. A nice morning trip to Starbucks with the family. Leo has had his first yogurt and banana at Starbucks.
When testing in Django there’s two basic ways to make an End-to-End test for your view: use the test client to send a request to the server or create a fake request object and manually call your view function.
One isn’t “better” than the other, but I’ve come to prefer using the mock client over the fake request for the following reasons:
Another post dinner walk to watch some trains.