View profile

The Self.Newsletter - Issue #20

Dan Hugo
Dan Hugo
New week, new name

Transitional Newsletter FTW!
I decided to consolidate two newsletters (Substack + Revue) for my personal social media avoidance efforts, into one, hosted and sent by Twitter-owned Revue (you are here). Here are some things to consider moving forward:
  • I don’t have a lot of subscribers, and I’ve really been testing the waters for projects that could benefit from subscribers (maybe leading to revenue, etc), so… do I just slam the Substack subscriber list into Revue (sans intersection) and hope nobody minds?
  • I will migrate eventually to something like Mailman, a real listserv that enables actual control over construction of the content, etc. However, I think something like Revue has value as a non-member newsletter (that is, if you want to get updates on a website launch before sign-ups are enabled, etc).
  • Revue is a bit buggy, especially the API (I had high hopes, maybe they’ll get v2 fixed up or kick off v3 with new and improved, um, anything), but it’s still slightly better than Substack, which does not have any plans for an API. Substack’s browser-based editor is slightly better in some ways than what Revue offers, but overally, Revue is okay.
I renamed from The Thursday Newsletter to Self.Newsletter which may evoke thoughts of python (the issue number is running since I started on Revue, pay no mind). I’m sure I’ll make mention of newsletter-related observations right here, so stay tuned.
Seven Days
I will be packing up the last of my stuff one week from today (from this moment, perhaps) to head down to Arizona for a few weeks, before I venture back to Vegas into the new place. This has been something of a headache, but when it’s time to change you’ve got to rearrange, right?
The new place has a loft-ish layout, with two open spaces. The main open space has no carpeting so I’m looking forward to making better use of my wheeled home office accoutrements. I have a feeling any thoughts of kicking of video for any of my projects will be post-re-move later in October, it will certainly be easier to sort of the placement of things like a camera and a light and whatnot. My current abode (which, let’s face it, is a big cubicle with a bed) has a layout that essentially kills about 100 square feet (around 10 square meters), relegating it to storage for Amazon boxes and luggage, especially when I was traveling for Intel every week. One big space will almost certainly work better. The other, carpeted space is intended for bedroom use.
I’m sure George Carlin has something to say about some of this…
A Place for My Stuff
A Place for My Stuff
Anti-Social Media
I’ve mentioned this before, but I believe this issue of Self.Newsletter might get auto-posted to a Facebook Page that I don’t really engage with, because I don’t log in to Facebook anymore. I still use Instagram, a little bit, but there is less and less reason to. So now and then I’ll post a comment along these lines as a reminder that I’m not reading your facebook posts, nor your facebook messenger DMs, etc.
Why?
While I don’t call content constraints Censorship, it is censorship of a sort (note the case of the C in each those), which I don’t care for. More important to me, though, is the fact that handing over our content and identity to corporate sites which profit specifically from using our private data and personality insights, which we’re handing over, doesn’t really get me anything in return. Not really.
So self-hosting and self-publishing are it, with any involvement of social media sites more along the lines of vectors back toward my own content.
In some cases I’ve deleted accounts (WhatsApp, for example), but mostly the accounts stay put and go silent (mostly). Facebook requires an account for use of their APIs, so I do actually have an account without any friends, specifically for managing pages, APIs, etc. This doesn’t get much use, but it’s there and you aren’t like to to interact with it so much.
I generally make some contact information available, eg I have posted my direct contact information to people connected on my “friends” account on Facebook (people I actually know, from high school, etc) and others can reach me in most other places (you can even reach me via this newsletter, if you really want to). On the professional side, I still maintain a Facebook, er, LinkedIn account with current contact info, so that base is covered for now. LinkedIn needs to go, also, but that will take longer.
Comedians and Authors
I normally have one or both of the How Funny and Light Reading sections down here, those will appear at some point. Since I’m getting away from a Monday/Thursday schedule for now, I don’t think it’s critical to fill in those sections if I don’t have anything interesting. This follows with newsletter plans for some other projects… what are expectations, should there be a hard schedule and expected sections/content, or are these flexible?
From my experience on the newsletter-consuming side, a regular newsletter tends to drop back into the noise layer, while a newsletter that arrives with a purpose gets more attention. Not to mention the subject line (for my early testing I let Revue use its default subject line, which is quite boring).
The tools Revue has in place to construct newsletters should make gathering up these items easier, but they aren’t quite there yet.
Buy Me a Coffee and bio.link
I created a Buy Me a Coffee (often abbreviated BMC, I usually go with BMaC) profile mostly as an out-of-band link site, so that I could refer to a central place in podcasts and in written works (like newsletters) regardless of which projects, blogs, etc are up, down, launching, closing, etc. As a way to offer a tip jar of sorts, it works for that without being too obnoxious.
Recently, the BMaC people launched a link tree site called bio.link, and I did sign up to check it out. I’ve had my DanHugo.bio.link url active in my Twitter and Instagram profiles since they launched, and there hasn’t been much interaction from what their analytics tell me. Ultimately, the BMaC profile page seems likely to stick around, the bio.link as another thing to maintain without an API drops down the list.
I think there are better ways to implement a link tree (which, by the way, is a reference to linktr.ee, but there are many, many similar tools out there, all pretty much the same), but really the link tree service is just a templated bit.ly link…
Artwork Attribution
Did you enjoy this issue? Yes No
Dan Hugo
Dan Hugo @DanHugo

Various topics of the day, whichever day, from home or abroad, about this and that and the other thing.
Engineer in Las Vegas, working on a variety of cool projects; Maker of Friends, Friend of Makers. Answers to most pronouns, you can call me Al.

In order to unsubscribe, click here.
If you were forwarded this newsletter and you like it, you can subscribe here.
Created with Revue by Twitter.
Las Vegas, NV 89101