Category: Social Computing

Writing about social computing (digital media, social media, cyborg anthropology, online communities, et cetera).

The Republic of Newsletters, the Isle of Blogging

Continuing with the topic of the revival of blogging, emailed newsletters and small communities, Warren Ellis also recently commented:

I miss that long moment when the web seemed full of people doing the same thing, or thinking in public. It happens in the Republic Of Newsletters, now. But it was nice to have all those little radio stations broadcasting in the night.

And later stated:

I’ve seen the idea circulating for a while: come off the streams, own your own platform for your own voice and your own complete statements. It seems like a reactionary step, from some angles. But maybe that great river, The Conversation, was, like every river followed to its source, a dead end. The resurgence of the Republic Of Newsletters may be one aspect of a return to the ocean, dotted with little pirate radio stations broadcasting through the night again.

I like this metaphor (or combination of metaphors), and I agree. I’ve got a few newsletters I’m subscribed to at the moment, and I really appreciate them, particularly the ones that are a little more human, sharing a bit of the personal alongside whatever other interesting things they’re wanting to share. The same can be said for my favorite blogs, the ones I read without fail and never gloss over.

What I Use: RSS

I encourage people to subscribe to my site via RSS, when mentioning I have a site on the Facebooks and Twitters and similar. This may seem a little archaic (that is so 2008), but honestly RSS is still one of my go-to solutions for finding worthwhile things to read, watch, or experience.

One of the big reasons you don’t really see RSS mentioned anymore (despite folks actually using it often, without realizing it… looking at you, podcasts) is because Google stupidly shut down Google Reader, which was the de facto standard for reading your feeds. That killed a lot of momentum for its use.

While RSS may be limping along, it’s not dead, and a lot of sites actually do have RSS feeds, still — they just aren’t as prominently noted or advertised or linked anywhere.

Of course, even if you do decide to use RSS, there’s still the hurdle of finding an RSS reader you actually like. A lot of folks go with a web-based option (ala Google Reader), so they can read on whatever device they happen to be on. There’s also some pretty nice apps for sale (for instance, NetNewsWire), if you’re so inclined, and a lot of RSS-adjacent apps (like several web browsers, and even Apple Mail) are available as well. Personally, I use Vienna RSS, which is an open source project made for macOS. I’ve tried a bunch of other apps and methods, and this is the one I keep coming back to (there was a gap where development wasn’t really happening much, so I looked around a fair bit, but regular updates are happening again). It’s fairly fast, robust, and seems to handle a ton of feeds well. If you’re looking for a reader, I’d say it’s worth a try.

I recently went through and cleaned up my RSS feeds, getting rid of dead feeds. I just want to say, to all those bloggers who have continued to post after the blogging fad wore off: I salute you, and I’m still reading.

Link: Careful Now

Chris Coyler over at CSS-Tricks has a worthwhile response to the “Chrome is the new IE6” article I linked to earlier.

Even more concerning than browser-specific websites is seeing browsers ship non-standardized features just because they want them, not behind any vendor prefix or flag. There was a time when web developers would have got out the pitchforks if a browser was doing this, but I sense some complacency seeping in.

These days, the vibe is more centered around complaining about other browsers lack of support for things. For example, one browser ships something, we see one green dot in caniuse, and we lambast the other browsers to catch up. Instead, we might ask, was it a good idea to ship that feature yet?

Link: How to Fix Facebook

Over at Washington Monthly, Roger McNamee discusses How to Fix Facebook – Before It Fixes Us. It’s a good read, and while I may not agree with all of his suggestions, there’s some very astute observations in there:

This is important, because the internet has lost something very valuable. The early internet was designed to be decentralized. It treated all content and all content owners equally. That equality had value in society, as it kept the playing field level and encouraged new entrants. But decentralization had a cost: no one had an incentive to make internet tools easy to use. Frustrated by those tools, users embraced easy-to-use alternatives from Facebook and Google. This allowed the platforms to centralize the internet, inserting themselves between users and content, effectively imposing a tax on both sides. This is a great business model for Facebook and Google—and convenient in the short term for customers—but we are drowning in evidence that there are costs that society may not be able to afford.

