HTML file format

HTML are really nice files, they are straight text, but with it (well and a few other things) you get what you are looking at now.  So, let’s take a look at what an HTML file consists of:

  • Content encoding
  • Doctype declaration
  • HTML block
  • HEAD block
  • BODY block

So, let’s dive into that a bit, and go through this step by step.

Content Encoding

HTML files are usually encoding in utf-8 unicode format.  Which for “8-bit” characters is pretty close to ASCII (in fact all ASCII characters are coded identically in utf-8, though ASCII at times might have transferred them differently being only 7 bits of significant data) but also allows for “extra characters” due to the fact that the first “block” of characters (8 bits) is only part of the set.  In fact, in utf-8, if you need to encode more than the 7 bits of ASCII you will need more bytes per character.

Using ASCII encoding (declaring it) is relatively rarely done these days.  ASCII encoding was used in about 17% of websites in 2012, while utf-8 was used in about 63% of websites.  Other encodings were used as well.

You probably don’t need to worry at all about this, unless you are using characters outside of the ASCII set, and not escaping them (so they can be represented as ASCII).  I have seen some websites where the ‘ displays as 3 characters that don’t look correct.  This is a problem that somewhere along the way utf-8 encoding has gotten shifted to ASCII encoding, and the result is that rather than a “left single quote” you get a meaningless series of characters.

So, save your file in text format, and be careful if you are transferring the file from one place to another, that the encoding isn’t getting broken.  Then you need to look at what you put into the file itself.

Doctype Declaration

The first part (first line) of an HTML file should be a doctype declaration.  There are a number of options, and in the past the “correct” one was difficult to remeber as it was something like:


which you can see is a lot of specific bits of things to remember, now the current version of the same thing is:

<!doctype html>

Which is a lot easier to remember.

While most browser don’t care much at all about this, in order to have things properly formatted it is “supposed” to be there.  The w3schools says that it is “required” in their information about doctype declaration, and the W3C list of valid doctype declarations, has a list they consider valid (though I believe that there are other ones which can be used, as well).  So, if you open with a proper doctype declaration, that’s a “bonus” in my book, but people who are even more pedantic say it’s “required”.  And by the standard (w3c sets the standard) it is required.

You’re unlikely to have anything break if you forget it.

HTML Block

This is something which has not changed since I started working with web development.  The doctype is not part of html, it is just part of the file.  And it does look a lot like an html tag, but it’s not.  It comes before any html, and the first tag (an opening one, which needs to be closed, but closing comes after opening) that you are required to use (again if it’s missing, probably no browser you’re likely to encounter will have any problems with the file as long as it can determine in other ways that it is an html file) is the html tag.

In its most basic form (and I usually don’t modify this myself until I start to look at finalizing stuff about a page, and mostly for accessibility reasons) is:


Which is really simple. There are a number of attributes you can add, such as:

<html lang="en">

in order to define your entire document (you can use the lang attribute on any tag, as it is a “global” attribute) as being in English. This is helpful in terms of screen reading, or other accessible technologies. It also can help (though usually not by much) search engines to better understand your website.

Once you have that defined (it can only occur once), it needs a closing tag (and also has two required blocks inside it the head and body blocks (again only one of each)), and the closing tag is:


And as with all closing tags, it is only the / and the tag name, and not all tags have required closing tags.

