Differences between revisions 11 and 59 (spanning 48 versions)
Revision 11 as of 2011-04-08 00:45:05
Size: 8369
Editor: SamatJain
Comment:
Revision 59 as of 2011-11-11 05:20:43
Size: 7421
Editor: SamatJain
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
= Why I use Firefox 4 Mobile, & Other Thoughts = = Backing up your Identi.ca account =
Line 4: Line 4:
Last week, [Mozilla released Firefox 4 Mobile][ff4mobilerelease] (née Fennec) for both Android and Maemo.
Line 6: Line 5:
  [ff4mobilerelease]: http://blog.mozilla.com/blog/2011/03/29/mozilla-launches-firefox-4-for-android-allowing-users-to-take-the-power-and-customization-of-firefox-everywhere-2/ To backup [my Twitter account][twitter], I use [ThinkUp][thinkup], which also happens to backup my now-dormant Facebook account. Take that, corporate data silos!
Line 8: Line 7:
I've had an Android phone since 2008 and honestly, I've never browsed the web on my phone as much as I have in the past few months when I started using Firefox 4 Mobile. It really is that much better! Here are my thoughts (focused on the Android version) on why.   [twitter]: https://www.twitter.com/SamatJain
  [thinkup]: http://thinkupapp.com/
Line 10: Line 10:
## Sync ## Because of the recent (late-2011) downtime on Identi.ca, and with the release of StatusNet 1.0, I figured now was as good a time as any to seriously setting up my own federated µ-blogging instance. With the heavy focus on federation and [autononous Web principles][franklin-street-statement], I always assumed that it'd be both easy & obvious to get data back out of Identi.ca.
Line 12: Line 12:
Firefox 4 Mobile's number 1 killer feature is [Sync][sync], which syncs tabs, logins, browser history, and bookmarks across multiple devices. The most useful of these are logins and browser history.   [franklin-street-statement]: http://autonomo.us/2008/07/franklin-street-statement/
Line 14: Line 14:
  [sync]: http://www.firefox.com/sync One word: meh.
Line 16: Line 16:
It's a *complete* pain to type user names and passwords on mobile keyboards, exacerbated personally since I practice good security and use a different password for each site on the web. Because Firefox Sync makes available on my phone all the passwords I've saved on my desktop, I never need fumble entering or remember anything anymore. Identi.ca has a [backup feature][identica-backup], but it [doesn't work quite right][identica-backup-bug]. For example, I could only fetch dents going back 4 months.
Line 18: Line 18:
I use the web quite a bit (who doesn't?), proof of which is my 15 MiB history file. Sync makes available that same browsing history, everywhere. Having your browser history available to do simple things like coloring visited links purple really makes a difference (e.g., think about looking through apartment listings on Craigslist).   [identica-backup]: http://identi.ca/main/backupaccount
  [identica-backup-bug]: http://status.net/open-source/issues/3296
Line 20: Line 21:
Having history available also powers Firefox 4 Mobile's Awesome Bar. I don't need to remember exact URLs anymore, or rely on a search engine—I can just start typing a keyword and Firefox's Awesome Bar automatically searches URLs and page titles of pages I've visited, just like it does on the desktop. }}}
Line 22: Line 23:
As a freedom-loving, free and libre open source software advocate, another bit about Sync I love is that it is an [autonomous web service][autonomous]. That is, you can [download the server-side component of Sync][syncserver] and run it yourself, should you not trust Mozilla. = Handling times on the Web in Python w/out headaches =
Line 24: Line 25:
  [autonomous]: http://autonomo.us/2008/07/franklin-street-statement/
  [syncserver]: http://hg.mozilla.org/services/minimal-server/
Describe using dateutil, W3C CDTF, etc
Line 27: Line 27:
Google has a Sync-like feature in Android 3.0 for its built-in web browser and Chrome for your desktop, but so far nothing is available for anyone stuck on older versions of Android. It also isn't autonomous—you're locked into trusting Google. {{{#!text_markdown
<abbr title="Comon Date-Time Format">CDTF</abbr> from the <abbr title="World Wide Web Consortium">W3C</abbr>
}}}
Line 29: Line 31:
## HTML5 ## = Camera at a mountain Webcam on the Web =
Line 31: Line 33:
Firefox 4 Mobile has much better HTML5 support, in the sense it supports more [New & Exciting Web Technologies][newt] (<abbr title="New & Exciting Web Technologies">NEWT</abbr>), such as CSS3, SVG, and new Javascript APIs. = Theming Apache's mod_autoindex =
Line 33: Line 35:
  [newt]: http://www.brucelawson.co.uk/2010/meet-newt-new-exciting-web-technologies/ = Doing WHATEVER URLs the right way w/ jQuery Mobile =