I’m going to try and not keep harping on this — there’s plenty of other things to think about and talk about. I’ve been an advocate for the “indieweb” for a long time, and the current realizations over how algorithmic content curation (with no one driving, no less) through single sources might not have been such a great idea certainly help vindicate the desire for a “smaller,” more independent web. That said, I’m painfully aware of some of the gaps in the indieweb space: many tools have an incredibly high bar for getting started, and several parts of the stack frankly just aren’t getting a lot of attention (the state of web galleries is the source of a semi-annual lament). If we’re going to make a serious stab at “making the internet smaller again,” there’s still a lot for us to do.

Link: Chrome-Only Sites are a Problem

Via the Verge, Chrome is turning into the new Internet Explorer 6. I’ve been saying this for a while, and often get poo-pooed by folks who really like Chrome. Let me expand on that a bit and explain what I mean. (First, go read the article, it lays some good groundwork.)

The big response I hear is “Chrome is standards compliant, so if only Chrome is supported then the others need to catch up!” There are several browsers that claim to be standards-compliant. This is fine, and a good aspiration, but is also a bit of a half-truth: in reality browsers are partially compliant. This is because standards continue to evolve, and it takes time to implement those standards, and literally no browser is actually 100% compliant with current standards. Further, different developers are going to prioritize different parts of the standard, so while Chrome might have one feature implemented, Firefox implemented one Chrome doesn’t have, and Safari might have a different feature than either of them. Each of those features are standards compliant.

Part of the issue, and why articles like the one linked above are starting to crop up, is developers look at the new shiny in Chrome specifically, and develop around that, ignoring all other users and browsers. While there’s room for experimentation and trying out new features, putting sites into production without considering the impact on users that don’t have the features Chrome chose to implement first is bad for the web (and frankly bad for business). This isn’t specifically Chrome’s fault, mind you — the same could be said for sites using features only Firefox or Edge or Safari support, without including a fallback. However, since Chrome has the marketshare, the issue becomes much more prevalent with Chrome.

The other response that comes up is “if it works in Chrome then it’s the others that are broken.” Sometimes that’s the case, I’ll happily concede, but frankly not as often as people make it out to be. There are no shortage of bugs in all browsers, and Chrome is no exception (just in the Chromium public bug tracker, bug IDs are about to crest 800k, of which 57k are still open and active). This means you are going to work around quirks and issues in their implementation of a particular feature, even longstanding parts of CSS or HTML. This is an unfortunate but unavoidable part of web development. The issue (again) is when you only fix the issues around Chrome, or assume Chrome’s incorrect behavior is what should be expected, and leave a broken experience for all other users.

This all leads to a result of sites saying “Best used in Chrome!” or having broken functionality in other browsers without even a note, or even just blocking use with other browsers. That is what people are talking about with Chrome becoming the new IE6. It isn’t really Chrome’s fault it’s turning into IE6, but it doesn’t change the fact that as long as developers treat it as the gold standard and ignore other browsers, that’s what it will become.

(This, of course, isn’t even getting into the shift at Google to start making their newer services Chrome-ONLY, which is the next phase of IE6-ification. Some have received claims of eventual compatibility with other browsers, but others have not. While as a company they’re entitled to make those sorts of decisions, there’s nothing “standards compliant” about that sort of behavior, and earns them every bit of IE6-comparisons they receive.)

Link: The year we wanted the internet to be smaller

Over at The Verge, The year we wanted the internet to be smaller is an article discussing the state of the internet, and how we’re becoming increasingly disillusioned with broad social media (the Facebooks and Twitters and similar), reverting back to blogs, niche communities, and mailing lists. Found via Waxy.org.

Breaking Up with Social Media

Or at the very least, “taking some time apart.”

I’ve been thinking for a while about my relationship with social media (in particular Facebook and Twitter). I’ve been pretty tired of Facebook for quite some time, and have increasingly been feeling the same about Twitter — namely, they’re more outrage machines than valued information sources at this point, and frankly cost more in terms of mental and emotional wellbeing than they’re worth to me.

I’ve decided to take the month of January off from both Twitter and Facebook, entirely. After the month is up, we’ll see how I’m feeling on whether they’re reincorporated into my routine, and to what amount. In the past I’ve limited how much time I spent on FB, taking a sort of “vacation”, but it had ways of creeping back in and starting to absorb more of my time again, so this time I’m opting to remove myself from it entirely.

If you need to get ahold of me, there are lots of ways to do so (heck, slide into my DMs on either service and I’ll likely still see it). I’ll also be turning off the auto-crossposting this blog does, so if you do want to keep up with my sporadic posts, I’d suggest subscribing either via RSS or email.

