blog birthday

oh yeah… this is my blog-birthday. on this day, twelve years ago, i retired from LiveJournal and began my tenure on my own, personal server:

The Last Post on LiveJournal
The First Post on my own server

now would also be a good time to mention the reason behind my blog, on my own server, Bacchus’ First Law Of Internet, which is “Anything worth doing on internet, is worth doing at your own domain, on your own server, which you control.”

music

there’s this guy who makes music that i really like. he goes by Dominic Robertson, or Ergo Phizmiz, and he’s REALLY prolific: he’s got AT LEAST 40 CD-length albums, plus a whole bunch of soundscape/radio-theatre-like stuff, including a 12 hour 45 minute piece called The Faust Cycle which i haven’t listened to in its entirety because… well, it’s 12 hours long

he wrote me to say that he is “running this radio station at the moment” at Wolverton FM, and wondered if he could broadcast my CD from 2015, I Breathe At It, which i put up on bandcamp and promptly forgot about… 🤩

i didn’t really forget about it, because i always carry a few copies of the physical CD with me, especially when i’m busking, but i forgot i put it on bandcamp, which is, sort of, the way bandcamp is supposed to work… sort of…

the only thing better than writing music and playing it on the radio yourself, is writing music and having it played on the radio by an artist you respect, because he really likes it… 🤩

.org TLD

originally, the .org TLD was intended for non-profit entities, although it was never enforced, and it has been operated by the Public Interest Registry since 2003.

on november 13, 2019, it was announced that the PIR had agreed to be acquired by Ethos Capital, a for-profit investment group, as their first “investment”.

so, basically, what this means is that the .org TLD, which was originally intended for use by non-profit organisations, is now owned and controlled by a for-profit organisation.

also, i’ve heard that some of the executives for ethos capital are also connected with ICANN, and have sneakily maneuvered around so that ICANN has eliminated the cap restricting the registration fees for domains under the .org TLD, which means that registration costs for .org domains are going to go up, MASSIVELY, in the next couple of years…

because that’s what for-profit organisations do with newly acquired resources…

i mean, they made this “investment”, and now they have to make sure that it pays off for them, otherwise why make the investment in the first place? 😒

i currently own 5 domains under the .org TLD.

i am, at this very moment, determining whether it’s possible for me to register all of them for the maximum of 10 years, all at once, rather than having to do it one at a time… because, one way or the other, i’m going to register them for as long as i can at the current price, rather than waiting to be gouged out of business, later on. 😒

🤬👎‼

/8 blocks

i now have three /8 blocks in my email filters.

25.0.0.0/8 in the UK, 53.0.0.0/8 in germany, and 133.0.0.0/8 in japan.

the “standard” email filters, built on “and/or” and “contains/does not contain”, break down when you’re dealing with 16.75 MILLION addresses.

they break down because you can’t just filter on 25. which appears in the middle and end of IP addresses, in message ID numbers, and, occaisionally, in the body of the message.

the result is A LOT of false positives: email which i can’t forward to the correct recipient, because it will get filtered AGAIN

which is quite annoying. 😒

so, with the help of my friend robert, i built a regular expression to handle it:

\D25\.\d{1,3}\.\d{1,3}\.\d{1,3}\D

finds non-digit character followed by “25.”, followed by three repititions of one to three digits, interspersed by periods, followed by another non-digit character.

technically, this regex could be adapted to accomodate any IP address, which means that, theoretically, i have a whole new, easier, and faster method of processing spam. 😈

the next step is to learn how to search for a specific range of digits… 😈

ETA 191127 i discovered that you can’t specify a range of digits with a regex. for that, you need a script, which is too much work. also, i determined that i DON’T need the white space character at the beginning and end of the regular expression, because, sometimes, the IP address is surrounded by parentheses, square brackets, or both.

ETA 191128 i changed it from white space character — \s — to non-digit character — \D — because some IP addresses are surrounded by parentheses or square brackets, but some are surrounded by white space characters. the only thing \D doesn’t capture is an empty string, so the IP address can’t be the first thing in the line of text.

and, even with the \D, this regex, modified to capture 27.16.0.0/12 in china, captures 2.2019.11.27.23.41.02, which is part of the message ID on a LEGITIMATE message. 😖😒😠🤬

this is why i’m rerouting these messages, rather than summarily deleting them, which is my inclination… summarily deleting what i think is spam has come back to bite me in the ass often enough that i don’t do it any longer. 😒

tibetan incense

i ordered a bunch of tibetan incense from Dakpa Tamdin, in India, this afternoon. it should be here in a couple months or less… it’s coming from india and i don’t even have the shipping details, yet. it may be sooner, but a couple of months sounds about right. keep an eye out here for further details as they become available.