Anyone else ever feel like their sleep apnea fights back?
I will periodically reach these points where I feel like I’m absolutely dialed in on my CPAP settings. 0.2 AHI, 0.0 95% Flow Limitation, 0.0 on all leak measurements all night, 0x 3-4% O2 drops.
Congrats! You’ve conquered OSA!
A few days will go by, a week, you’re just happy. You make no changes. Then you wake up and check your stats and they’re all over the place, eh that’s odd, just a bad night.
And another, and another. Nothing changed, except your OSA adapted.
Installed an Ecobee thermostat, and one feature is an indoor air quality sensor. When our windows are closed, it almost always reports our home is “poor” despite two other Eve sensors saying everything is fine.
The ppb level of the Eves (at their worst) yesterday were 116 in the main floor (where the Ecobee is) and 198 ppb in my office which gets the worst ventilation of any room in the house – and is where I sit all day.
Finally pulled the reading off the Ecobee API: 172718 ppb
I apparently live inside a volcano.
Even on Sunday, when it was beautiful weather outside and we had literally every window in the house open, the Ecobee shows 517 ppb in TVOC, which, like, would still be kind of terrible.
Every time I start to think to myself that I’m done with Mastodon and all the inter-instance-blocking-bullshit-drama, I go look at Bluesky and Threads for a little bit and then remember on the whole we are still better off.
I can’t get Apple Intelligence to create a Genmoji based on all the thousands of images it has in my Photos library of Me, with blue eyes. It really pisses me off.
I’ve been pretty consistent about taking vitamins and such for 15 years. I go through periods where I’m more serious about it, and sometimes just keep it simple.
The following is an email sent to all vmst.io members on July 3, 2023.
Before you swipe left on this message, allow me to clarify that I’ve considered for a long time whether to send an email to all of you. I deeply respect your privacy and understand that you didn’t provide us with your email to subscribe to a newsletter. Whether you joined yesterday or nine months ago, we’ve only ever used your email for account alerts.
After decommissioning the vmst.io WriteFreely instance last week, I moved my blog back to Ghost. But then this weekend I remembered what an absolute shit experience writing or editing on a mobile device is with Ghost. A few people mentioned that they just don’t blog from mobile, but I like to be able to do all my work from as many devices as possible (I push vmst.io updates from my phone just because I can.
I went to an ENT a few weeks ago because I have been getting tonsil stones for a few years now, especially bad in the winter months. He said “yep your tonsils need to come out, this is going to be terrible, plan to be out for at least a week” 😯
That adventure is now scheduled for the week of June 26.
While I’m there I also mentioned that I snore really badly at night.
On Friday, the vmst.io team made the decision today to sunset our WriteFreely offering for vmst.io members. Since launching in January we've only had 23 users create blogs, of which only 12 users ever generated any content, many of which were a single post. In total we had about two users aside from myself that used it with any frequency.
My usage was mostly to justify it's continued existance.
Because WriteFreely requires a MySQL database backend (all our other services use Postgres) the costs of keeping the service operational outweighed the benefits to our members.
Elan Hasson asked in a Matrix chat group of Mastodon admins how he should go back and watch classic Star Trek. It got me thinking about a list of episodes to help jumpstart your knowledge without having to watch every Original Series episode (of which some haven't aged super well, or are confusing to new viewers in the context of modern Trek.)
Here's the list that I came up with:
We’ve been using Netlify for the docs.vmst.io site for a while now, but it wasn’t until recently I realized it could be used for other things that we host.
I’ve now successfully moved:
element.vmst.io, our Element Web portal for accessing Matrix. elk.vmst.io, our Elk alternative web client for Mastodon. semaphore.vmst.io, our Semaphore alternative web client for Mastodon.This means fewer Docker containers and custom build operations are needed to maintain these deployments.
This morning I removed just over 3000 dead instance connections from vmst.io. I know Mastodonizens don’t follow their follower accounts as closely as some folks on other networks, but I wanted to let you know you this operation might have caused some go missing in this purge.
These are instances that have quit responding for at least seven days, and in some cases they haven’t been around since November. A couple weeks ago I saw an uptick in the amount of SSL errors in Sidekiq communicating with various remote instances and noticed a trend of instances that were stood up around 90 days ago, with Let’s Encrypt certificates, that have since been abandoned.
I've doing some blue/green (maybe it's just A/B) testing on vmst.io this week with server updates and Mastodon dependency testing. Specifically focused on some upgraded versions of Nginx and Puma (which are now fully live for everyone) and some backend libraries for the streaming API to things like Redis and Postgres.
I've been rolling out more updates this way, since things are pretty happy and functional with multiple systems running each component.
I've been doing things with computers, since last October. In addition to launching a Mastodon instance at vmst.io I've since launched an integrated WriteFreely platform at write.vmst.io. As a result I will be blogging there regularly from now on.
The vmstan.com site will remain here for the time being, until I can maybe migrate the content into WriteFreely.
https://write.vmst.io/vmstanhttps://vmst.io/@vmstanhttps://whois.vmstan.com
One of my core beliefs about Mastodon and the Fediverse is that there needs to be transparency in the operations of the various projects and instances. This includes transparency in both the financial and technical operations of the instance. For the financial piece, we have a single source of truth on our Funding page that has total income from memberships as well as monthly/yearly expectations of expenses. We'll be providing a more granular update here soon that shows exactly where we are in terms of free cash flow.
I wanted to provide a round-up of some changes to the vmst.io infrastructure since it went live last month.
No More CloudflareOur domain had always been registered and DNS provided through Cloudflare. For a brief period I was testing their WAF (web application firewall) service with the site but this led to more problems than perceived benefits. The sentiment within the Fediverse is generally negative towards Cloudflare, although many other instances use them.
I’ve had a few thoughts rattling around about registration numbers on vmst.io, vs instances that are generally wide open. The instance officially went live on October 6, but didn’t let anyone else join until a few weeks after. We are listed on joinmastodon.org so we definitely see more random user signups than instances that just rely on word-of-toot.
Because we ask folks to "apply" for their account here rather than just signup without moderation, we get maybe 1/10th the number of registrations you’d see in somewhere else.
This post is a rollup and expansion of a set of Toots around the new vmst·io infrastructure that went live on the morning of Wednesday, November 23, 2022.
When I launched vmst·io at the start of October, it was intended to just be a personal instance. mastodon.technology had just announced it's pending closure, and I wanted to see what it was like to own my own corner of the Fediverse.
Interested in trying into an alternative to Twitter? Mastodon is a federated and decentralized social network with over 8,000 different active instances. I’m running vmst.io, which is open for signups. No ads or algorithms. Join us.