BlahgLegacy updates and Bluesky abstinence

Update: fixed a heading being the wrong size

I've been working on BlahgLegacy the past few days, to change a few things and fix an issue. I'm also abstaining from using Bluesky for a day to see what it feels like.

BlahgLegacy updates

The day after Brine was set up, I decided to change how URLs work. Previously, it would be the rkey and title of the article, like 3lyz6j6dwvk2p-welcome-to-brine-2. Now it is flipped; the title is first and then the rkey. This is more in line with other blogging sites, in particular Medium, whose URLs are almost identical, for example, web3-is-self-certifying-9dad77fd8d81.

Not long after that, I discovered a problem: for some reason BlahgLegacy can disconnect from the Jetstream without throwing an error, which causes it to never reconnect. This was made worse by the fact that while BlahgLegacy can save the current Jetstream cursor, it had no ability to reconnect with that cursor. So on the 18th, I took some time to fix this. While it can still disconnect randomly (I suspect this is a problem in the atproto-jetstream crate, which I can't fix), it will load the cursor on start, so it won't miss events like it used to.

Lastly, BlahgLegacy now supports RSS feeds, among other changes. At this time, Brine 2 does not expose its RSS feed, but this may change in the future.

24-hour Bluesky Abstinence

Today I decided to completely abstain from using Bluesky for 24 hours. My current plan is to leave Bluesky on New Year's (this is not set in stone, however), and this is a test to see how much I will miss it.

As I write this, only a few hours are left before the abstention period ends, and I've definitely missed being able to see what the people I follow are up to. But more importantly, I'm missing all the news regarding the AT Protocol.

I can forgo my follows, as much as I don't want to, but the ATProto news is localized on Bluesky, and it's too important to miss out on. As such, my new plan is to do what I did with Twitter before I enacted my current "no interactions" policy: I'll stop posting original content, but I'll continue to like and repost the things I'm interested in. In a way I'm already doing this; I haven't been posting very much as of late.

The main problem is where all my original posts will be. While I have been maintaining BlahgLegacy to aid my efforts in reducing my dependency on Bluesky, I still desire a place to microblog. My hope is that a new microblogging AppView that uses its own lexicon will come into existence, and I'll begin to post there. Preferably, this AppView will have an optional setting to show posts from Bluesky, so I can continue to interact with people there while keeping my posts exclusive to the new AppView. And when Bluesky gets to the point where I'm too uncomfortable to use it any longer, I can just turn off the setting.