2009-12-16

autophagia another form of self-destruction


6.12:
. autophagia was another way that cell's can self-destruct,
similar to how bone cells get destroyed in order to
rebuild themselves stronger .
. other ways include necrosis and apoptosis .
. after seeing that,
I wondered if silicosis could be caused by hyper-autophagia
rather than from a hyper-immune response to particulates .
. in the case of this class of nanoparticles
- ployamidoamine dendrimers (PAMAMs) -
they knew it was autophagia because a known autophagy inhibitor
prevented the cell death and counteracted nanoparticle-induced lung damage .

weightlifting hangover

6.10:
. a reason for weightlifting hangover is that
while an extreme amount of exercise can replace insulin's function,
conversely, it may tend to temporarily decrease insulin sensitivity;
ie, insulin is spurring the cells a bit,
and then after exercise spurrs the cells a lot,
insulin's kick just isn't noticed as much .
. that may be yet another reason why stretching is magic:
not only does it do more ripping an damage that requires growth,
it also involves on-going exercise -- more cellular spurring .
. conversely,
perhaps any vigorous aerobics after weightlifting
might be a replacement for stretching?
.

beware sciencelab.com backorders

proj.gov/delicious.com/sciencelab.com

6.13:

. is mywot.com alerting about sci'lab yet? no;
. mywot says some links are coming from delicious.com?
make sure delicious has same warning added for mywot.com:
. they can give good service,
but if they tell you some items are on backorder,
that's their way of hinting that you ordered illegally,
and you then have 3 days to decline the order
after which time you legally agree that they can
take as long as they want -- forever !
-- they are not a member of their local bbb
exactly for this tactic .
. compare with spectrumchemical.com first;
if they say you'll need to call rather than order online,
that's an item that will cause sciencelab.com to pull a "backorder" on you .
proj.gov/sciencelab.com/web presence/
. other reports:
. found 2 complaints ripoffreport.com:
. there is also a place to find legal help:

co.apt/pol/drug war/sci'lab:
6.3:
. thinking aloud how I got confused by changing laws
into getting trapped by sci'lab:
. when I was able to buy script-only hormones from chem'supply,
I assumed that if the script wasn't a controlled substance,
then suppliers could give it to you
-- any with a credit card -- likely not any children,
but then getting hassled by sci'lab,
and double-checking with spectrumchem'
I noticed that the scripts I could get
were simply ones under that new law
that said we could have our own hormones .
. reviewed history and reasons for drug war:
. it was a sad day when war against alcohol was lost;
I'm sure that has fueled effort to
not lose ground on other drug prohibitions .
. alcohol was difficult to stop esp'ly
because every private house can produce it
(with no visible connections but food and water);
anti-alcohol was also an obvious minority inflicting its will on the majority,
similar to when today's elite
has shipped most of our jobs overseas .

2009-12-15

tire.pump with Topeak pressure-rite adapter

6.26:
. the Topeak`pressure-rite adapter is ingenious:
it has it's own pressure sensitive valve inside;
give it a pump to engage it,
then your pump's gauge's reading will be true;
finally release your pump's engage
and the adapter quickly releases pressure on the tire's stem valve .
. now easily unscrew the adapter .
. the adapter screws on easily, and has a rock-solid connection .
. they advertise it as getting into tight places,
and providing exact pressures;
but, it's also doing well at an additional use case:
since it's the pump's pressure that sets the adapter's stem depressor,
the pump's stem depressor never gets worn out .
. also, since the adapter's stem depressor is metal,
it never gets worn out either !

trike trainer


6.24:
mis:
. at one point of gear shifting, the chain will drag on the trainer;
but that is just one gearing combination to avoid
when there are plenty of others nearby to choose from .
[7.1: later I would find I was using 20" tires on their 26" configuration ]
pos:
. the trainer should be geared high,
but also not using highest rear gears
since those will wear out easily:
the front is at largest ring, and the rear has a mid-sized ring .

6.26: trike`trainer/set for 20" tires:
. it has 2 settings for {20", 26"} tires ?
checking the current setting, I see it needs to be changed .
. it still lets you cycle with the front brakes off,
and now it might also let you cycle without the problem of
some gearing combinations causing the chain to drag on the front roller !

computer stand:
. sizing trike for table`size needs .
. trike faring won't fit under kitchen table?
after the trike`shell is built,
it may give a place to lay a board across .