Line 35: Line 37:
Firefox has dropped vendor-specific prefixes for many CSS3 properties, including box-shadow, text-shadow, etc. All in all, it makes your CSS that much more clean. = A JSON proxy for the OpenStreetMap API =
Line 37: Line 39:
There's support for SVG, only [recently supported in Android 3.0][androidsvg]. [[http://gis.638310.n2.nabble.com/JSON-output-for-xapi-td6483673.html|Developer Discussion - JSON-output for xapi]]
Line 39: Line 41:
  [androidsvg]: http://code.google.com/p/android/issues/detail?id=1376 = Multiprocess in modern browsers =
Line 41: Line 43:
There's support for [notifications][notifications] via a proprietary API. Recently landed in Chrome 10, it's still missing (AFAIK?) in Android 3.0, even with 3.0's rich notifications support. == Internet Explorer ==
Line 43: Line 45:
  [notifications]: https://developer.mozilla.org/en/DOM/Displaying_notifications First multi-process browser? MSIE4?
Line 45: Line 47:
The iPhone has had multi-touch Javascript events (think pinch-to-zoom, essential for mapping widgets) since its debut, but such events are still [missing from Android][androidmt] while introduced much later. Firefox 4 Mobile has had [multi-touch support][ffmt] since last year, though, it's slightly different than the WebKit implementation and, IMHO, a bit more difficult to use without built-in gesture handling (i.e. no easy-to-use pinch Javascript event). == WebKit ==
Line 47: Line 49:
  [androidmt]: http://code.google.com/p/android/issues/detail?id=11909
  [ffmt]: http://hacks.mozilla.org/2010/08/firefox4-beta3/
 * http://trac.webkit.org/wiki/WebKit2
 * WebKit and WebKit2 from a Qt perspective: http://blog.forwardbias.in/2011/08/on-webkit-and-webkit2.html
Line 50: Line 52:
## Other stuff == Firefox ==
Line 52: Line 54:
Firefox 4 Mobile also supports add-ons. While I haven't found the need for any, there are some neat ports, like [Adblock Plus Mobile][adpmobile]. Expect the [list of add-ons][listaddons] to grow quickly.  * http://timtaubert.de/2011/08/firefox-electrolysis-101-part-1/
Line 54: Line 56:
  [adpmobile]: https://addons.mozilla.org/en-US/mobile/addon/adblock-plus/
  [listaddons]: https://addons.mozilla.org/en-US/mobile/
