3,117 karma · joined November 11, 2009
I built and operate SlickDNS (https://www.slickdns.com), a DNS hosting service.
I co-founded YouPatch (https://www.youpatch.com), the world's most popular pixel quilt pattern generation service.
Location: Adelaide, Australia (via Canada, California and Melbourne)
Website: wombatsoftware.com
Email: john@wombatsoftware.com
Web backend: Django
DNS/Web API backends: Go, Flask, Tornado
DB: Postgres, SQLite
Cache: Redis
Frontend: htmx (via jQuery, Backbone.js and Vue.js)
Marketing site: Cloudflare Pages
Hosting: Mix of Heroku, Linode and Fly
Backups: Backupsy
Dev: Linux and Docker Compose
Payments: Stripe and PayPal (reluctantly)
I'm definitely ambivalent about this move from Namecheap. I'd be curious to know whether this decision was made unilaterally by Namecheap's US-based CEO or whether it was pushed by their Ukrainian employees.
While Namecheap are understandably angry about the Russian invasion of Ukraine, I'm skeptical that cutting of their Russian customers will do anything to help Ukraine. If anything it will only cause Namecheap to lose revenue and thereby force them to cut jobs in their Ukrainian based workforce. Long term it also creates reputational risk for Namecheap as a company that makes decisions based on short-term political factors.
Requiring Namecheap's Russian customers to transfer their domains to another registrar in the next week is also easier said than done given the financial sanctions against Russia will probably make it much more difficult for them to pay for transferring the domains to a different registrar. I think it's safe to say that the average tech-savvy Russian is probably more anti-Putin than the average Russian as they have to jump through hoops and mess w/ VPNs to access western based services such as Twitter etc. So in practice this move might lead to de facto censorship and loss of income for their Russian customers, many of whom would be against the war.
Definitely agree that the brain is quite malleable. I think it was an unexpected result at just how malleable the brain is in adult implant recipients.
FWIW I participated in a post-op research study and IIRC was told that more electrodes wouldn't necessarily improve the quality of the sound. I think what's much more important is the algorithms in the over-the-ear processor. (I have the Nucleus 7: https://www.cochlear.com/au/en/home/products-and-accessories...)
Here's the reference song and timestamp: https://www.youtube.com/watch?v=GI1cGPfL-Bw&t=130s Without my implant I can barely hear anything the drummer does for the next 10 seconds, so it must be > 1500 Hz, which is the upper limit of my "good" ear. With my cochlear alone (i.e., plugging my "good" left ear) I can hear all the frequencies, but the song sounds "tinny" and lacks clarity. With both ears I'm not consciously missing much in terms of clarity if I had normal hearing, so the brain does a very good job at creating almost normal sound from my two very imperfect ears.
However, please note that outcomes for cochlear implant recipients vary. I've been told that my result is unusually good given that I scored 90%+ on standard audiology speech tests post-implant.
For unknown reasons my normal hearing deteriorated rapidly in my late 30s to the point where my right ear became "profoundly deaf". (My left ear only hears up to 1500 Hz or so.) I got the implant in my right ear in late 2015 and it was literally life changing.
With the combination of the implant and the residual low frequency hearing in my left ear, in most situations my hearing is almost normal. I can understand speech fine and appreciate music.
I wonder if they'll do a follow-up article next year to report how the solar systems performed over the long Northern Ontario winter...
I recently upgraded to the Nucleus 7 processor, but it sounds identical to my previous Nucleus 6 processor. Main benefit is that the Nucleus 7 is smaller and lighter and the batteries last longer.
Keep in mind though that cochlear implants are generally a last resort since implanting them will usually remove any residual hearing you might have left. AFAIK your ear has to be "profoundly" or totally deaf before doctors will recommend implant surgery. Preferred treatment is to augment whatever hearing you still have with hearing aids before recommending implants. In my case my left ear is almost normal up to 1500Hz so it has a hearing aid that does some frequency transposition for higher frequencies. Implant is in my right ear which was almost totally deaf.
Hope that helps.
I moved my authoritative DNS name servers over to Fly a few months ago. After some initial teething issues with Fly's UDP support (which were quickly resolved) it's been smooth sailing.
The Fly UX via the flyctl command-line app is excellent, very Heroku-like. Only downside is it makes me mad when I have to fight the horrendous AWS tooling in my day job.
There were some initial teething issues as Fly only recently added UDP support, but they were very responsive to the various bugs I reported and fixed them. My name servers have been running problem free for several weeks now.
The Fly UX via the flyctl command-line app is excellent, very Heroku-like.
For apps that need anycast the only real alternative to Fly that I found is AWS Global Accelerator, but it limits you to two anycast IP addresses, it's much more expensive than Fly and you're fighting the AWS API the whole time.
Great read, but as someone else who has worked on mainframes and in Python I found this especially impressive.
Note though that I had perfectly normal hearing until my late 30s, and only have an implant in one ear. After my implant operation my brain "knew" what it should be hearing from the implant signal. This is apparently true of many adult CI recipients and the unexpected plasticity of adult brains to adjust to the CI signal is an active area of research.
I think that the typical outcomes for people who have cochlear implants when they are born deaf would be quite different to adult recipients like me who grew up with normal hearing.
I did a whole raft of audiology tests and for the speech comprehension tests in particular I scored 90%+ compared to people with normal hearing. (They're tough tests too, trying to pick out a sentence from a lot of background noise which is a worst-case scenario for hard of hearing people.)
I was told that my outcome was better than average, but I was a younger than average adult recipient given than I was in my early 40's, compared to most (in Australia at least) who are 60+.
And yes I can now distinguish all notes on a piano.
This claim is totally false for cochlear implants. I am a cochlear implant recipient and before the implant I had essentially no hearing in my right ear ("profoundly deaf"). With the implant in my right ear my hearing has been restored to 90%+ of normal hearing.
Remote: Yes
Willing to relocate: No
Technologies: Python, Django, Go
Résumé/CV: https://www.wombatsoftware.com/john-barham-resume.html
GitHub: https://github.com/jbarham/
Email: john@wombatsoftware.com
My expertise is Django web app development and high performance distributed systems in Python and/or Go. I've also done embedded and desktop app development.
I created and operate SlickDNS (https://www.slickdns.com/), a DNS hosting service, and co-founded and developed the website for YouPatch (https://www.youpatch.com/), the world's most popular pixel quilt pattern generation service.
Technologies: Python, Django, Go
Résumé/CV: https://www.wombatsoftware.com/john-barham-resume.html
GitHub: https://github.com/jbarham/
Email: john@wombatsoftware.com
My expertise is Django web app development and high performance distributed systems in Python and/or Go. I've also done embedded and desktop app development.
I created and operate SlickDNS (https://www.slickdns.com/), a DNS hosting service, and co-founded and developed the website for YouPatch (https://www.youpatch.com/), the world's most popular pixel quilt pattern generation service.
Remote: Yes
Willing to relocate: No
Technologies: Python, Django, Go
Résumé/CV: https://www.wombatsoftware.com/john-barham-resume.html
GitHub: https://github.com/jbarham/
Email: john@wombatsoftware.com
My expertise is Django web app development and high performance distributed systems in Python and/or Go. I've also done embedded and desktop app development.
I created and operate SlickDNS (https://www.slickdns.com/), a DNS hosting service, and co-founded and developed the website for YouPatch (https://www.youpatch.com/), the world's most popular pixel quilt pattern generation service.
Seoul is a concrete jungle where the vast majority of people live in tiny concrete apartments. (Literally concrete, I destroyed a lot of masonry drill bits trying to hang pictures on the concrete walls of our apartment.) Sure the subway network in Seoul is extensive but it's still not exactly a fast way to travel.
Speaking from experience the fastest way to get around Seoul is on a scooter. That's because scooters routinely jump red lights, go the wrong way down one-way streets and take shortcuts on sidewalks with impunity. Lots of fun when you're young with no kids, as I was at the time, but it doesn't scale and would never be allowed in LA.
The easiest way to cut down on vehicle traffic is to stop forcing people commuting to workplaces where they sit down at an internet connected computer that they could just as easily do at home. As the current pandemic has forced so many of us to do, which is one big upside.