6.30: reversed for fan under seat:
. if the trike`trainer is oriented so that the fan is right under the driver,
then chain will be dragging in the fan;
fortunately, the design allows for the position of the fan to be reversed !
. not only does the fan provide more cooling in this location,
but when the trike and trainer are in a cramped location,
they take up less space this way .

6.30: proj.apt`sanctum/replace easychair with trike-trainer:
. removed the south wall of the sanctum
(just a separate piece of taped-on plastic)
to temporarily pull out the table to get the chair out .
. measurements show the trike can roll under table as is,
though had to be tilted a bit for trike`rack,
and might need to be raised later to fit the trike shell .
. getting the trike in there was made easier by
clearing the way from the kitchen to the living room,
so that the trike could be rolled in normally .
. this entailed moving the kitchen table and the fridge out of the way .
. the easychair now faces the east window, sitting beside the sanctum .
. it's facing away from the couch, but there is room for 2 other chairs
that do face the couch, serving a group of 5 .


kybd holder:
. while the table must be tall eno' to allow the trike to roll under it,
this makes the keyboard too high .
. one way to bring the keyboard closer to lap
is to attach al'beams to the platform it's on,
and these would provide a tooth to grip
matching al'beam under the table,
that are hanging from strings .
. this is still a good setup for reading while cycling,
and then breaking from cycle during much keyboard use .

8.20: proj.gear/try head phones replacing buds:
. less helpful with masking trainer noise .


11.1: mis.trike/noisy trainer:
. no plugs for sore ears;
how much of tire squeel is fan transmission? 0 .

11.6: proj.trike/maint/BB[bottom bracket] noises:
. making noises that match front pedal cycle;
might be the front derailleur rubbing against the chain guard;
adjusting that may have helped,
but another knocking sound may be just one the BB (bottom bracket) again
known to be easily loosened with time,
but now not hand-loose at this time .

2009-11-27

getting organized

6.4: obj db's may be merged:

[11.27: intro:

. the fs (file system) is referring to the way that
files should be organized by folders
for the purposes of assisting in my pim (personal info' mgt) .
. the current pim is obj'oriented
meaning that info is categorized by source {self, other} .
. within the author folder is the log and the obj.db (topics database):
. the log is for placing info chronologically;
many old papers being scanned-in have no known create.date,
so they cannot be logged precisely by month or even year,
although most can still be fitted within era.folders;
however, in an earlier version of the pim,
articles without a date-stamp were simply not logged,
being placed into an obj.db instead .
. copies of important articles within the log
are then ordered by subtopic into obj.db folders .
. some subtopics correspond to physical objects,
whereas others are objects only within conceptual space .
. this pim was designed some time ago
and I'm finding that the reorganization has not fully materialized!
]
. I'm having a renewed interest in the organization of the obj.db's
because I want a space for organizing the velomobile design project .

. reviewing the obj db's
I'm wondering why I wanted the obj.db's separated into
{L(lexical, text),M(multimedia)} branches;
it is not obj-oriented and starting to complicate things
because the pictures and pdf's are not with the text of the same
subtopic .
[11.27:
. there have been many times when it's been easier to
use an application if all the files of similar type were together;
eg, when backup space is limited,
and text has a much higher priority than multimedia
then separating out multimedia makes for a compact backup of text .]

. some of the files are in the obj.db simply because they
existed before the current pim:
they are date-stamped yet not in the log .
. many emails are in the obj.db
-- even though they are datestamped --
perhaps because it seemed like too much work .
[11.27:
. later I started using mac's sparse bundles for encryption
that's easy to backup with Apple`timemachine;
obj.db now contains only log`copies or exo's (from other authors) .
]
. many of the scans are in obj.b because they are
important more as objects than as loggable events .

. the obj`L schema has been:
care/bus (gear involving wheels)
care`dev (abrasives, solvents)
care`gear (clothes, appliances)
care`maint (tools, lube) .
. that system is not working;
eg, tools can be for both maint and dev
so then you have to check 2 categories to cover a subtopic .
. I started the merge of the {L,M} forks into obj.db
for just the currently hot subjects (eg, {gear/composites, gear/trike})
.

6.5: log-based pim:


[11.28:
. the aspect.folder of my pim
is a place to copy important logged entries
into categories that are not obj-oriented:
eg, history, policy, address.book, and todo's
are folders that mix info belonging to any subtopic .
]
. like the todo file, the best way to maintain the aspect.folder
is to always keep the current working version of it in the log,
at filename: 99 {todo, pos, hist, addr ...}
-- always near the current date when ordered by name .
. unlike the monthly subj.files or folders,
the 99 files are moved from month to month rather than copied,
since they really belong in aspect.folder,
but are in log as a way to quickly access and backup
recent updates to them .
. just like the log is merged with obj.db's after being reviewed,
the log-based pim is occassionally merged with the aspect.db .

mis:

. doubting whether {tech, pos(position or policy)},
should be in the aspects.folder .
[11.28:
. whatever I was thinking, I should have shared it with clueless!
]

6.12: pos"keeping track of what's blogged:

idea#1:

. integrate blog posting with transfers to obj.db:
. to keep track of what's transfered from log to obj.db,
I started an obj/subj/todo dates.folder
whose name is updated with what range of log has been
successfully reviewed and copied
. when it says that part of a log has been merged,
you know that those notes have also been posted online .
. problem with that
is a future where you need to merge in object,
but you don't have access to the web .

idea#2:

. as usual, keep in obj`X/net.x
a mirror of what is on the site"x
. this system would be extended to blogging sites .