Link: Stop Using Facebook and start using your browser

Via Kottke.org, an article on Mashable about how we should stop relying on Facebook (and Twitter) to feed us content, and should try and go back to actually visiting sites that interest us. Get out of the algorithm for a hot second, for a variety of reasons — not the least of which being that you’ll (hopefully) get more diversity of thought on a wider variety of topics, rather than just what Facebook’s algorithm thinks you should see.

It’s definitely not simple, nor insignificant. By choosing to be a reader of websites whose voices and ideas you’re fundamentally interested in and care about, you’re taking control.

And by doing that, you’ll chip away at the incentive publishers have to create headlines and stories weaponized for the purpose of sharing on social media. You’ll be stripping away at the motivation for websites everywhere (including this one) to make dumb hollow mindgarbage. At the same time, you’ll increase the incentive for these websites to be (if nothing else) more consistent and less desperate for your attention.

Social Media Fasting

Over at kottke.org, Jason discussed a social media fast he went on. His observations mirror my own “vacations” I’ve taken: no one really notices or cares when you take a break, even if you’re an active social media user (which I’m not), and that a lot of social media (and phone use in general) is more of as a virtual fidget-spinner than any actual need.

My own take: I took an extended break from Facebook last fall, and still haven’t really returned, though it has crept back into use in various ways. It’s still got just enough social utility that I’m not quitting it entirely, but I do plan to continue to not use it much. I probably could fully quit if I decided to — it would just take a few life adjustments and a little preparation. Interestingly, there seems to be a trend of this, folks getting fed up with the bullshit of modern social media, and making the deliberate decision to exit (and at least anecdotally, the people who’ve quit weren’t due to some weird policy change or other outrage machine, but simply because they realized it wasn’t useful to them anymore and was making them less happy).

As for other social media, well. I’ve been on Twitter for a decade, and have it pretty nailed down on what I use it for, who I follow, and what I choose to post there. That said, it still ends up going in fits and spurts: I might be on it daily for a few weeks at a time, and then not log in for a month. This is a far cry from when I was most active (circa 2008-2010), where I was on daily and actually kept up with probably 90% of my feed. The shift is due to a few factors: 1) it’s not my priority; 2) I’m not a fan of some of design changes and loss of client support; 3) the community has shifted, and seems to vacillate between being an outrage machine and a trash fire. (Don’t get me wrong, there’s still a lot of great content there, but the short form, punctuated broadcasts seem to foster emotional outbursts, miscommunication, and misunderstanding just as much as they provide short, pithy thoughts and entertainment.) The shift towards tweet storms and people just retweeting the start of a 300 tweet thread is also a cause for a lot of eyerolling and disinterest (if you are writing medium-long form text in tweets, go write a blog post and tweet the link, seriously).

I have accounts on a number of other social media sites, but don’t really touch them, whether because they were on a whim (Peach), or inertia (Flickr), they just never grabbed me. I do occasionally log in and check my ello account, though I basically never post — I just think it’s neat to see how they’ve pivoted towards being an outlet for designers and artists. I’m infrequently active on Instagram, though I use very few of their features — mostly I use it because they make it stupid simple to cross-post to other services. I have a Snapchat but don’t use it (I kind of hate the UX, and I’m not using “hate” lightly).

I think a lot about consolidating, and finding ways to self-host everything. I don’t know if it’s really “there” yet, though the tools have come a long way (the Indieweb scene is actively working to make POSSE viable and easy). There are open source, self-hostable versions of many of the services we use every day (as an example, OStatus is a protocol that replicates and even expands on a lot of the functionality of Twitter, with tools like Mastodon, GNU Social, and PostActiv all in active development, and at least ostensibly able to federate with each other). It would be a lot of initial work to get everything set up how I want, and then there’s maintenance and keeping everything secure (it’s just me, so I’m not exactly a shiny target, but that doesn’t really matter to a bot that just probes the internet for any service with one of a list of vulnerabilities unpatched), but I keep coming back to the idea. Maybe I just miss the old internet, when things weren’t so silo’d, and we felt a little less like a product and a little more like a person. Even if I didn’t worry about POSSE, and just posted in one place, I’m not sure how much that would matter — I might not get as many views, but if past experience is any indication, I’d get just as much connection. Something to think about, anyway.