Untitled

So, if by any chance you–the reader–are someone that has been paying attention
to what I’ve been writing–or posting, rather, as I’ve not necessarily been
writing a whole lot of anything–I think I can proudly announce that I am
finished tinkering with getting my various blogging efforts in order. Maybe.

A recap / explanation of what I’ve managed to do or accomplish is:

1.) I re-synchronized all of my self-hosted WordPress formatted posts to my
gemlog and to the WordPress.com location.

2.) I went through all of my old WP posts and tried to update all the broken
links.

3.) I started tinkering with my not-so-quick-and-easy gemlog posting script to
try and include a way of automatically uploading posts written in gemini to
Wordpress.

4.) I lcoated a WordPress plugin that someone created that automatically exports
fresh WordPress posts to gemini *.gmi files.

5.) I tinkered with my not-so-quick-and-easy script some more, to make sure that
I could have the WP plugin and my script use the same *.gmi files without
arguing about permission errors or attempting to create duplicate files.

6.) (or maybe 5.5) I figured out how to account for me being silly and
possibly including capitalized letters or spaces in my gmi filenames when
saving, and put in checks to rename things to lowercase and use hyphens in order
to be compatible with the WP plugin.

7.) I figured out how to use nano as something a little closer to a word
processor. YAY!

I would love to sit and write more about how I accomplished all of this, but
I’ve now given myself a slight headache in figuring all this stuff out. I’m just
happy to have something working, finally.

I hope to come back soon with a little more of an explanation of how I did all
this, probably with a reveal of my terrible and likely insecure bash script. I
would also like to come back and share which plugins, scripts, servers and
anything else I’m using, as I really want to give credit where credit is due. I
mean, really, I wouldn’t be getting any of this crap accomplished without the
use of countless other people’s work.

Well, I think that’s it for now. Until the next time.

Thanks for reading;

–J

Untitled

Okay, so now, I’m testing this to see if it will break long lines automatically
or not at 80 columns. So far, it looks like it’s doing it’s job. Sweet! I like
that I finally have it working.

And, I figured out how to run a spell-checker with nano, which works pretty
nicely, as I couldn’t find a console based word processor that really suited
what I was wanting to accomplish.

Thanks for reading;

–J

Lipsum

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Integer iaculis nulla nisi, at sodales dui vestibulum sed. Aenean eu mollis neque. Phasellus volutpat sagittis malesuada. Curabitur vel tellus dui. Morbi ac mi iaculis, placerat leo a, faucibus nibh. Sed arcu justo, ultricies porta lectus congue, tincidunt ultricies tortor. Ut tristique vel dolor vitae tincidunt. Aenean placerat pretium fermentum. Aenean suscipit purus est, pharetra ultricies sem ornare eu. Nulla nunc dolor, finibus vel velit ut, tristique sollicitudin ex. Integer aliquet nibh quis erat malesuada, ut tempor nisl dictum.

Donec sed congue est. Maecenas porttitor ultricies lacus in lobortis. Maecenas at scelerisque orci, at gravida libero. Nulla blandit enim elementum hendrerit dignissim. Duis sagittis libero sed ex porta molestie. Aliquam condimentum sapien ut porta aliquet. Integer ipsum tortor, pharetra at tortor eu, pellentesque cursus justo. Mauris imperdiet id ex vitae volutpat. Orci varius natoque penatibus et magnis dis parturient montes, nascetur ridiculus mus.

Morbi ac sem nunc. Morbi a volutpat sem, non mattis justo. Nunc non magna tempor, faucibus purus at, porta metus. Nulla hendrerit aliquam nunc, at vehicula mauris. Mauris ac tempus nunc. Vivamus vel magna lectus. Cras sit amet urna dui. Donec lacus orci, tristique sit amet semper sit amet, dictum quis ipsum. Nam accumsan tortor vitae vulputate faucibus. Maecenas fermentum felis eu justo congue, eget hendrerit tellus euismod. Sed feugiat fringilla augue, ut rhoncus sem. Etiam a augue lorem. Etiam nec cursus sapien. Cras molestie orci maximus ornare luctus. Praesent velit ligula, molestie nec tincidunt sed, feugiat eu est.

Vivamus cursus venenatis nulla, eu rhoncus urna venenatis id. Sed mollis ut augue in luctus. Class aptent taciti sociosqu ad litora torquent per conubia nostra, per inceptos himenaeos. Phasellus pulvinar pulvinar nisi, id venenatis est. Phasellus sagittis accumsan risus aliquam maximus. Phasellus lorem risus, mattis vitae diam a, mattis lacinia tellus. Donec fringilla, lacus ac mattis eleifend, enim ipsum malesuada justo, molestie tincidunt nibh enim ac augue. In aliquet ornare nunc, in rhoncus nisl dignissim ac. In condimentum ligula a blandit pellentesque.