[11.28: idea#3

. a problem with that having to wait until
the entire month's log is reviewed and copied to obj.db
before anything can be blogged .
. the current system is to add a link to any log entries
showing the url where they were blogged .
]

6.12: pos"overview

. "(addn) was originally conceived as an abstract category
for including all the technologies I was using:
{ mac, pc, net, ... --. office equipment .
, fs --. how to organize my data portably across equipment .
, pim --. how to organize my self (viewed as office equipment) .
} .
. adds -- amer'dream doc subjects .
. addx -- amer'dream doc software systems .

. dev.{platform | lang} has been about how to develope
for a certain platform or lang .
. the syntax was dev.x
rather than x.dev;
because, the primary interest was in knowing how to control things,
and figuring out how to do this;
while secondary to that,
was an interest in what things were being controlled .

. if you're using a net service to provide subj content,
then it could be filed under subj or some meta.subj like
addn, adds, or addx .
. if the most important thing about the interaction
was that you were interacting with co.workers or talking about co's,
then it could be filed under co .
. for example, a project that put personal info on a social site,
would go under co.net/site .

. most writing actually should fall under the heading of
proj.addn/dev.co.self/subj
and if you think the matured writing is generally usable,
then sharing it would go under the heading of
proj.addn/dev.co.subj .
. this insight could mean a change in obj`X/net.site
moving all net.site.folder's to folder"addn/dev.co .
. then again,
that brings us back to the original intent of the dev.heading:
. also, dev was a subheading of addn -- cybersphere .
. from that perspective, dev.co should be reserved for
ways to influence people and make them do what you want .
. legal and psychological power moves would go under dev.co;
they are about creating systems of cooperation
where we develop interfaces that define how we agree to
serve, command, or interact .

6.12: mis"platform vs dev.platform:

. I've been inconsistent with how I'm using the categories
{ addn/dev.net
, addn/net } . not sure how to file instance of
putting info about myself on a website .
. a project that put personal info on a social site,
would go under co.net/site .
. I have mistakenly been putting this under addn/net.site;
but, that should be about the service at that site
(what's there, how to use it, mistakes made, policy about its use) .

6.18: mis"stuck again on naming system:

. adding content to my google'code site
( linking it to an active blogger site)
is tagged as dev.net .
. not sure what the obj' is? break then review pos .
. net.g'code.com is an app I'm learning how to use .
[11.28:
. adding content to a site is primarily communicationg;
it's now being tagged as co.net/g'code.com .
]

6.25: pos"co.net:

. the co.net log will no longer include delicious.com;
that info is preserved in bookmarks .

2009-09-03

I can see how they can do it

. here's how the dem's need to compromise on this health bill:
#1:
. use a grandfather clause to not fail previous promises:
current medicare will not have death panels (restricting doctor choices);
but, the currently medicare-taxed will be given this choice:
let us restrict your doctor`choices, and we'll also reduce your taxes .
#2:
. have several gov-plans with premiums that reflect
the real costs of having doctors not restricted .
. a plan that includes abortion services or consultation
must be paid for out of pocket .
. during tax time, give moralistic people a chance to pay extra taxes
to support abortions for the poor .
. and on the pro-lifer side,
give moralistic people a chance to pay extra taxes
to support unrestricted doctors for the poor .