= Getting through Python 2's Unicode problems =
Line 57: Line 58:
When Firefox 4 Mobile was in beta, Mozilla didn't do a very good job alerting people to its high system requirements. However, on release, a [supported platforms and systems requirements page][sysreq] is first and foremost. A summary: you need a phone with at least 512 MiB RAM. The official builds require an ARMv7-generation processor (or more specifically, one that supports [ARM's Thumb instruction set][thumb]), but there are [unsupported builds for older ARMv6 devices][armv6builds] that have enough RAM (e.g. T-Mobile's MyTouch Slide, aka the HTC Espresso). Not to gloat, but Firefox 4 Mobile for Android works great on my T-Mobile G2.  * [[http://farmdev.com/talks/unicode/|Unicode In Python, Completely Demystified]]
 * Force Unicode for all strings w/ Python 2.6+: [[http://docs.python.org/py3k/howto/pyporting.html#from-future-import-unicode-literals]]
 * Instead of built-in open, use codecs.open
Line 59: Line 62:
  [sysreq]: http://www.mozilla.com/en-US/mobile/platforms/
  [thumb]: http://en.wikipedia.org/wiki/ARM_architecture#Thumb
  [armv6builds]: https://wiki.mozilla.org/Mobile/Platforms/Android#ARMv6_.28experimental.29
= Color on the Console =
Line 63: Line 64:
[Go download Firefox 4 Mobile now][download] from Mozilla's landing page if you've not done so already. You can also get it from the [Android Market][market], or, if you don't or can't use the Android Market, get the [latest Firefox 4 Mobile release from Mozilla's FTP site][ftp] instead. Also, if you're playing [Mozilla's Spark][spark], please [tag me][sparktag]! dstat
grep
htop
pydf
Line 65: Line 69:
  [download]: http://firefox.com/m/
  [market]: https://market.android.com/details?id=org.mozilla.firefox
  [ftp]: http://releases.mozilla.org/pub/mozilla.org/mobile/releases/latest/
  [spark]: https://spark.mozilla.org/
  [sparktag]: https://spark.mozilla.org/en-US/user/tamasrepus?f=t
== less ==
Line 71: Line 71:
On to other thoughts…  * [[http://www.reddit.com/r/linux/comments/knxz9/syntax_highlighting_in_less_ive_been_using_less_a/|Syntax highlighting in less - I've been using less a long time... why this has never occurred to me before today? : linux]]
Line 73: Line 73:
Firefox 4 Mobile's previous name was Fennec 2.0, a name I much prefer. But somewhere along the way, Mozilla decided to take a page from Microsoft's marketing playbook—home of atrocities like Microsoft Windows Live Mesh and [Microsoft Windows Server Base Operating Systems Management Pack for Microsoft Operations Manager 2005][longestmsname]. What makes it worse is disambiguating Firefox 4 Mobile for Android and Firefox 4 Mobile for Maemo means you're using 5 words for a product title. = Movie Review: Michael Madsen's Into Eternity =
Line 75: Line 75:
  [longestmsname]: http://blogs.msdn.com/b/jonathanh/archive/2005/08/05/what-s-the-longest-microsoft-product-name.aspx {{{#!text_markdown
With Chernobyl's 25th anniversary a few weeks past (ignored, for the most part, by Western media), and the Fukushima nuclear disaster fresh in everyone's minds, now is as good a time as any think about nuclear energy's role in our civilization. [Into Eternity][ie], a Finnish documentary released in 2010, takes a very unique look at the nuclear power industry, one not typically thought about. Rather than nuclear proliferation or the plants themselves, it focuses on the geologic storage of [spent nuclear fuel][snf] (aka <abbr title="Spent Nuclear Fuel">SNF</abbr>), in particular, [Finland's Onkalo repository][onkalo].

  [ie]: http://www.intoeternitythemovie.com/
  [snf]: http://en.wikipedia.org/wiki/Spent_nuclear_fuel
  [onkalo]: http://en.wikipedia.org/wiki/Onkalo

The movie skimps on technical details, some of which I will talk about here.

Nuclear waste can be divided into two levels: high-level and low-level. Low-level nuclear wastes include things such as clothing, plant construction materials (e.g. concrete) and machinery that have come in contact with anything nuclear.

High-level nuclear wastes include spent nuclear fuel and chemicals used to process and create nuclear fuel. The movie focuses on spent nuclear fuel, which in most nuclear power plants are things called fuel rods. Fuel rods

At the moment, the US does not have a storage plan for spent nuclear fuel. There is one geologic storage site, the [Waste Isolation Pilot Plant][wipp] in southeastern New Mexico, but the site is relatively small and destined for storing the generation I nuclear wastes of America's nuclear weapons programs, not that of commercial reactors. A larger site, [Yucca Mountain][ym], well isolated in the [Nevada Test Range][nts] (where nuclear weapons were tested for decades, and much contamination remains), was shelved in 2010 by the Obama administration, leaving America's nuclear energy industry without secure storage for its spent nuclear fuel.

  [wipp]: http://en.wikipedia.org/wiki/WIPP
  [ym]: http://en.wikipedia.org/wiki/Yucca_Mountain_nuclear_waste_repository
  [nts]: http://en.wikipedia.org/wiki/Nevada_Test_Site

Much of the topics <i>Into Eternity</i> touches, such as communicating the dangers of nuclear wastes stored at sites via markers and monuments, has similarly been discussed for the US' Waste Isolation Pilot Plant.

}}}

= Drupal 7 upgrade post-mortem =

{{{#!text_markdown
This weekend, I upgraded [Samat Says][samatsays] (this blog, in case you missed the memo) to [Drupal 7][d7].

  [samatsays]: http://blog.samat.org/
  [d7]: http://drupal.org/drupal-7.0

For my Drupal 4.6/4.7-based site, I had created my own theme, [Sands][sands]. Lack of time prevented me from porting Sands to Drupal 5 or 6, and it's unlikely it will be ported forward. I'm probably going to recreate it with one Drupal 7's many starter themes, however.

  [sands]: http://wiki.samat.org/Sands

Backing up your Identi.ca account

To backup my Twitter account, I use ThinkUp, which also happens to backup my now-dormant Facebook account. Take that, corporate data silos!

Because of the recent (late-2011) downtime on Identi.ca, and with the release of StatusNet 1.0, I figured now was as good a time as any to seriously setting up my own federated µ-blogging instance. With the heavy focus on federation and autononous Web principles, I always assumed that it'd be both easy & obvious to get data back out of Identi.ca.

One word: meh.

Identi.ca has a backup feature, but it doesn't work quite right. For example, I could only fetch dents going back 4 months.

Handling times on the Web in Python w/out headaches

Describe using dateutil, W3C CDTF, etc

CDTF from the W3C

Camera at a mountain Webcam on the Web

Theming Apache's mod_autoindex

Doing WHATEVER URLs the right way w/ jQuery Mobile

A JSON proxy for the OpenStreetMap API

Developer Discussion - JSON-output for xapi

Multiprocess in modern browsers

Internet Explorer

First multi-process browser? MSIE4?

WebKit

Firefox

Getting through Python 2's Unicode problems

Color on the Console

dstat grep htop pydf

less

Movie Review: Michael Madsen's Into Eternity

With Chernobyl's 25th anniversary a few weeks past (ignored, for the most part, by Western media), and the Fukushima nuclear disaster fresh in everyone's minds, now is as good a time as any think about nuclear energy's role in our civilization. Into Eternity, a Finnish documentary released in 2010, takes a very unique look at the nuclear power industry, one not typically thought about. Rather than nuclear proliferation or the plants themselves, it focuses on the geologic storage of spent nuclear fuel (aka SNF), in particular, Finland's Onkalo repository.

The movie skimps on technical details, some of which I will talk about here.

Nuclear waste can be divided into two levels: high-level and low-level. Low-level nuclear wastes include things such as clothing, plant construction materials (e.g. concrete) and machinery that have come in contact with anything nuclear.

High-level nuclear wastes include spent nuclear fuel and chemicals used to process and create nuclear fuel. The movie focuses on spent nuclear fuel, which in most nuclear power plants are things called fuel rods. Fuel rods

At the moment, the US does not have a storage plan for spent nuclear fuel. There is one geologic storage site, the Waste Isolation Pilot Plant in southeastern New Mexico, but the site is relatively small and destined for storing the generation I nuclear wastes of America's nuclear weapons programs, not that of commercial reactors. A larger site, Yucca Mountain, well isolated in the Nevada Test Range (where nuclear weapons were tested for decades, and much contamination remains), was shelved in 2010 by the Obama administration, leaving America's nuclear energy industry without secure storage for its spent nuclear fuel.

Much of the topics Into Eternity touches, such as communicating the dangers of nuclear wastes stored at sites via markers and monuments, has similarly been discussed for the US' Waste Isolation Pilot Plant.

Drupal 7 upgrade post-mortem

This weekend, I upgraded Samat Says (this blog, in case you missed the memo) to Drupal 7.

For my Drupal 4.6/4.7-based site, I had created my own theme, Sands. Lack of time prevented me from porting Sands to Drupal 5 or 6, and it's unlikely it will be ported forward. I'm probably going to recreate it with one Drupal 7's many starter themes, however.

Patient care in the ICU in terms of vectors and topological spaces

Biomedical Informatics, Medicine

A few weeks ago, Timothy G. Buchman gave a talk at the Columbia DBMI weekly research seminar. During the QA session, someone asked why patients in intensive care units (ICUs) were given such “extreme” treatments, often causing them to develop new health problems and complications, keeping them in the hospital. He replied with this wonderful mathematical metaphor about patient care.

You are a point in an n-dimensional space. Each dimension is some vital sign or homeostatic attribute, e.g. blood pressure, blood glucose, temperature, etc. Homeostasis is defined a polytope in that space. As you do the various things of life, your point moves within the space defined by that polytope. For example, when you eat, your blood sugar goes up, and the point moves along in the blood sugar dimension; when you take a cold shower, your body temperature is reduced, and you move along in that dimension. Young people have a large space inside their homeostatic polytope

When you leave this homeostatic polytope, you're considered “sick.” If you travel to far from it, you die.

People who enter the ICU have points that are moving away from their homeostatic polytope. Their movement away can be represented as a vector, representing how quickly their condition is deteriorating.

Treatments in the ICU represent vectors that try to point you back towards your homeostatic polytope.


SamatsWiki: DraftBlogs (last edited 2016-08-19 22:04:14 by SamatJain)