If you own an ASUS router and you brick it while trying to upgrade the firmware or some other action, you'll probably find documentation saying you need to run a Windows-only firmware restoration program to undo this damage.
While this is apparently the only officially supported method for restoring firmware (the alternative being to ship the router to ASUS for repair, a 10+ day process), I found with some exploring that the Windows program is likely just a glorified tftp client, and that you can restore firmware using some more standard, non-Windows tools.
I'm listing below the steps I had to use today after trying to upgrade my RT-AC66U device from firmware version 126.96.36.199.266 to 188.8.131.52.270. (The release notes for the latter indicate a fix for a "live update related bug" which is what I suspect I encountered when I first tried to do the upgrade via the web GUI.)
I'm a Mac user, but these steps should work for other non-Windows operating systems such as Linux. It hopefully goes without saying that you should follow these steps at your own risk, and I make no claims or warranty about the outcome; you could end up worse off than you are now. You could set your router on fire. You could end up killing another version of yourself living in an alternate universe. Be careful.
Continue reading Recovering ASUS router firmware without Windows
I'm intrigued by websites powered by wikis, where the content can be added, modified and deleted by the users of the site. When the people who are affected by the quality and structure of the content presented have some control over that content, you sometimes have an opportunity to get more useful, relevant, current material than if the site is maintained by a small number of content administrators.
At Summersault, our entire company intranet is a wiki. Anyone who works with us can edit the content on it, add new pages, delete stuff that they think is out of date or unhelpful, and so on - from small typo fixes to multi-page documents and images. If someone makes a change that needs to be un-done, the wiki software lets us "roll it back" or otherwise incorporate only partial changes. All of this gives us the opportunity to have an intranet "by and for" its users and our staff, instead of something built and maintained solely from a management point of view.
Wikis aren't appropriate for every kind of website, or even most kinds, but I've been thinking lately about what it would mean to have wikis power city, county and state government websites.
If these sites are primarily meant to be informational tools for use by the people who live in a given geographical region (and who are theoretically paying for the site's creation and maintenance), could governments give those people some control over the content on those resources?
Continue reading State and local government websites as wikis?
What if Facebook shut down once per day, every year?
Turn it all the way off. No one could get to it. No walls, timelines, profiles, friends, games, apps or messages.
They could call it Facebook Appreciation Day.
Some people would appreciate that Facebook was off for the day and turn their attention to other things.
Some people would appreciate how much they enjoy / like / depend on Facebook the other 364 days of the year.
Facebook's servers and employees could appreciate the day off, or maybe they could do some deep cleaning.
I'm only partly joking here:
A ritual of sabbath from something that has become so engrained in modern culture, something that many people can't imagine NOT using in some form every day, could be useful.
Having everyone who uses Facebook experience it on the same day, together, would just be amazing.
What would you do on Facebook Appreciation Day?