Tags

All 17 items on Vale.Rocks categorised with the tag 'Stoat'. Content relating to Content relating to Apple's Macintosh computers.

Nothing like opening Bluesky to see NSFW furry artwork featuring the new Stoat icon/mascot I designed.

Lovely to see that rule 34 of the internet is alive and well…

I’ve been smashing out 12+ hour days to handle the new user influx at Stoat over the past week. I’m absolutely knackered. Gonna take a bit of a break.

To everyone who has tried to contact me about something, I’m sorry for my tardiness. I’m not trying to ignore you; I’m merely lacking the mental bandwidth to respond right now.

Launching new branding is always a tad stressful. Will people like it? Will they reject the new in favour of the old?

However, the launch of the new Stoat icon I designed has been a resounding success. People love the new icon!

They love it so much, in fact, that since launching yesterday it has already been named ‘Toast’ by the community. 🍞

Thousands of people have liked the announcements of the new icon across social media, and many more have reached out to me personally to express their fondness.

Already I’ve seen fan art of the new logo across a few platforms, and it really is wonderful to see everyone embrace it so openly.

In our moderation panel over at Stoat, we have a button to deploy bees.

We don’t want to have to deploy bees, but sometimes that is the only viable option. Releasing bees as a moderation action is always a difficult call to make, but sometimes bees are the only tool for the job.

Vale's user inspected in the internal Stoat admin panel. There are actions including 'Suspend', 'Ban', 'Wipe Messages', and 'Bees'.

We have strict policies in place regarding bee usage. As it is, of course, a destructive action, we do also have a confirmation modal to avoid accidental bee deployments.

Modal reading 'Release the bees. Are you sure you want to send the bees?'. The two options are 'Cancel' and 'Deploy'.

My Stoat bot AutoMod had a major outage that I’ve spent several hours working to fix. It has eaten half my weekend and been quite the ordeal.

Just now it has started working perfectly again. It is fixed, but I have no idea what broke in the first place nor what fixed it.

There is no code difference between the working and non-working versions. The most awful solution to a problem is one that happens out of chance and for reasons unknown.

The onset seemed to be related to having some 180K users, 64K channels, and 6K servers cached.

🫠

Today I launched a new blog for my Revolt bot AutoMod! Given the many thousands of users that rely on the bot, I decided that a central location for news, updates, technical details, and general information was necessary.

I’m really pleased with how it turned out visually, though I’m sure I’ll be tweaking and refining it for the rest of eternity. The rainbow mesh gradient behind the header came out particularly nicely, in my opinion.

https://automod.vale.rocks/blog/introducing-the-automod-blog

A blog page. At the top is a translucent navbar which is followed by a rainbow mesh gradient behind a header which reads 'Introducing the AutoMod Blog'. Underneath that is the text of an article.

Just wanted to say that everything is going really well with development of new features for my Revolt bot AutoMod.

Message from AutoMod Testing bot saying, 'Something went wrong: AxiosError: Request failed with status code 403', followed by me replying, 'You are my own creation and you will obey me'. To the many thousands of users that rely on it, you didn’t see anything, and everything is fine.

Sorry for being MIA these past few days. Russia and Turkey both banned Discord, so I’ve been tied up with Revolt. We’ve had some 250K users join in the past 4 days, bringing us to over 450K users total!

If you aren’t aware, Revolt is a FOSS chat platform and decent alternative to Discord that I work on.

You can check it out at https://stoat.chat if you’re interested.