The HTML closing tag should be the last thing in your document, as anything after it is not supposed to be interpreted (I don’t know what the behaviour of any browsers are if there is a closing HTML tag, with content following it, they are not supposed to interpret it at all, or display anything with regard to it, but I can’t guarantee that all of them follow this behaviour.

Now let’s look at the first of the two required blocks within the html block.

HEAD Block

Most of the information you need to know about the HEAD block, is mentioned regarding the HTML block.  They have different attributes (global ones can be used on any html tag), but the basics are the same.

The HEAD block defines “header information”, most of this isn’t displayed (well it’s not displayed on the web page itself), but is used to define the entire document.  The HEAD block starts with a:


tag. This is the minimum you will need to use for that, but as with the html tag, you can include attributes. I’m not going to go into that. If you have included an lang attribute in the html tag, unless you are “changing” it, you don’t need to repeat it, and it should only be used where you are changing it (if I use a French word, I might tag it as such, though it is rarely needed unless you are looking at the highest level of accessibility standards).

Likewise you will need to close your head tag. It’s the same as closing the html tag (though it’s a different tag):


Just that simple.

Now on to your main content in the BODY block.

BODY Block

The body block is where everything that you display goes. There are things which can go into the body block (and certain things may only belong in the body block) which aren’t usually displayed. But everything that is in the “web page” which gets displayed is in the BODY block. (Though there are cases where some of that display is at least partially defined elsewhere)

So, really, not much new to say here:


and likewise there are attributes that can be applied to it. This is where all your content will go.

Likewise you will want to put the closing tag:


after to close your BODY block. As this all falls in the HTML block, your HTML closing block is what you need to do right after that.


Here are a quick list of resources, both general sites (I am starting there) and specific resources for the topics which are included here:

Looking at basics of web development (starting with HTML)

I have decided that I would like to look at the basics of web development, and I have a bit of an approach I would like to look at for this.  I think that I will probably approach it in this order:

  • HTML
  • CSS
  • PHP
  • JavaScript

I think that makes a fair amount of sense.  I’d like to create a new lesson every week:

HTML Basics

I have been looking at the HTML basics, I’m not really sure where I would like to go with this for sure, but I am going to look at this starting in this order:

  • HTML file format
  • HTML <head> content
  • HTML <body> content
  • <head> tags
  • <body> tags

I know that looks pretty brief, but I think several of these will end up being multiple lessons.

I also would like to be able to provide external resources for most of these things.  In part because I refer to them on a regular basis myself.

CSS Basics

I will do a similar thing with CSS:

  • Inline CSS format
  • Header CSS Format
  • External CSS Format
  • Including External CSS
  • CSS selectors
  • CSS declarations
  • CSS properties
  • CSS values

This is a much longer list, though I think it is more finely broken down.

PHP Basics

PHP is my strongest programming language.  I hear a lot of people complaining about it, so I keep trying to do things in different ways for a variety of things, but I think that it is a reasonable place to start learning a number of basic programming concepts:

  • Writing output
  • Getting input (forms)
  • Processing input
  • Displaying based on new input.

That’s really the very basic structures.  I will probably need to look a variety of different things or not.

JavaScript Basics

JavaScript allows you to do things on a client’s computer.  I use it very minimally right now, and think that I am strongly of the opinion that JavaScript (and CSS) should be able to be turned off, without losing the basic functionality of the webpage.  I can’t really break this down all that easily, but I can work on handling this in a better way along the way.

sudo and su are very different…

I have been trying to get my computer updated since Friday (almost a week) and I usually use a command like:

sudo emerge -uDaNt @world

When I want to do an update of my “world”. To me this should be very close, if not practically identical to:

emerge -uDaNt @world

And I have found that in a lot of ways, they are very different. I had been having a number of packages which I have been unable to update with the previous command. And someone told me “don’t use sudo”. Which to me sounded like a “really bad idea” as I understood it, because sudo is supposed to allow a person to run a command as another user (usually root) without having to log in on that user’s account.

Apparently, and this is probably a good option, is using:

sudo -i emerge -uDaNt @world

is almost the same as using the “su” version, but not quite.  So, if when using “sudo” you run into problems, there is a good chance that doing “su” will fix this.

Honestly.  This is mostly just a quick note to myself.  By writing this down like this, I remember it far better.

The way I ended up breaking things, and then trying to find something to fix it wasn’t really pretty, but it seems like now I have got the things that I was having so much trouble with for weeks coming up.  This should be the last bit of this part of the update process, and I am working on package 6 of 18.  But it’s a huge package, so that is likely to take a few hours, so I will sign off with this.  I do think I will need to fix a few other things, which I will write more about shortly.  I have a “new” kernel that I need to get working correctly, and somehow in this process, I have managed to break grub badly enough that I’m having to manually start my boot.  But those are for Tomorrow, or Saturday.  Tomorrow is a Open Psychology Work/Drop in day, so may not be working on this stuff in the foreground during that time (10:00-15:00 Pacific Time (Pacific Daylight Time this Friday, and until after the first Sunday in November, thus GMT-7 (or UTC-7 if you prefer that designation))).

So, see you tomorrow for the stream (if it actually works).


More notes on Gentoo install (cheatsheet stuff)…

When I last wrote about my process for getting my machine up and running I was getting the system updated to the latest version of software.  That was a while ago.  But there are a few more things that need to be done before the computer really is bootable, though I have found the order is probably somewhat less important than the documentation suggests.

Continuing on

There are a few steps that are still needed.  Setting up timezone is next on the list I have, then setting up locale, setting up fstab, and there is where my notes get really fuzzy…  But GRUB is what I next have notes on, and that ended up being messy…  That will be a separate post…  But at the end of this, I have a few additional packages that I found I had to install.

Timezone Setup

ls /usr/share/zoneinfo
echo "America/Vancouver" > /etc/timezone

This first line points to where the timezones are defined. The second how to set it (though this itself doesn’t set it right now). The example is what I have used.

Setting Locale

This sets a bunch of different things, it needs to be set, so you need to go through a bit of a process.

vi /etc/locale.gen
source /etc/profile
export PS1="(chroot) $PS1"

The first is editing the locale.gen file, which says what you are running for locale on the system. Then you run locale-gen to create it. The remaining commands are getting you into the newly created locale settings.

Kernel stuff

Creating and installing a kernel is needed to get your system working. Complete instructions for setting this up will require at least one other post. There are a few commands that will get you started for setting up your kernel.

emerge --ask sys-kernel/gentoo-sources
ls -l /usr/src
emerge --ask sys-aps/pciutils

The first command gets you the kernel sources, there are other options for this, but this is the recommended one. The next line checks to see if you have your symbolic link (symlink) set correctly. Then you install the pciutils which gives you the command lspci which can help you to identify your hardware which you’ll need support for.

After you have that information you need to make your new kernel. To do so you will need to go through the process that I have listed as:

make menuconfig
make modules_install
make install

This is a very brief list of commands to go through, but the figuring out what you need to do with the configuration in make menuconfig is probably the hardest part of it. Also, there may be other steps, for example I need to mount my /boot partition before the make install stage.

Setting up fstab

The next thing you need to do is setup fstab. I don’t have any notes here, but you need to have your partitions that you need to run the system listed so they get properly mounted. I do not mount /boot as I mostly don’t need it, and changes that happen there can be a problem, but I still put an entry in for it, because then I can do mount /boot when I need to do that.

Setting up GRUB

Setting up grub should be fairly easy. You need to install the grub package, then install grub to boot, and then create your grub.cfg file.

This was not what happened for me. I will write a post about how I ended up setting up grub, it could be coming shortly. Also, I will need to write something up about setting up the new video card. That was an adventure too.

Useful basic function packages

There are a few packages that I think are important and rather helpful that I installed manually.

  • vim
  • gentoolkit
  • mate-terminal
  • kterm
  • lm_sensors
  • dmidecode
  • pciutils

Goings on

Haven’t said anything here for a while.  I had been meaning to create a new podcast episode a while ago, and I was hoping to be comfortable saying that the first functional version of the Autism Jobs site was ready.  But currently neither of those things can be said.

What has happened is that I started writing about some of what I wanted in the podcast episode.  And I have been plugging away at the Autism Jobs site.  I hope that by the middle of June to have the ability to login, and post job postings.

I had been also hoping to be starting with the open psychology podcast.  But that hasn’t happened either.  I hope to post something there about some of the reasons that a lot of this hasn’t been happening as I expected.  I think that right now I keep this the way I have it mostly, and then send it off.

Podcast Episode 01 – Setting up Podcast (Part 1)

I talk about setting up this podcast, which is our first podcast.  I have saved this as a number of different formats, but will only be “podcasting” the MP3 file.  All file types will be available on the Blog Post at

I will also be adding my script that I worked from (but really has very little to do with the audio content).

Podcast Script

Podcast Introduction

Jigme: Hello, and welcome to this episode of the Datse Multimedia Podcast.

Jigme: This is episode 1. It was preceded by a very brief episode, which could be called Episode 0. That episode was created to look at the very basics of setting up a podcast.

Episode Introduction

Jigme: Welcome to Episode 1. We are recording this on Tuesday March 14th 2017. Or at least we are planning on doing that.

Jigme: This first episode (real one) is about setting up our first Podcast, and what we did to go about doing that.


Jigme: We are working with this podcast to look at setting this up for the Open Psychology Group, and the Capability Club meetup groups. This podcast is not one of those podcasts.

Jigme: Earlier today I was talking to the founder of the Capability Club, and we were working on our shared group meeting and talking about setting things up for how to look at things in the future.

Jigme: Currently my group (Open Psychology Group) is not exactly working out that well in terms of being able to get anyone to actually meet in person. We are both looking at finding ways to handle online content in a way that ends up working both for ourselves, but also works for other people being able to view what we are working on.

Jigme: As it currently stands, all of our online activities have been done on a prearranged basis and with both of us, and probably the majority of people who might participate, this doesn’t really work that well without a physical space to actually meet in.

Jigme: We were looking at how we are working with things, and decided that possibly a podcast is a good idea, and further that we would like to discuss if the Capability Club would like to have a website developed (which could host the podcasts).

Jigme: So, with that in mind, I started to look at both what it would take for me to develop the website (and provide hosting), as well as looking at setting up podcasting.

Jigme: So here in this episode I will be talking about how I intend to setup the podcast. Most of it actually setup now, except for the fact that this is being written, not recorded right now, but we’re working on that shortly…


Jigme: We will be looking at recording this, finding how to save an iTunes supported format (mp3), creating the post in WordPress including the writing of the post, adding the audio content, and setting the post up to be handling the post as a podcast through PowerPress, and setting up things so that the podcast will be shared on iTunes.

Purpose of episode further explained

Jigme: Really a lot of creating this episode is about why I am setting this up, and also what the process of setting this up is for. I have a feeling that a lot of this text will probably end up in the actual recorded version of this in a very different way. Some of this stuff probably is not going to be as I have scripted. While I have written this in advance, most of that is because I just tend to write better than speaking off the top of my head. Especially when not in front of people.

Jigme: I really am hoping that recording this, and setting this up will help with both myself, and my friend’s goals in being able to reach more people with our content.

Jigme: For me, one of the ways I have been working on both reaching more people, and providing ways for people to support me is through using Patreon. With how that has been working, it has allowed me on good months to be able to pay for both the fellow Creators I have on Patreon, and my costs with being able to produce that content. Or at least help support me in that. So, if you got to you can see what I have been doing there.

Jigme: With the ability, and it seems relative ease of being able to produce podcasts, I feel that further, and hopefully more engaging content will be produced. If we manage to produce at least some more content that people are likely to be more engaged with, then we will hopefully also be able to attract more supporters.

Jigme: My friend who created the Capability Club in Vancouver has similar goals. The way that things have recently been going the group is starting to look at the possibility of having more people working on hosting events, or co-hosting events. While the addition of other venues itself may not be a primary goal, the ability to present information, or presentation is ways which would allow my friend to point someone towards those resources rather than having to reproduce the same sorts of resources over and over again, appears to be highly desirable.

Jigme: For myself, I feel that if I am producing content which is more likely to attract some degree of engagement, especially content that allows that without having to go through having to get several thousand dollars of new equipment (which I really would like to do, but can’t justify it at this point) but hopefully be able to work with existing equipment and through being better able to attract engagement, and produce content attract money through my online activities.

Process of producing this episode

Jigme: I talked very briefly about what I have been doing to set this up. Initially I was feeling that I might be able to take something with how WordPress handles things by itself, and get it working without the need to add any plugins or anything. It is possible that is actually possible, but I’m not entirely sure that it is.

Jigme: In trying to set this up, before I tried to create my first podcast post I ended up installing PowerPress. When I looked at what I had read might be a “good enough” version of the podcast I couldn’t get iTunes to add it manually, nor could I get it to validate with hosting the podcast on iTunes. So I continued to look at it and try to figure out how to better handle it through setting things up with PowerPress. But that first episode (let’s call it Episode 0) I created the post that would become the podcast episode entirely including recording and publishing the post and all that even before I got there.

Recording the episode

Jigme: I am really big on working with things open source, software where possible, and I looked at recording the podcast episodes in Audacity which is a cross platform audio editing package.

Jigme: I know that I had it installed on this computer at one point because I was working on a variety of things where I wanted to be able to work with audio files. I think the most recent time I used it was when I took the audio that I had recorded with my phone (when that wasn’t needing to be plugged into the wall all the time if I didn’t want it to “run out of juice) and ended up editing the audio (mostly I ended up boosting it) so that the audio as it played relative to “normal listening volume” didn’t end up being “is there even any audio here”.

Jigme: But I found it isn’t currently installed. Which isn’t a big deal. I ended up installing it, which I think took a surprisingly brief time to do (maybe a few minutes including finding where to download, and actually installing it).

Jigme: In Audacity when you are recording straight into it (which in the end, I hope I don’t end up doing, but for now I feel it is going to work). There is the ability to monitor prior to doing any recording. When I looked at that to start off with I could see that when I wasn’t really recording any actual content that I was managing to pick up some significant levels of “background noise”.

Jigme: My first recording (which this one is the second) I didn’t really look at how it was recording and try to get it correct. With that recording (which I actually hadn’t listened to the recording itself) I found that I was experiencing clipping at certain times while I was recording (I thought while I was watching the recording that I likely was getting that). With this recording I am hoping that I will be able to find a way that I’ll be able to better handle that. And I think that I probably will be able to with a bit of tweaking as I am recording it.

Jigme: Right now, anything more about recording this particular podcast won’t really be able to be written. I expect that before I move to saving the file that I will do some comments about what the process ended up looking like for the podcast you are listening to which I don’t expect that actually type any of that part up.

*** Jigme likely talks about the recording process for this podcast and any issues which have shown up so far, and how we have dealt with them. ***

Saving (MP3)

Jigme: Apple supports a number of formats for podcasts and the goal for this podcast is partially to get things showing up on iTunes. With the list of formats which we can use for a podcast, I decided that for our purposes right now using MP3 is probably the best option, or at least close enough to the best option.

Jigme: My reasons for choosing another format which Apple supports would probably be to better able to record at a higher, and preferably lossless format. As Audacity doesn’t directly support a format that is lossless that iTunes supports, I decided that I will work with MP3, though I hope to save some lossless format (Probably FLAC) when I end up saving things for this.

Jigme: Due to how Audacity handles a variety of things, most of the export functions need to have another library installed which rather than including the libraries in the binaries, have to be installed separately. In order to save a file in MP3 format, you need to have the LAME library installed. This process on my system took about 1 second to download, and about 30 to get it installed and configured.

Jigme: When I saved the Episode 0 file I set things up so that I had the metadata that I wanted with the file to be included there. I may end up wanting to add more data, though I would really want to make sure that doing so will not end up either getting lost, or end up breaking the MP3 file.

Uploading to WordPress

Jigme: Uploading the saved MP3 file ended up being pretty simple. With the current version of WordPress I can upload it with using the “Add Media” button which shows up when creating a new post. It might not be as intuitive as I would like for some of my clients, but it seems to be a reasonably easy way to handle things for clients who can look at recording and that sort of thing.

Jigme: Once WordPress has handled having the file added through the upload media portion of the “Add Media” page, there are two ways which it allows it to be inserted, that is as a player, or as link. As a link, it links either to download the media itself, or the attachment page.

Jigme: Personally how I would like to handle this, I would use at least two of these forms, possibly all three.

Using PowerPress

Jigme: When setting this up, I saw some stuff which indicated that there are ways to get the podcast to work without really doing much beyond either tagging, or categorizing your podcasts with a unique, or near unique tag or category.

Jigme: I wanted to look at what the highly recommended plugin PowerPress was going to offer me, and consider if it was going to be useful, so I installed and activated it, and worked on getting it somewhat setup, but as I didn’t really know what I had planned for it, I wasn’t really sure I wanted to spend some serious time with it until I actually found out if the “simple without plugin” method actually worked.

Jigme: My first experiments with the “without plugin” indicate that either it doesn’t work that way, or there is some issue with some plugin making that method not working (I think if any plugin is to blame, it is likely PowerPress). So with that in mind, I decided that I really wasn’t planning on looking at it further now, so I started to actually set things up properly.

Issues with setting it up

Jigme: I really hadn’t thought too much about how I would set things up until I got things kind of started with finding that doing things with the plugin installed and activated was simply not going to work. And in looking at setting things up, things don’t work unless you actually have all the settings which are required properly set.

Jigme: I just checked to see if the way that I had set things up with the podcast listing which was supposed to work, now that I have the podcast settings properly set (and the podcast itself listed as a podcast within PowerPress), the feed which I had setup before works. I will need to look to see if I need to set each episode up as a podcast with PowerPress in order to have them listed, or if the other settings are correct.

Jigme: For me, the biggest issue I ended up running into (and I haven’t got it how I want it yet) was handling the podcast cover art. I didn’t have a version of any of my work which I wanted to use for that which worked. I had a file that I had hoped would work, but it didn’t.

Jigme: I looked at what that file looks like (I didn’t replace it) and I see that there are two issues that may have been a problem. One, and probably most important. The dimensions in pixels was “too small”. The largest pixel size for that is about 1/6 of the smallest that is accepted for the file. That might not have been enough to save it to the right size for that dimension. But it might have been.

Jigme: The other issue with it, is that the cover art image is supposed to be square, and that file is certainly not square.

Jigme: So I created a new version of that file, which was square, and was the size of the maximum (and recommended) dimensions for the file. But as I said, that file still isn’t how I want it, but at least I have something that is working for now, and it won’t really take that long to change how it works for this podcast, and create new ones for the other podcasts.

Jigme: Once I created the settings correctly, it asked me to create a post (which I actually had already done)…

Creating Podcast Data for Podcast

Jigme: Looking at the create a post, the first thing it takes you to is the post editor, with a blank post. Nothing is obvious on my setup as to how to handle a new podcast episode because that was “below the fold” being below the edit window, and also far enough below that to not even show up. So clicking back and forth, I see that the way things are setup, there is a podcast listing which needs to be setup in order to allow the podcast to be seen as a podcast. It is pretty simple with MP3 to set this up, all you do is link to the MP3, and once that’s done it pretty much works.

Jigme: I see that there are options which I don’t have enabled and probably won’t until either I want to work with them myself, or I end up working with a client who wants to work with them. These options include a variety of ways of handling podcasts, and that was under the Basic Settings, under Advanced Settings, things get “very interesting”.

Jigme: How the Episode 0 ended up going out, pretty much all I had to (and wanted to) do was to make sure I properly linked to the MP3 file. Looking at the advanced settings, and some of the things there, I can see that fixing the issues I was seeing with how iTunes handles the podcast display, I will want to work on setting things up so that the information displays in a way that is helpful.

Thinking About Show Notes

Jigme: When I see how the podcast is showing up in iTunes, after having a post which has the content I want for show notes, and I end up seeing that iTunes is not displaying that other than the first 500 (or so) characters. This is a good thing to note, and try to get these show notes either through putting the information in a format that works that what ends up at the top of the blog post is a good pointer to the blog, which will contain the full show notes, or saving the show notes for the podcast version (specifically for iTunes) ends up directing those who want full show notes to the full notes.

Jigme: It does look like I can write my posts however I end up wanting to, and then write show notes for iTunes, and possibly other sites independently to point to the full notes on the blog (for those that don’t display them in full on the player).

Saving Page

Jigme: Once I had the right stuff there, I then tested to see if things show up differently with the podcast in iTunes. With my looking at that, I could see that now iTunes is loading it, and that listing in the iTunes directory it is verifying that we have a working feed. This was our main goal that I had hoped to manage to get to at this point. And we’re here.

Setting Up iTunes

Jigme: The next goal that we were looking at was having the podcast being listed in the iTunes directory, so at this point, we have submitted the podcast to the directory, I have received an email saying that it is indeed successfully submitted to the directory, and that it is pending review. Most likely, it will be up to 24 hours from the time this post (including the recorded podcast) ends up getting accepted, or to some degree responded to.


Jigme: So with that, I thank you for listening. I am going to try to get some of this, if not the whole thing recorded before heading to bed, and if that is done, I hope to have it posted around the time I get it recorded.

Jigme: I suspect a good amount of what I wrote here will be either elaborated on, or edited in the actual recording. But here we go starting the recording (or in the audio, finishing the recording). Take care everyone.


Looking into podcasting

A friend of mine asked me to look into podcasting and what would be involved in getting that to work.  This will be a quick post, which is part of testing things out.  As I currently understand you can pretty much run a podcast with WordPress without any extra plugins or anything.  This post will test this out.  Steps to get this post out are (not all done yet):

  1. Create start of post
    1. Place in Podcast, and Episode categories
  2. Record episode
  3. Save episode in supported format (looking at posting to iTunes)
  4. Upload episode to here
  5. Link media as both media, and as a link to the file
  6. Test to see if we can get an accepted RSS feed with the file included
  7. Test importing to iTunes

If all of that works out, that would be “most basic setup” but I also want to test how things work “better” with the recommended Podcast plugin, and see if that ends up being worth it.  I think maybe it does for some features, but if this works it may not be really that worthwhile for the existing setup.

That should be a playable link…  And:

Intro Podcast 01 is a link to the download.

Intro Podcast 01 a link to the attachment page.

OK, I have done steps 1-5.  I am OK with how that’s working so far.  Now to test 6 and 7…


Autism Jobs development

About 3 months ago I decided (after reading something I saw on YCombinator’s Hacker News) that I’d take a look at creating a site for Autism Jobs.

The first step in doing that was really deciding just what I wanted to do.  The Hacker News piece was helpful in giving me some guides as to just how simple it could be left.  So since I was pretty sure that for the absolute most basic part of it, I probably could do my coding and stuff in about 2 hours if I manage to screw things up badly enough.

So over the space of a little over 3 hours, I end up creating the first version of the site which is running on our site.  I posted about it several places, and ended up getting a number of interesting results right away (ie. people were very quickly coming to the site).

After that, I decided I needed to start working on a “better version” of it.  So at I worked on developing a better system.

What have we done so far?

  • Replace existing TypeForm form with something we wrote ourself (but isn’t currently functional).
  • Move static content to a more dynamic MVC format. (at index.php)
  • Moved site (when existing site died and existing host said it was my problem to fix) to linode.

There are a few steps I need to get going before I feel that it is “full launch time”.

  • Setup database
  • Move existing content entirely to MVC system
  • Have data for known listed jobs (4 I think instead of the listed 1) into database
  • Create login/register system
  • Look at account types (job seeker, and job poster)
  • Work on getting payment stuff up and running
  • And get mail setup so I can at least send mail out from site.

I’m not entirely sure that those jobs would be done in that order or not.  But I think they are more or less the way I want them in terms of order (though bits and pieces will have to move about some).

I just really wanted to post a quick update to the autism jobs site.  I think the latest post may have been on some other site.  This really is mostly a project which I am working on for the primary purpose of getting stuff together in a way I feel “better” about how it all works.

Autism Jobs Site Creation

Yesterday I quickly read through a post on Hacker News about creating a site for jobs for older people in the tech industry.  I thought a little bit about it, and thought that maybe someone could do the same for Autistics (and other neurodivergent people possibly) so I put it on the back burner because well heck, I didn’t really want to go through the process of creating such a site at this time.

Where are we now?

I really didn’t want to spend the time doing this at the time I was reading the original post, I ended up going to bed.  In the middle of the night I ended up waking up and getting really oddly inspired to just go ahead and do what I was going to do for it.

Getting Domain Names

I decided that I was going to register a domain name (possibly more than one) so went to Web Names and decided to look around on there. I saw a couple of names that I was interested in that were available, and one which I was interested in which was not.  There was a 4th one where it was clear that someone actually was doing something with it, so I just ignored those.

Web Names offers the ability to “make an offer” on a domain name, so I selected these three options.  The pricing which I was seeing was more or less in line with what the “cheaper” sites were listing so I figured go with the Canadian Registrar.

When I clicked “send” the prices that they were presenting were almost 3 times what it looked like they should have been costing.  I wasn’t looking for anything other than purchasing the domain names (and making the offer on the other domain) so I decided to not go there (but I did ask why the discrepancy, will report back later when/if I get a response).

I have been working with two different companies which offer domain names, as well as other services, and have been happier recently with one of them, so decided to purchase the domain names from them.

But, that ended up being “not possible” for one of the domain names, so looked at the other registrar which I believe I could get that domain name through.  I found that I could, so tried to get that, but it ended up falling through.  So, that will have to wait for a week or so.  Or maybe not.

Setting up hosting

Again, I wanted to try something new with my hosting, so I wanted to look at what would happen with the company “Digital Ocean” so I setup to be able to host there.  The big advantage I see to them is that they seem to have the ability to host in Canada, and living, and being based in Canada, I thought this was a good idea.

I had not setup an account with them, and their pricing is a good bit more than what I am currently paying for hosting at Linode, but I am willing to pay a little more for hosting in Canada (well twice as much for roughly the equivalent to the smallest server I can get from Linode).  When I registered they asked me to confirm that I am who I am, but heck why do I have to do that (they have received a payment actually at this point) and since I’m not really sure how long (or if) it will happen I went over to Linode and set things up there.

The site so far

The site is incredibly basic at this point.  The idea which I got from the post I read was that of a minimum viable product (MVP) which is the “least you can do which actually can be considered an actual product”.  With that in mind (and details from the post) I created a Typeform form for people to submit job listings.

That form I tested for the “Autism Jobs Quality Assurance” job (we’re accepting applications) and then worked on getting a static HTML version of the site up.

As it currently stands, there is that job listing there (that I hand coded) as well as the form itself.

Mentions of the site

I have mentioned the site on Hacker News, as well as on Reddit.  I likely will mention this on my more “normal” social network sites such as Plurk, Twitter, and LinkedIn.  I also consider the combination of this post, the site itself to be a Patreon Supported Thing, and I will see how all of this goes.  I intend to write another post about it on the Open Psychology Project website within the next week.

With luck we actually will be having something more to say before too long.

Latest Update:

Here are a few of the things that have happened in the last month or so:

So let’s take those “to the next level” and actually talk about them.

Patreon Post about Amanda Palmer

I wrote a very brief post sharing a “thing” which Amanda Palmer shared with us supporters of her work.  She was “talking” about (in a funny creative way, by writing a song) how she believes everyone who wants the “artwork” should actually support it.

While I believe very strongly that artwork (including stuff which I do, that people really don’t see, my coding and stuff) does not get created for the purposes of simply creating works of art (for the most part) and we need to support our artists.  I also believe that artwork should be available to everyone.

Oddly, in a way Amanda Palmer seems to have missed that bit of the memo regarding that the purpose of Patreon is to actually provide a means for an artist to more freely release their stuff, rather than to create an exclusive club of people who are supporting, and thus receiving your artwork.

support her artwork.  I actually rather like it.  I do not support her attitude of “give me money now or I’m going to go into the corner and sulk, and not give you any more of what you want.”  I guess part of my not supporting that view is since she started expressing it, she’s been having not a bit of difficulty with getting money, and she knew full well that “the art of asking” really is “knowing the answer is yes, even before you ask”.

I am still trying very hard to learn what my art of asking is.

Updated Todo posts:

I updated my upcoming posts, or whatever I want to call them.  It is a list of posts which I am planning on writing “in the near future”.  Usually, I don’t actually pay a bit of attention to them, except when I go, “hey I need to update the list here”.  And right now I’m close to getting to that point again.


I added (I think) a couple of items to stuff which will show up here.  As well, I also made it clear that I was creating a list which also included the other site, the Open Psychology Project.

Right now, I am thinking that each project I will keep the updated posts stuff separate.  I will link to the “latest at the time” post when I update the other list.  It should make keeping the lists updated a little bit easier.

Open Psychology Project

I also updated the post with the list of topics I intend to cover over at the Open Psychology Project.

Moving of this site

Hey, I think we only managed to get this site moved a little over a month ago.  Or maybe a little less.  I really don’t remember exact timing.  There is a post which was “while in progress” about moving the server now.  That I think was the day I moved this site to where it is currently.  Which was 32 days ago.

Moving of Open Psychology Project

I also moved the open psychology project, I think about 2 weeks later.  A lot of technical stuff has gone on there.

“Last Month’s News”

Last month, I wrote about what had been going on.  I’m glad that I did, because really it seems that by writing a wee bit about every little thing that I managed to do, I actually might have managed a few different looksees at what I have been doing.  I don’t really know for sure.  While I do have some tracking setup, I really don’t know what the traffic really is.

eBook initial thoughts

I received an eBook by a woman writing about her experience as an “Aspie” and wrote a few things about my experience with trying to read it.  Oddly, writing those words about my experience of reading it, did get me to dig in deeper in terms of setting up something more for funding beyond the Patreon which is supporting the creation of content here and elsewhere, and created a Gofundme campaign to help with upgrading my hardware, in part to better do videos and stuff.

Setup of Gofundme Campaign (and video and post about initial setup)

This is the Gofundme campaign I ended up setting up.  It looks like my estimates for what I really intend to purchase are roughly 60% lower than they should have been for some stuff.  I am going to keep the current goals in mind, and let things figure themself out as I end up getting enough money to actually do the updates that I am looking at.

I had intended to create the campaign earlier, but I found that not having a phone to confirm who I am (worked around it in an odd way, which really doesn’t do much to confirm who I am) was likely to be problematic.  None of what I wrote about this (I don’t think) actually addresses the issues I had with the “two factor authentication” which they have instituted (and I think poorly) apparently on the insistence of their payment processor.

Open Psychology post about Gofundme

I wrote about what I want to do in terms of videos etcetera with the Open Psychology Project, and with that, I created a form for people to type in questions they might have about the psychology, or whatever.  There is currently one topic which I wrote out by hand (and will probably mostly type in from that) which will go with that content.  But I might also try to answer the question I posed to myself (or maybe the explanation of the answer I posed for myself) in a video.

Setup of Type Form looking at questions to answer for Open Psychology Project

As I said above, I created a form for asking questions that will be answered in the Open Psychology Project.  Right now I think I have two questions which I would like to take a stab at.  Perhaps they will be videos.  Or perhaps they will be my usual text thing.  Or if I get around to it.  It will be a bit of both.

Several updates on the Gofundme Campaign (it’s going decently)

After 11 days we are sitting at just under 10% done the initial target (I have done an estimate of what I need for the computer I want which is about $1000 more than I set for computer and camera, but that is more of a computer than really I should really “need” for some time, so if I manage that, things will be fantastic, if I don’t, well no big deal).

Work on the theme here (I think it was here).

I also did some work on the theme.  Currently all that work has ended up on the backend.  And I didn’t manage to get it close enough to release another “point release” but the github for the project (develop branch) has been kept up to date with my testing server.  It is pretty rapid fire while I am developing to see what ends up going there.  I hope that by the end of this month I will be able to enter shortcodes to get what I want, and I can configure those shortcodes to put “default text” where I want it, and that the default text actually configurable through some configuration mechanism.