Opera RingThe reporting is a bit confusing, but it looks like the Opera web browser has been sold to a Chinese consortium. The group wanted to buy the Norwegian company outright, but the bid failed, and they fell back to an alternate deal.

According to NewsWeb:

The following business units of Opera will be included in the Transaction:

· Mobile Browser, including Operator Co-brand solutions
· Desktop Browser
· Performance and Privacy Apps
· Opera’s technology licensing business outside of Opera TV
· Opera’s 29.09% ownership in the Chinese joint venture nHorizon

The Consumer Business will be reorganized into a separate company structure. For
clarity, the following businesses are not included in the Consumer Business or
the Transaction:

· Opera Mediaworks
· Opera Apps & Games (including Bemobi)
· Opera TV

It’s a shame to see Opera broken up and dispersed…but in a way, that already happened years ago. When they switched to WebKit in 2013, they lost what made them unique and (IMO) valuable: They’d been a solid third-party (well, fourth-party) that helped keep the web from collapsing back into a monopoly. Within a year the community portal was gone as well.

Since then I’ve only bothered with the desktop browser occasionally when I need to test multiple sessions at once. I used to keep a copy on my phone for times when I was stuck on a slow connection, but these days the cell network in my area is a lot faster. When it gets slow, it’s also unstable, so compression doesn’t help much.

VivaldiI think I will check out Vivaldi again, though. Founded in part by Opera co-founder Jon von Tetzchner, it started as a new home for the Opera community. When I first checked out their browser, it was a really rough preview, but it’s at 1.2 now. While it’s using Blink as the rendering engine, they seem to be trying to innovate through the UI instead, with a heavy emphasis on customizing everything. Update: Yeah, Vivaldi’s become a solid option.

(via Slashdot)

After way too long, I finally upgraded the processor on my desktop. I’d held off because that always involves upgrading the motherboard, which is major surgery on the computer, and with a small child who wants to grab everything, that wasn’t really a good idea. Replacing phones and tablets, and replacing the Windows box, sure, those are relatively simple. Nothing fragile is open for several hours, and we use them all the time.

But I’ve recently done some small maintenance with him around and he’s been able to keep his hands to himself and just look, and I’ve trusted him to help with a few things like clipping in the panels on unused drive bays and opening/closing the main case screws.

I ordered a processor/mobo/memory combo from NewEgg, and it showed up on Saturday. I waited until Sunday morning to get started, knowing that these things always take more time than you expect (and typically at least one extra trip to the computer store). No surprise, it turned out I needed a new power supply for the new motherboard. In an odd echo of the last time,* I drove out to Fry’s and found one with the connectors and wattage I needed, with a rebate on it, then picked up some takeout for lunch.

The kiddo was able to leave the half-disassembled box alone while I was out. Things were strained by the time I was finished around four, and he had a full-on meltdown at the grocery store later, but I got the new hardware installed.

It’s amazing how much smoother everything runs now. I feel like I can actually use the computer again!

*I may have done another upgrade between then and the time we moved, but I only remember adding the wireless card in 2010 so that I could move the computer desk to another room and put the crib in its place. I definitely hadn’t done anything this major on the home desktop since he was born.

I finally removed the floppy disk drive from my desktop. I don’t know why it took me so long, except that it wasn’t in the way of anything. Living with a small, inquisitive child means either making hardware changes at night or keeping the work brief, and timing it so that he still has enough metaphorical spoons to keep his hands to himself.

Continue reading

Sophos reports that Facebook is testing a feature to hide new posts from your timeline so they don’t feel so permanent. Of course they’re still searchable until you actually delete them, so they’re still permanent in that sense.

What’s odd: Facebook posts don’t feel permanent to begin with, even though they effectively stick around forever.

Thinking about it, two things make an internet post feel permanent to me:

  1. Can I count on it sticking around?
  2. Can I count on finding it again?

Facebook, despite a lot of improvements over the years, is a mess. The newsfeed algorithm means you can’t just keep scrolling back. The timeline view isn’t reliably complete. Search is kind of a crap shoot. Don’t get me started on trying to find a particular old post on Twitter!

And that’s dealing with sites I can expect to stay online over time. A post on a forum, or a comment on someone else’s blog, or any social network could easily vanish in someone’s server crash or business shutdown.

If I can’t count on being able to find what I post a few years down the line, it feels like it’s temporary, even if it isn’t.

This is one reason that my Flickr portfolio feels more permanent than my Instagram photos: I can find them without resorting to third-party apps. If I want to find a particular photo on Instagram, I have to page down through my profile until I find it. On Flickr, I can find a 10-year-old photo of a fountain in seconds by searching for “fountain” and expanding the “Your photos” section of the results.

Then again, running my own site is only reliable as long as I can afford it. If something happens to me, and I can’t pay for hosting anymore, what then? I figure I’d simplify things down to where I could get a basic, super-cheap hosting plan. Make the blogs read-only so they can be served statically from a shared server or S3 bucket, or move them to WordPress.com, or just be willing to let them crash under load. But what if I’m incapacitated and can’t convert it? Or just plain not there anymore? If I really want to keep my corner of the web up “permanently,” I’m going to have to make a plan ahead of time.