Sed metus turpis, posuere non ex eget, ornare eleifend sem. Nunc vestibulum vulputate mi non pretium. Etiam hendrerit, lorem at bibendum posuere, nibh quam vestibulum orci, nec tempus nulla justo vitae sapien. Nunc aliquet diam nec metus vehicula consectetur. Duis lacinia massa quam, in fermentum purus pretium vel. Donec tincidunt massa sed nibh blandit placerat. Maecenas eget lorem posuere nisl consectetur malesuada. Aenean ultrices, ex at elementum congue, sem nisi luctus nisl, non interdum dui ipsum eu odio. Nulla congue nec elit ac pulvinar. Vestibulum aliquam urna erat, in iaculis nibh congue ut. Phasellus laoreet quam rutrum, pulvinar lacus a, semper tortor. Fusce vitae mauris tincidunt, malesuada nisi vitae, gravida mi. Nam dictum velit diam, non ornare arcu efficitur non. Nunc sodales mi sed massa sodales, ut porta turpis euismod.

Thanks for reading;

–J

Untitled

# Untitled
## Sat 10 Jun 2023 09:56:32 PM EDT

So, I think I have finally figured out the problems I was having with my script last night–proofreading the script for misspelled variables did the trick. I swear, that seems to be the problem whenever I have issues with something I am attempting to create. Speaking of proofreading and misspellings, I’m hoping to update things and get myself into using wordgrinder or something to create and edit posts–just so that I can have spellcheck; I mean, while I am fairly confident in my spelling, I do know that I do make mistakes. I’m also planning on changing what I send to WordPress, so that WP doesn’t get the header and footer in the post.

Thanks for reading;

–J

=> ../ 🔙 Previous Page

Hopefully a FINAL test of the script

Okay, here’s what I hope is my final attempt at making a script to post to my gemlog, cross it to wordpress, and then go back to the gemlog after manually doing an edit in wordpress.

I say *hopefully*; though I doubt it. I’m likely going to change what I use to edit the gmi-files in the near future, anyway.

———

and here, I’ve now edited the post in wordpress, killing the original headers and stuff that got sent in. I should include that in the script, really. I also need to remember to stop using ellipsis in my writing–I keep forgetting that’ll break my gopher server.

Thanks for reading;

–J

Testing my new script for posting to gemini

If all goes well, then this post will be saved in my gemini capsule, update the capsule, create an atom.xml file, and publish a file to wordpress, automagically.

We’ll see if I actually managed to cobble together something that worked…

(…and now with this edit–after changing permissions and ownership of the corresponding gmi file–we’ll see if wp2smol likes me sending it back to gemini)

Thanks for reading;

–J

Just a quick blog update

So, for the past week or so–in between doing a ton of automotive repairs–I’ve been tinkering with my blogging/journaling efforts. One would think that would mean that I’ve been trying to actually do more writing, right? Well, by looking at the timeline here, that’s obviously not the case.

What I’ve been doing is working behind the scenes on trying to figure out the best way possible to get everything synced between my at home server–the WordPress installation, and the Gemini & Gopher file servers–and my WordPress hosted mirror. If you look back a few posts, you’ll see I had mentioned the desire to have it all playing together, with the ability to continue to have the “big web” content, like my Instagram posts, being brought over into the “small web” of Gemini and Gopher-land files. Well, I think I have things sorted out… Maybe…

I’m still working on getting a perfectly synchronized thing going, and working on trying to fix older “posts” that were migrated from sites like MySpace and LiveJournal–most of these posts are suffering from dead links and references to bad embed codes/commands–which, sadly, this will still suffer in the future as I’m wanting to keep hooks into the “big web”. (See, this is part of the argument for and appeal to the “small web”–keep things simple and less media rich so that data can survive and transfer easier; and, of course, here I am totally mucking up the point by injecting my “big web” ideas into it.)

I haven’t yet seen about whether I can successfully draft things in the gemini-space and have them translate into the larger scope of things–I’m waiting to see if all of my efforts to bring the bigger world into the smaller world works first; as such, this post is being written and published in WordPress for the time being.

