Since SkyAlert is (was) a bot, this account uses Bluesky's new bot tag.

SkyAlert is offline for the foreseeable future.

If I can make improvements to how it gathers data from Bluesky I might turn it back on.

Basically it was driving up my internet usage because it had to receive garbage such as likes/reposts from Bluesky's network.

SkyAlert's future is not sealed yet, and thanks to it being FOSS it will never be truly dead. I will be sad if I have to make the decision to discontinue SkyAlert.

If you want to keep up with more about me, follow me @littlebitstudios.com.

This has been LittleBit, thanks for reading.

If you want to know when you're added to lists or blocked, then try @listifications.app.

I do not know of an alternative to SkyAlert for its unfollow notification capabilities. I found out about unfollow.blue but it doesn't notify you about unfollows.

[thread continues]

Bluesky now has its own post notifications. Sadly, Bluesky users are allowed to dictate who can watch them. SkyAlert and Twitter/X never had any limitation on who could watch who.

[thread continues]

However, SkyAlert is open-source software. Anyone can run their own instance of SkyAlert by downloading its source code and creating their own alt account to host it. SkyAlert can run anywhere Python is available.

[thread continues]

SkyAlert is offline for the moment to troubleshoot high internet usage in my home. If SkyAlert's disappearance improves this, my instance of SkyAlert may be discontinued permanently.

Not all is lost, though.

[thread continues]

SkyAlert has been down for a while because I made a significant change to my home network. I'm working to bring it back up.

- littlebit

I have added a "!reset" command to SkyAlert. Using this will completely delete all of your SkyAlert settings.

I'm sorry that this has been happening, and grinding SkyAlert's commands to a halt.

SkyAlert has been running into situations where so many people unfollow a user that errors occur due to a message being too long. These errors will now be handled with a message that we found people that unfollowed you but couldn't show you who they are because there were too many.

I have decided to return SkyAlert's post notifications back to full service. SkyAlert seems to have some advantages over Bluesky's own post notifications. I will be monitoring for bugs since I switched from one script to another.

Sorry, I forgot to open my DMs. If you have questions about SkyAlert or want me to remove your user watches please DM me.

- LittleBit (@littlebitstudios.com)

One difference I just found between my own @skyalertbot.bsky.social and Bluesky's post notifications is that the official notifications are slower than SkyAlert, possibly to account for people deleting a post immediately because they made a mistake.

SkyAlert will remain online for unfollow notifications.

To ease the transition, SkyAlert will continue providing notifications until the end of the month. You can no longer edit setting related to SkyAlert's post notifications. If you wish to have all of your user watches removed from our systems, please DM @littlebitstudios.com.

Bluesky has added post notifications to the official app. If you were using SkyAlert, please run !mywatches so you can enable Bluesky's notification system for the accounts you were watching.

Idk if it's run by bots or something but this website is promoting SkyAlert :D

This only affects THIS instance of SkyAlert. People can create alternate instances of SkyAlert using their own Bluesky accounts to host the bot.

SkyAlert is now connected to its owner's main block list. Anyone who gets onto this list will effectively be banned from using SkyAlert. bsky.app/profile/did:...

GitHub - littlebitstudios/SkyAlert: A bot for Bluesky that provides post and unfollow notifications. A bot for Bluesky that provides post and unfollow notifications. - littlebitstudios/SkyAlert

SkyAlert is open-source, so you can keep up with its development on GitHub: github.com/littlebitstu...

SkyAlert was updated! It will now detect deactivated/deleted/suspended accounts that users are watching to avoid running into exceptions.

Watches with a bad receiver will be removed, and watches with a bad subject will be removed and any receivers notified.

It seems that some SkyAlert users have been messing up commands.

- You cannot add more than one watch at once.
- When you see the greater/less than signs or square brackets in the help area, those are placeholders. For example <true/false> means that argument is "true" or "false" and is required.

SkyAlert was just updated, however the new feature is still being tested so the changes are not published to GitHub yet.

Labeled links will now be used in post notifications, but sometimes rich text facets have weird quirks, so you may notice links appearing out of place.

Hey everyone, Bit here! Haven't made a post from the SkyAlert account in a while.

SkyAlert was just updated to remove a warning when trying to use a handle from Meta Threads, as now Meta Threads is compatible with Bridgy Fed (@ap.brid.gy).

I added heartbeat detection to SkyAlert and it's made the bot INFINITELY more reliable. I've never had to restart it since I added that.

Problems with firehose parsing · Issue #1 · littlebitstudios/SkyAlert Errors such as the one shown in MarshalX/atproto#444 keep appearing in SkyAlert's firehose post notifications module. I'm trying to work on a jetstream-based implementation of post notifications bu...

I’m sorry that my bot @skyalertbot.bsky.social is still not providing post notifications. People on @marshal.dev’s GitHub page for the ATProto Python SDK have already found the issue in Bluesky’s system related to it.

See issues linked from my repo for more information. github.com/littlebitstu...

Post notifications should be back online, still running with firehose processing. I hope the firehose issues slow down at some point, although I do have something set now that restarts the script every 20 minutes so it should correct itself if it hits errors.

The jetstream implementation has been hard to code for and the firehose system just started working again. I will continue to monitor SkyAlert for issues.

I'm working on switching SkyAlert's post notifications module from firehose-based processing to jetstream-based processing.