10 June 2023

Why Buzzkill(.org) went Paid

TLDR; buzzkill.org and DF Crafts.net are in the same workspace because I started a business. Read on for all the weird not so technical stuff that happened that caused it.

Yep. I did a whole bunch of confusing crap.

So it started way way way way way way back in the day, Google workspace was called something else. Maybe Google Apps, I don’t even remember. Suffice it to say it had a different name.

For the sake of this article: it’s Google Workspace.

I had two domains set up on what is now Google Workspace: buzzkill.org and crazedsanity.com. each had their own setup. I had a whole bunch of licenses. Crazedsanity.com was one that I used for all the aliases that I could use to obscure my real email address. Spam. Special account names.

Now, before Dain starts laughing about how many email addresses that I have, that domain actually had only one. There’s also the catch-all, which basically I never really looked at… Except when I wanted to take a laugh at the patterns I saw in spam.

Then there’s Buzzkill.org. It’s short for Buzzkill Productions Unlimited. A business name that has been sitting with me since… Well, a long time ago. Since I had the “.com” version that got stolen out from underneath me due to a whole bunch of technical crap. I didn’t pay for it because of aggravation and principle… Because I missed paying like 20 bucks by 2 days, and I didn’t want to sit in court forever with the company that could hold me in court forever until I eventually gave up and just let what happened happen anyway.

At one point I tried to start a business from that name. It didn’t work out, because I didn’t have a salesperson.

I didn’t have a salesperson because I didn’t ask the right question to the right people. And I don’t handle rejection well, especially when I get flustered.

But I digress.

Buzzkill.org was for a little while a business. Then I gave up on that dream… Like, I literally said ” Fuck it ” and asked anybody that if they wanted an account there. Because it’s a cool name… I mean, I thought it was.

We had that sort of unofficial motto: “accept no limitations,” (copywronged 1996-ish).

Then it, again, this idea of a business was started up again. This time, it was my mom’s idea.

Anyway. DF Crafts LLC was born.

I played around with a whole bunch of stuff. WordPress. WordPress with its own cart system using things recommended to me by this great little advertisement agency called KK Bold.

Anyway, one of the Workspaces needed to be personal. The other needed to be a business. Things happened. I logged in through different browser profiles. Account cross-linking happened.

I got confused. I got frustrated. I tried to avoid paying too much by doing a bunch of complicated bullshit.

Then, a light seem to happen. Google indicated to me that my billing would be delayed for years, possibly indefinitely.

So finally, I figured out how to get my one Workspace to remain free. The other one, being a business, is paid. Unfortunately, the billing is not delayed…

This website? This is not a business.

Can you hear that Google? Microsoft? Bing? Random spiderweb thing that’s listening to my personal shoutbox?

I’ll probably write up something humorous and more cohesive on my private shout box, aka my Patreon page (patreon.com/crazedbuzz). If you want to peek at it, subscribe. Or ask for a cheaper rate if you are unsure. And if you’re upset? I’ll refund your damn money. I’m easy. Wink.

PS: If you were wronged by losing your email from one of my domains? You can always just ask me to get it back via patreons free contact system, or by my socials, or by my phone number, or… Send smoked signals to my friends, they will probably relay the information to me.

PPS: if you haven’t figured out how to ask me for things? I mean, I can always wait until somebody figures out how to do wireless brain to brain communications. Lol… ? (Shudder)

Category: Uncategorized | Comments Off on Why Buzzkill(.org) went Paid
25 October 2021

Development, Automation, and Saving Time

(Note to the reader: this post has actually been a draft for a number of years.)

I’m a developer. I write code. Also, I’m just one guy with limited resources, so I can’t be spending a bunch of time testing my code in a bunch of different environments, or making sure that every single little change I make doesn’t have some unknown catastrophic ripple effect.

So I automate my life. I take advantage of freely-available tools. As much as possible.

How, you ask?

Self-Hosting Isn’t Worth It (sometimes).

First off, I don’t bother trying to do everything myself. I used to host my own code repository (a really, REALLY long time ago), and this took excess time to:

  1. setup
  2. configure
  3. maintain
  4. work with (use)
  5. keep updated
  6. handle security crap like SSL (you know, changing the website to https://….)

So I use GitHub. I’ve used SourceForge.net in the past, and it was alright for my first everyone-can-see-it code repository, but GitHub just feels nicer to work with. Going from SVN to Git was a hell of a learning curve, but totally worth it (yes, SourceForge now supports Git, but not when I switched). All my code gets out into the world, others can see it, and I get a tiny bit of exposure.

That said: self-hosting is a lot cheaper, if you’re willing to sacrifice time for money (like if you’re a poor nerd 🤓).

Continuous Integration is Very Important.

Unit testing helps avoid introducing bugs that have a nasty ripple effect. I’m not that great at getting massive code coverage with it, but I’m getting better at it.

The other thing is that, really, I can only directly (read: easily) test with the version of PHP available to me. Which is usually the newest version. And my server, or the servers that would potentially use my code, don’t necessarily have that new of a version… so I need to have something test against those old versions. That’s where Travis-CI comes into play.

So I setup the GitHub repository to work with Travis-CI. Every time I push something to GitHub, Travis-CI gets notified. They spin up a fresh new virtual server for each version of PHP that I declared my code to be compatible with. And they run all my tests in that environment. Oh, and they email me the results. WIN.

Semantic Versioning is Important.

Putting readable, easy-to-understand version numbers in the code makes life easier. Well, usually, except when I fall into “version hell,” where this project requires that project which requires another project, and none of them can decide on a version of a related project that they both like. Yuck.

Anyway, I’ll probably write more on this later. Maybe. If you’re lucky. (And I have time… Which is basically never.)

Category: Code, PHP, Rant, Software Development, System Administration | Comments Off on Development, Automation, and Saving Time