…and, just to mention what has driven me to push this along at an attempted increased rate–I’ve been playing around with a “pen-pal” app called Slowly. On Slowly I’ve introduced myself with my ham calls and invited people to Google said calls to find out more about me if they’re so inclined, as I tend to post everywhere as KG4VMA. Well, after making that introduction, I thought it would be a good idea to actually get my butt in gear and make my posts more accessible and in sync so that people using Slowly could see the more up-to-date and for-everyone sides of me. (Yeah, there I go, again; introducing the concepts of the faster “big web” into a world where the idea is to slow down. I’ve really got a problem, here, don’t I?)

So… If you’re into Slowly and would like to exchange letters, you can find me directly with the Slowly ID. My Slowly ID is Z5Z3WY. I try to write ASAP, and usually from the web interface as I find it easier; the web interface also means that I can potentially write a heck of a letter instead of something short, so be warned.

Anyway, I think that’s all I have for now.

Welcome to the Internet

So, the past two posts that have appeared here were things I wrote for publication within the “geminispace.”

Sorry, I’m not going to dive into that and try to explain any of that in this post–feel free to go back and check those entries out if you like if you want to know where I’m coming from.

I don’t know. I’m feeling very lost and conflicted–and outright stupid, I suppose–following the last few minutes I spent checking out a few things people have posted over in that universe. I want to continue to explore things over there–see what other people have to say about anything–but… I think I’ve only managed to find yet another place where I don’t fit in.

Funny. I’d swear that once upon a time someone had told me that there’s something for everyone everywhere on the Internet. Maybe that’s true. But more often than not, I end up finding communities that just don’t jive with me. That bothers me. A lot.

I don’t know.

blah.

Here, have something entertaining to watch. I need to go cook supper for the family…

EDMG340 Week 7 Assignment – Managing Crises and Response to NBC Incidents

Supported by readings in the course material to this juncture, the open or deep web, the E-Reserve site found in the online library at the EDMG340 Consequence Management | Course Guide page ) and / or other outside sources of interest, student is to choose any NBC device/ or CB agent of interest and provide an overarching analysis of that selection.
At a minimum, analysis should cover the following points:

• State the name of the devise or agent and describe its historical development.
• Describe the physical/chemical/biological properties of the device/agent.
• Discuss the harmful impact of the device or agent – its mechanism of action.
• Cite one case where the device/agent has been used in the field.
• List any treaty/policies covering the device/agent and or prohibiting or controlling its availability or use.
• Cite any current news article referencing the use or development of the device/agent.

Work should be a minimum of 750 – 1000 words and should utilize APA formatting.

Save your work as a Microsoft Word or WordPerfect document entitled:
“EDMG340 Week 7 YourLastName.doc” (i.e., EDMG340 Week 7 Jones.doc) and upload as your Week 7 written assignment.

Initially created in the search for a more potent pesticide, sarin became one of many feared chemical nerve agents of World War II and beyond. German scientists Shrader, Ambros, Rudiger and Van der Linde discovered the chemical compound in 1938; nearly a year later, the chemical was introduced to the German Army Weapons Office. Fortunately—though the agent was manufactured into artillery—Germany decided against the use of the weapon in combating Allied forces. (Sample, 2013; BBC, 2016)

Most applications of sarin have been—historically and militaristically speaking—in the form of chemical payloads in artillery. Oftentimes the weapons are binary in fashion, with the final compound being created from separated components upon activation; mixture of the separate chemicals into sarin typically takes place just prior to weapon impact or immediately before/following weapon’s launch (Sample, 2013). Constructing the weapons in this fashion allows for greater stability of the weapon and a longer-lasting shelf life; extending the shelf-life of sarin is of concern for any group or agency wishing to stockpile the agent, as sarin has the potential to degrade into nontoxic acids within a relatively short amount of time—weeks to months—especially when the mixture contains or picks up impurities in the manufacturing and storage processes.

Medically speaking, sarin reacts similar to other nerve agents, with inhalation and absorption posing the greatest threats; ingestion, too, is of great concern. Initial symptoms of sarin exposure include runny nose, constricted pupils and the feeling of tightness in the chest; respiratory and gastric problems soon follow, along with immediate fecal and urinary incontinence. Finally, the greater effects of nerve damage are seen in involuntary spasms and convulsions, coma, and death due to suffocation. Certain drugs—such as atropine and biperiden—can combat some of the effects of sarin if applied immediately and exposure is limited. (CDC, 2013)