Otherwise my carefully preserved photos, articles, and extended musings will be toast…leaving behind as context only broken links and all my supposedly (but not really) ephemeral offhand remarks on Twitter and Facebook.

It’s weird to look back on all the posts I made agonizing about whether or not to buy a netbook.

It was never anything I would have used on a regular basis, and I knew that (which is why I never went through with buying one). It would have been something I used on trips, mainly conventions, and only to overcome the shortcomings of late 2000s smartphones.

Mainly: photos and typing.

Photo by VIA Gallery from Hsintien, Taiwan - HP 2133 Mini-Note PC (front view compare with pencil) uploaded by Kozuch, CC BY 2.0
Photo by VIA Gallery from Hsintien, Taiwan – HP 2133 Mini-Note PC (front view compare with pencil) uploaded by Kozuch, CC BY 2.0
Back then, I always carried another camera to get the “good” pictures, because phone cameras were still crappy. So if I wanted to post something online, I had to get it off the camera, onto a computer, and then upload it. Today’s smartphone cameras and apps are so much more capable that they mostly solve the photo issues.

It’s still painfully slow to type anything of length on a phone, but tablets have emerged since then and are a lot easier to type on. Hybrids like the Surface Pro and add-on keyboards make it even easier.

Touchscreens have solved the crappy trackpad problem netbooks had.

Faster phones and cell networks, and a more mobile-friendly web, have made a lot more things possible directly on the phone.

Netbooks, meanwhile, are pretty much forgotten, at least in the form they existed in at the time. Chromebooks are doing OK, at least in schools, but they aren’t quite the same thing. You’d think “netbook” would refer to something more like the network-dependent Chromebook, but it typically referred to the tiny form factor of a mini-laptop.

Looking back at the Tori Amos signing that I mentioned in the series’ first post: These days I probably would have taken the pictures directly on my phone and posted to Instagram within minutes. As for the blogging, I might have powered through on the phone and added the pictures directly, or I might have done so on the tablet and added the pictures that would already have synced from the phone over WiFi.

I wouldn’t carry a laptop of any size around the convention floor, that’s for sure. And I probably wouldn’t bring one on a short trip at all unless I was planning on working during the evenings.

I finally moved the public side of this blog over to HTTPS last weekend. Traditionally I’ve preferred to put public info on HTTP and save HTTPS for things that need it – passwords, payment info, login tokens, anything that should be kept private — but between the movement to protect more and more of the web from eavesdropping and the fact that tools are making it harder to split content between open and encrypted sides (the WordPress app sometimes gets confused when you run the admin over HTTPS but keep the public blog on HTTP), I decided it was time.

The last sticking point was putting HTTPS on my CDN, and I’d decided to try getting Let’s Encrypt and CloudFront working together over the weekend. Then Amazon announced their Certificate Manager for AWS, which took care of the hard part. All I had to do was request and approve the (domain-validated) certificate, then attach it. Done!

Downside: Because I opted for the SNI option on the CDN, rather than pay the premium to get unique IP addresses on every CloudFront endpoint, the images won’t work with older browsers like IE6. (Server Name Indication is a way to put more than one HTTPS site on the same IP address.)

On the other hand, the cert I have on the site itself is SHA2-signed (as it should be, now that SHA-1 is no longer sufficient), so it wouldn’t work with older browsers even if I turned off the CDN and kept the images on the server.

It’s the first time I’ve actually broken the ability of older browsers to see any of my personal sites. I’ve broken layouts, sure, but not completely cut them off. In general I’d rather not, but I think I’m OK with it this time because

  1. SHA1 really does have to go, SHA2 is well-established, and it’s not like I’m providing downloads of modern browsers or a critical communications forum for people who are stuck with ancient hardware/software because that’s all that’s available to them.
  2. SNI has been around for TEN YEARS.

And as it turns out, DreamHost’s ModSecurity rules block IE6 to begin with, so the whole site’s already broken in that browser.

So I guess next time I redesign I can finally drop any IE6 workarounds. :shrug:

I woke up to ten or so first-time comments* in the moderation queue at Speed Force this morning. As I started reading them I was briefly confused: they were well-written, specific comments about comic books….that had nothing to do with the posts they were attached to. Complaining about Bendis’ writing on an interview with Paul Ryan (the artist, not the politician). Gushing about an Ultra-Humanite figure on a review of a Flash comic. Tips on finding exclusive Aquaman figures on a Flash TV episode review.

Then I felt strangely nostalgic, because I hadn’t seen this sort of spam in a long time.

As near as I can tell, the spammer finds a related site, scrapes comments from it, and pastes them into the target site. To what end I’m not sure, because the comments all linked to Facebook profiles. Most comment spam seems to be about link generation to prop up a spamvertised site in search rankings. But sure enough, when I searched for phrases from the spammy comments, I found the originals on a Daredevil fan blog, an action figure site, an artist’s blog, and so on.

I’ve got to give the spammer a little credit for two things:

  1. Finding actual comics-related blogs to scrape comments from.
  2. Inserting typos to make it harder to match. Though Google’s pretty good at fixing those.

In the end, though…

*plonk!*

*I have WordPress set up so that first-time commenters always go through moderation, while returning commenters are allowed through unless they trips a filter.

»All pages site-wide with this tag