“Computers are too complex” my doctor said this to me yesterday. I didn't think much of it till this morning. I think I'm going to find another doctor.Typically in computing things start out simple, yet over time more and more things are added which it wasn't designed to do making it more complex. Then years later someone comes along, redesigns it, making it simpler, and easier to use.
It would be interesting to find out from your doctor what parts of computers he believes is too complex.
You mean you have a humble doctor? I wouldn't get rid of him, I'd treat him like gold!
I mean, would you ever stop and pretend to know everything about the krebs/citric acid cycle in conversation? ..or just say it's too complicated? Seriously, computers do tip the "too complicated to bother" for most people (that's not to say they can't learn if they want to, it's just to say most prioritize other things) and people who are all "ha ha I bought an ipad, I'm suuuuch a geek!" are just fronting. It's ok to not know everything about everything and people who know that instead of taking every opportunity to pretend like they do are the very people you want to be your doctor, plumber, waiter, etc. because they're focusing on what they're good at. You're lucky :)
Dylan likes this.
- With no power comes no responsibility.Show all 5 repliesIf people thought less about having power over others and more about setting a good example, the world would be a better place.
I believe those with greater freedom have to be more responsible than those who don't possess the same freedom.
- Congratulations to Pete, who managed to produce out third-most viewed article in the last seven days among all the World Cup news.
Pete Daniels shared this.
O.o#^This Happened: Woman Breaks Both Her Legs During Threesome in Car
For the love of all that is holy, stop fucking in automobiles!
Pete Daniels likes this.
Pete Daniels shared this.
- Pete's email has me thinking about "creative" robots and the copyrightability of their works.
Just for context: I've heard that robots are being used for sports reports. I'm 100% in favor of robots but not in favor of anything approaching true AI...at least not yet.
However, robots "writing" reports would be great if we knew the reports were written by robots and thus not under copyright. I don't think we have any way of knowing that though, so the robots aren't contributing to the commons.
Pete Daniels likes this.
Pete Daniels shared this.Show all 10 repliesI think the TWiL argument treating robots like animals: http://law.musicmanumit.com/2013/06/9-monkey-art-and-copyright-intellectual.html
I'm not sure you can give agency to robots. If software was the problem of the creator, than warranty disclaimers wouldn't work.
I'd be happy to be pointed to case law or a section of Title 17 that suggests what you are saying with any certainty.
Feeling Old Again
It's hard not to feel old when the retrospective report on Casey Kasem's death on the NBC Nightly News tonight started with:
Before music was digitized and downloaded on demand,
It's a subtle thing, but when you consider about the fact that anyone under the age of 30 probably doesn't have a single clear memory for the Time Before Napster (aka the Long, Long Ago), of course they have to say that.
… And it does make me feel old.
… And I also feel old merely because I watch the NBC Nightly News. I'm sure its typical age demographic shifts mostly upward from me. I suspect that most people born after 1991 or so don't even know NBC, CBS, and ABC have nightly news programs at all.Show all 8 repliesWhen I were a teenager I used to go to places called "record stores" after school to shop for (usually) 33 1/3 rpm vinyl record albums. I occasionally bought cassette tapes but was appalled by their poor quality.
I didn't purchase a CD until I were 23, though by that time vinyl records were mostly dead and CDs were ubiquitous.
I think my parents had one album of 78s (album in the archaic sense). They had lots of LPs too as did my elder siblings. My father had some cassettes of The Carpenters for some reason, which I thought about when listening to the famous FaiF "Karen Carpenter" episode, wherein @bkuhn described The Carpenters as "easy listening", which I think is a questionable genre description.
making mix tapes off the radio
I remember that too .. I think its a feature of an entire generation! (and taking the cover off to get to the bias trimpot and having a non-magnetised screwdriver handy for head azimuth adjustment was a must :-))
apart from that, when I left school the other big thing was the 12" single.
CD players were just coming onto the market but they were still pricey and not many had them yet.
- I really have not explored #Mississippi yet, primarily because of the work schedule.
Every time a local resident finds out I'm from out of state, they say the same thing: "Give it a chance. It isn't the same as it was fifty years ago." The fact that they feel the need to immediately tell me this makes me hesitant to go out unnecessarily.
- redshift can be configured to turn up the red more than it does by default. This avoids any white glare, because only the red pixels are on. For example, I run it with -t 5800:1000 -g 0.9
Only disadvantage of this is certain foreground/background pairs will appear as red on red or black on black.
News flash: Public/private partnerships don't work.
flex-plan.com gives the (tomcat?) default 500 error page.
Redirects are apparently hard and will require a new grant/explicit line item from the government contract, because, business model.
Pete Daniels likes this.
Weirdness in T60 Thinkpad Volume keys
In my mission to make sure I write up technical detais of any random issue that takes me longer than 15 minutes to solve, I've written a blog post about resolving an issue with volume keys on a Thinkpad T60.
Hey, thanks! This worked on my ThinkPad X60 as well.
I have a T61 and an X60, both running GNOME 3 under Ubuntu GNU/Linux, and I had the same issue -- the volume keys worked as expected on the T61, but not on the X60 (same issue as you described, I think -- though I didn't do a detailed analysis with xev and the like). Your solution for the T60 works for the X60 as well, it seems (I haven't reboot the machine yet either).
That's been bugging me for months. Thanks!
- Bradley Kuhn recently me asked me what the plan is with pump.io. He pointed out that there a number of UI bugs with the Web interface, as well as some essential federation issues (for example, how comments don't get distributed to all followers).
As most of you know, I've taken another full-time job, and pump.io has become a side project for me. A beloved side project that matters to me very much, but it's no longer what I spend all day working on.
When I do have time to work on it, much of my work is system administration. E14N has some money still, but there's not any new money coming in, so I have to use what's left sparingly. Using cheaper resources more wisely with more efficient software is a big investment for me right now -- it means that we can keep these services running almost indefinitely.
The good news there is that this has mostly been a success. From a peak in 2011, the cost of running the servers E14N uses has gone down two orders of magnitude. That's a huge step.
That also means that I find myself with more time to work on the core software and supporting sites.
Another big step is the incipient Social Web Working Group which I will be co-chairing. The group has a mandate to build a social data format, a client-to-server API, and a server-to-server protocol for social interaction. It's likely that the resulting suite of standards will bear a close resemblance to the current pump.io API, and I definitely intend to track it.
Bradley asked me, "What's the plan?" and I'm going to take this opportunity to sketch out a plan for where pump.io is going.
- Over the next week, I'm going to take the current state of pump.io and release it as version 0.3 and start the 0.4 development. Yes, I realize there are still bugs outstanding, but it's probably time to just stamp it and move on.
- In the same time, I'm going to deal with the long list of pull requests and open issues with pump.io. The PRs will either get a reply, get pulled to 0.4, or closed. The issues will get put into milestones for 0.4 or "maybe later" or "probably never".
- I've been working on the Facebook bridge for pump.io, and I'd like to get that operational before starting any other development work.
- My next project will be a Github bridge to share data about commits, issues, and pull requests to accounts on pump.io. I think that will help with some visibility of the development activity.
- I'm going to convert the pump.io codebase to CoffeeScript. This may sound radical, but it's mostly a mechanical process with js2coffee. CoffeeScript is a mostly syntactical transformation of JS, and it's really a lot more fun to write. All the regular NodeJS libraries and modules work fine with CoffeeScript, and the installation process will stay the same (no coffee binary needed).
- I'm going to upgrade the pump.io dependencies -- Backbone, Bootstrap, Express, etc. A lot has changed in the last few years, and I'd like to keep up better.
- Start knocking down bugs in the core software -- mostly concentrating on distributed conversations and the notifications in the Web UI, but seeing if there are others that can get fixed.
- I'd like to release an 0.4 version by September of this year.
I appreciate everyone's attention to pump.io. I know that you've all put a lot of work into this platform, and I really appreciate it. I especially love that there are so many new clients and tools for the platform -- having that kind of ecosystem has been especially important to me.
And everyone who's put their online social presence into an E14N server -- believe me, it's appreciated. You are literally the lifeblood of this network, and making things work right for you is why I do this.Show all 19 replies
>> howcanuhavemyusername (Metal Biker):
“What about OStatus bridge with the other federated social platforms?”
There is a bridge to StatusNet/GnuSocial. What would be great would be if GnuSocial added a Pump plugin on their side to have transparent federation, not bridges.
[ Reposting this comment to make sure it appears publicly ]
Evan, first of all, in case you didn't see my later comment after my post, I want to link to it here. My main point there is that we need to start thinking about pump.io as a community-oriented volunteer project now, and that's a good thing. Everything will take longer, but such projects have a long history of producing much better, longer-lasting results that VC-funded stuff.
I don't have a lot to give, but I'd happily give $5 toward a Kickstarter. But, if you're talking about what I think you're talking about, I suggest you team up with the FreedomBox people and see if they have money left.
I've been critical of FreedomBox because it took on too much. It tried to make a home server for all network services everyone could imagine where 'hard reboot' was the only sysadmin task. But, pump.io actually seeks to be what the FreedomBox said it would be on the social networking part, so you should at least talk with them about helping you with fundraising.
Related to that, I encourage pump.io to apply to be a member project of Conservancy. (Of cousre, as a member of our Evaluation Committee, you'd have to recuse yourself of course from discussion about joining post-applying.) That would bring to bear the (albeit) meager resources of Conservancy to help with your fundraising and other efforts. We may be even able to get you gratis VPS's for pump.io if you don't have them already
As you know from your work on the Eval Committee, no one eval committee member can assure acceptance of an application, but I would strongly support your application and I expect other eval members would to. The downsite for you is it would mean E14N letting go of the project, which may be just too painful to consider after all the work you put into.
Evan, thnk you again for all you'e done: since we started autonomo.us, I truly think you are the only one who did more than "just talk" about what freedom for network services should be. You have worked for almost a decade now non-stop to make it happen. While we don't have a solution, you put a lot of great code out there and our community learned a lot. True federated social networking is one of the hardest technical problems our community has ever tried to solve, so any progress forward is impressive.
Thank you, Evan, for all you have done. You are a true hero of software freedom. (And I'll be nominating you for the FSF Award for the Advancement of Free Software, BTW, and I hope others will too. :)