Though the United States had invested into sarin as a chemical weapon and had grown a relatively large stockpile of the agent in weaponized form, no reports of the US deploying sarin in an action have been made. Documents did surface in 2008, however, showing that an interest in field testing sarin and VX on Australian troops. Australian Channel Nine reported that the formerly secret documents indicated that US military scientists wished to perform testing on approximately 200 troops in the 1960s, during heightened involvement in the Vietnam War. It had been suggested that the tests were to study the effectiveness of deployment in a jungle terrain. No further documentation exists to suggest whether testing was ever conducted. (Ansley, 2008; Berkovic & Stewart, 2008)

One of the largest uses—in number of victims—of sarin occurred in the 1988 during Iraq’s war with Iran; approximately 5000 deaths are attributed to Saddam Hussein’s use of sarin against the Iranian people and military. Five years later in 1993, the United Nations Chemical Weapons Convention declared sarin to be a weapon of mass destruction, and called for all nations to cease any production and destroy all stockpiles of sarin, as well as other chemical weapons. At the present time, sarin as well as other chemical stockpiles still exist in the US, and are awaiting destruction; other nations, too still have some decommissioned gaseous weapons awaiting destruction. (Sample, 2013)

Sarin has been used in acts of terrorism, as well, with the most notable being the use by Aum Shinrikyo in the attack on Tokyo’s subway system on March 20, 1995. The group’s release of sarin upon five selected sites near Japanese government buildings killed 12, severely injured approximately 50, and affected an approximate 1,000 people by rendering the victims with temporary vision loss. Aum Shinrikyo had released sarin in the previous year in response to a real-estate dispute.

In 2004 two members of the US military were treated for exposure to sarin in Iraq; exposure was limited, however, due to possible combinations of how the weapon was discharged, and the quality and age of the chemicals contained in the weapon. The soldiers treated were members of an explosives unit, and had been charged with the recovery of the IED. It has been theorized that the militants that constructed and detonated the IED had no knowledge that the chosen payload contained sarin or that it had not been understood that a much greater explosive force would have been required to attempt a better mixture, where the original weapon had been of the aforementioned binary design. (MSNBC, 2004)

Finally, one of the last known incidents involving sarin comes from the use in weapons during the Syrian Civil War on August 21, 2013. Portions of the Syrian capital city of Damascus found itself under attack that morning with weapons releasing the toxic gas; estimates of those killed by the poisonous gas vary in number from approximately 300-1700. It is technically unclear as to who was responsible for the use of these weapons—as both the military and rebel forces deny having used such weaponry and blame another for use; it is of opinion by many countries that the use of the chemical weapons was conducted by the Syrian government (Sample, 2013). Regardless of which party was responsible for the deployment of chemical weapons, most indicators pointed to the weapons having been a part of Syria’s inventory at some point. Since that time, evidence has surfaced of additional use of sarin in Syria, through investigative efforts of the Organization for the Prohibition of Chemical Weapons. The OPCW, however, has not been able to indicate a particular time-frame or responsible party for the evidence found in the blood samples collected from the random sample of Syrian citizens (AFP, 2016; BBC, 2016).

 

 

 

References

Agence-France Presse. (2016, January 4). UN chemical weapons watchdog finds traces of sarin gas exposure in Syria. Retrieved January 26, 2016 from: http://www.theguardian.com/world/2016/jan/05/un-chemical-weapons-watchdog-finds-traces-of-sarin-gas-exposure-in-syria

Ansley, G. (2008, July 7). US planned nerve gas attack on Australian troops. The New Zealand Herald. Retrieved January 26, 2016 from: http://www.nzherald.co.nz/world/news/article.cfm?c_id=2&objectid=10520276

BBC. (2016, January 4). Syria conflict: OPCW finds signs of sarin exposure. Retrieved January 26, 2016 from: http://www.bbc.com/news/world-middle-east-35231663

Berkovic, N. & Stewart, C. (2008, July 7). Answers sought over nerve gas plan. The Australian. Retrieved January 26, 2016 from: www.lexisnexis.com/hottopics/lnacademic

Center for Disease Control. (2013, May 20). Facts About Sarin. Retrieved January 26, 2016 from: https://web.archive.org/web/20220402130536/http://www.bt.cdc.gov/agent/sarin/basics/facts.asp

MSNBC. (2004, May 17). Bomb said to hold deadly sarin gas explodes in Iraq. Retrieved January 26, 2016 from: https://web.archive.org/web/20121103072549/http://www.msnbc.msn.com/id/4997808/

Sample, Ian. (2013, September 17). Sarin: the deadly history of the nerve agent used in Syria. Retrieved January 26, 2016 from: http://www.theguardian.com/world/2013/sep/17/sarin-deadly-history-nerve-agent-syria-un