{"id":12,"date":"2005-08-11T20:00:43","date_gmt":"2005-08-12T03:00:43","guid":{"rendered":"http:\/\/www.boxheap.net\/ddaniels\/blog\/?p=12"},"modified":"2009-02-07T10:46:02","modified_gmt":"2009-02-07T17:46:02","slug":"20050811","status":"publish","type":"post","link":"http:\/\/www.boxheap.net\/ddaniels\/blog\/2005\/08\/20050811\/","title":{"rendered":"20050811"},"content":{"rendered":"
I was planning on writing about the problems I faced at work looking up \r\nopen source software for SMPTE 125M convertion. I kept finding SMPTE \r\ntimecode stuff (for MIDI), and other usages of the acronym SMPTE without \r\nreference to which standard was being used. The one's related to SMPTE \r\n125M are SMPTE 292M (HD-SDI), SMPTE 259M (transport of SDI and SDTI), \r\nSMPTE 305M (sometimes called SMPTE 305.2M which is SDTI), and the \r\ndocument on ancellary data. Actually SDTI really is quite different from \r\nSDI except that it goes over 259M.\r\n\r\nAnways, tonight I think I write a bit about linking and google. Yes, \r\npart of the reason that I'm writing these notes is to increase the \r\nranking that I'll get for topics that I'd like employers to see. The \r\nbigger way that I plan to get a good ranking is something I've \r\naccidentaly found before. I've put a one line signature in my e-mails to \r\nmailing lists with my resume's URL. I was hoping I could find someone on \r\nthe mailing list that might be interested, or might refer me to someone, \r\nbut instead I found that the html mailing list archives looked to be \r\nincreasing the rank of my resume. I guess this was a neat trick that can \r\nwork on google, and maybe on other search engine's that look at what's \r\nlinking to a page to give it a score.\r\n\r\nWhen I finnaly am happy with the testing scripts that I'm working on for \r\nmy tarball enhancements I'll post the results to various mailing lists \r\nthat are development forums for projects with large tarballs (e.g. the \r\nlkml, some kind of gimp mailing list, maybe some OpenOffice.org AKA OOo \r\nmailing lists...). I've got my resume's URL in the scripts themselves, \r\nbut I also plan to put my resume URL tagline in my messages.\r\n\r\nOne of my problems with my tarball enhancement postings is that I'll \r\nwant a perminate place with my domain name that I can host the scripts, \r\nbut I'm getting free hosting from a friend (thanks Dean). I don't want \r\nto generate a lot of hits on my friend's server due to the fact he \r\nlikely has better uses for his bandwith, and his ISP may not apreciate \r\nit. To prevent such a load on the link to his server (and his server), I \r\nplan to keep the scripts only on the mailing lists (archived in their \r\narchives) until interest drops down a bit. I figure a few weeks would \r\ndo, but I'll probably wait a few months.\r\n\r\nI'm really quite kean to get my scripts out the door, but I feel they're \r\nnot yet ready to stand up to the kind of critism that one gets on the \r\nLinux Kernel Mailing List (lkml). I've got a script to do the actual \r\ntarball creation, and one to show the difference between a normaly \r\ngenerated one, and the one my script makes, but I don't have something \r\nshowing the amount of time that it takes. Measuring the sorting isn't \r\neasy, as it's a series of piped commands. My shell scripting really \r\nisn't put to enough use for me to be able to quickly work around such a \r\nproblem. I've checked a few howto's like the bash one, I've asked in the \r\nbash scripting IRC channel, but I couldn't find an answer. I decided to \r\nput the commands into a separate script and time that whole script.\r\n\r\nThe other problem I've run into is testing. My home computer was taking \r\na beating compressing and untaring etc.. I decided to use my \r\nSourceForge compile farm shell to do the testing, but it's a pain to put \r\nfiles onto them. It took me a while before I figured out I had to \r\ndownload the files to my computer, and then upload them to the compile \r\nfarm's central server via sftp or scp. That's something I can do, but it \r\nreally compounds another problem I'm having. It takes me a while to make \r\nprogress on my free time coding projects, so new target files are \r\ncomming out for me to test. I want to be able to post on the lkml the \r\nresults of recompressing the latest 2.6 and 2.4 kernels. I keep \r\noptimistically downloading the latest kernels and then having real life \r\ninterupt things long enough for me to need a new version to continue. \r\nI'll stop doing that for a while though until I've actually got a draft \r\nsitting in my posponed box of an e-mail to the lkml with the scripts \r\nalready finnished and attached or actually inline I think. That's \r\nanother problem. The lkml only accepts certain posts, and Linus only \r\nusually accepts things that are in a certain format (plain text inline \r\niirc). That put me on a tangent of looking up the mailing list rules, \r\nand reading the Linux Weekly News. It'll likely do the same once I get \r\nclose enough again.\r\n\r\nSo with all my knowledge, reading, and interest in digging deep into \r\nopen source stories that I see writen\/posted, I've thought about trying \r\nto get payed to write. These notes are a bad example of my ability to \r\nwrite, but a good example of what I enjoy writing about. I've been \r\nsolicited once to write a book on Intrusion Detection from a genuine \r\npublisher, but I kind of \"fubbed\" my responce. I said that I'd be \r\ninterested in contributing, but I didn't think I'd have time to write a \r\nwhole book. I kind of regret doing that, but I think it was the right \r\nthing to say (just look at my bad record finding time to do coding). I'm \r\nhoping however that a paying gig would actually let me take some time \r\naway from real life to actually get things done (and I'm sure it would). \r\nOf course I've got to stike a balance to keep my home life happy and \r\nhealthy (fammily, friends, and my own condition). I've offered to write \r\na peice on the history of the BSD's to the Linux Weekly News, but they \r\ndidn't seem interested. They do post BSD articles, and I was pitching \r\nthat I could write one that would show the parallels between AT&T vs The \r\nRegents of Berkly (BSD) and the current SCO vs IBM etc.. It's \r\ninteresting how the history repeats itself. For good reference I'd \r\nsuggest reading the FreeBSD mailing list archives (a google search found \r\nsome good stuff).\r\n\r\nLater I might publish the research that I used as part of my pitch for \r\nmy BSD history repeats itself story. I'm also probably going to consider \r\nwritng about why I don't want to publish my unrealized ideas. I'll also \r\nprobably talk about:\r\n- Why I don't write about office politics\r\n- Why I don't write much about my personal private home life (well, \r\nmaybe I made that clear <g>)\r\n- My music idea's\r\n- My thoughts and research into a self powered home (well actually \r\ngetting power form alternate sorces like sun, wind, water...)\r\n- Thoughts on using \"image stacking\" for ameture (and hopefully \r\nprofessional) astronomy (I'll talk about this because other people have \r\nalready implemented some of this)\r\n- Some idea's for how people can generate data that's easier to compress \r\n(e.g.'s typing in lower case when there's the option, removing obvious \r\nredundant information, using the same words...)\r\n- Perhaps my ideas on natural language processing\r\n...\r\n\r\nI may eventually post my project ideas from the last fourteen years that \r\nI've been writing on paper.\r\n\r\nConsider sending me money! My resume is at \r\nhttp:\/\/www.boxheap.net\/ddaniels\/resume.html<\/a>\r\n\r\nOh, and I'll probably write about resume creation and open source tools \r\nto do it (hey, maybe lwn.net would be interested in buying that \r\narticle).\r\n\r\nOriginally from: http:\/\/www.boxheap.net\/ddaniels\/notes\/20050811.txt<\/a><\/pre>\n","protected":false},"excerpt":{"rendered":"
I was planning on writing about the problems I faced at work looking up open source software for SMPTE 125M convertion. I kept finding SMPTE timecode stuff (for MIDI), and other usages of the acronym SMPTE without reference to which standard was being used. The one’s related to SMPTE 125M are SMPTE 292M (HD-SDI), SMPTE […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":[],"categories":[1],"tags":[],"_links":{"self":[{"href":"http:\/\/www.boxheap.net\/ddaniels\/blog\/wp-json\/wp\/v2\/posts\/12"}],"collection":[{"href":"http:\/\/www.boxheap.net\/ddaniels\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/www.boxheap.net\/ddaniels\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/www.boxheap.net\/ddaniels\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/www.boxheap.net\/ddaniels\/blog\/wp-json\/wp\/v2\/comments?post=12"}],"version-history":[{"count":1,"href":"http:\/\/www.boxheap.net\/ddaniels\/blog\/wp-json\/wp\/v2\/posts\/12\/revisions"}],"predecessor-version":[{"id":13,"href":"http:\/\/www.boxheap.net\/ddaniels\/blog\/wp-json\/wp\/v2\/posts\/12\/revisions\/13"}],"wp:attachment":[{"href":"http:\/\/www.boxheap.net\/ddaniels\/blog\/wp-json\/wp\/v2\/media?parent=12"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/www.boxheap.net\/ddaniels\/blog\/wp-json\/wp\/v2\/categories?post=12"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/www.boxheap.net\/ddaniels\/blog\/wp-json\/wp\/v2\/tags?post=12"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}