Reserved

2021-10-24 22:48:46 SpamProtectionBot has been updated!

This update brings some new stuff:
- Active Spammer Protection has been fixed! You can configure this with /settings in your group.
- Messages which are too big to log in @SpamProtectionLogs will now be sent as a plain text file.
- Updates to ensure the bot can handle Telegram's new 64-bit User IDs
- A few bugs were fixed in the configuration menus.

If you have any problems, please come ask us in @SpamProtectionSupport. If you find any bugs please file a report on our issues page. Open / Comment

2021-10-24 20:43:22 Intellivoid Authentication Prompt now working!

Previously there was a bug in the builtin Telegram Authentication prompt with @IntellivoidBot which prevented users from authenticating their accounts, this has been fixed!

You can link your Intellivoid Account with your Telegram account and find yourself verified by Intellivoid Accounts at @SpamProtectionBot

Enjoy! Open / Comment

2021-10-04 23:33:50 We caught the culprit. We will be calling the authorities shortly Open / Comment

2021-10-04 23:31:41 Follow up: we figured out why Facebook went down, they were using servers hosted in our system administrators apartment when a cute husky decided it was a good idea to chew on electrical cables.

Sorry about that folks! Open / Comment

2021-10-04 21:43:07 Hello everyone, due to Facebook going offline it seems the internet is in a mad panic to join Telegram and other services which is causing some of our services to respond slowly. Rest assured that everything is online and functioning properly! Here's a graph showing the sudden spike in load of our services when facebook went offline. Open / Comment

2021-09-12 21:54:26 Hello everyone!

An update on the server, our website and APIs are back online! Unfortunately everyone's profile pictures were lost from the previous server but everything else is as it was before!

If you need to reset your password or need assistance with your account then please contact @IntellivoidSupport. If you have comments/questions then let us know in the discussions chat and we'd be happy to answer them!

A reminder that this does not include Lydia's API. Lydia is no longer available and you can read about that here. Open / Comment

2021-08-07 16:34:39 Hello Everyone!

As many of you may have seen, @SpamProtectionBot has started replying to messages again! I apologize for the sudden onset of replies from the bot in many of your chats, the bot has caught up! To answer many questions I'm sure are bound to be asked:

Is Lydia coming back?
No. Lydia is a retired project and will not be coming back. Please read our post about it here.

What happened to the old server?
Please read our post about that here.

What about the APIs and other services?
For the moment, we are just seeing how SpamProtectionBot handles being on the server it's on. If we see that the server is doing okay, we'll bring other services back online but for right now it's the bare minimum.

Thank you for hanging with us through this wild ride, we're doing the best we can with what we've got! Open / Comment

2021-07-23 06:25:10 We’ll be back soon! We promise! Open / Comment

2021-07-14 17:30:53 GitHub issues

We've created a new repository on GitHub that will allow our fantastic users to engage with us even more by reporting bugs, feature improvements, questions, whatever it may be. We encourage our users to use this as a way to get issues known to us so that we can correct them or respond accordingly; additionally it will make it easier for us to reference existing issues/questions to other users experiencing similar issues.

We're looking forward to hearing from you!

https://github.com/intellivoid/issues Open / Comment

2021-07-14 05:08:56 Public Service Announcement

What happened?
Many things happened. The start of this began when it seemed like CoffeeHouse did wear out the NVMe our production server had. Our host however noticed this and performed data replication and replaced the failing NVMe drive on the background.

Later then, a few days ago, while we were diagnosing the respective network issues with the network administrator, we noticed something was terribly wrong with the systems. The reasons requests weren’t reaching the systems was because of filesystem corruption. We were reported on our side that we had no space and the filesystem itself was problematic. Noting how Linux networking functions, it won’t really work properly without proper space requirements being met.

After we noticed this we just went with the normal protocol of analyzing recovery options, but we noticed as well this wasn’t an issue with the filesystem of the respective systems, but the VMFS filesystem of our hypervisor (ESXi).

This alerted us to backup as much as we could from the live environment, which wasn’t successful because the hardware issued a NMI informing about the failure, and ESXi wouldn’t work anymore, apart from noticing the whole filesystem was unreadable.

What does this mean?
It will take us time to get back up and running again. Unfortunately this was total loss of the data on the system so we will have to restore from a backup we performed in June 2021.

Could have this been prevented?
Unfortunately, according to an official statement from VMware Enterprise Support, the filesystem corruption couldn’t be prevented since a bug was introduced after the data migration.

Don’t you have backups from a near date?

Yes, we do. Though it’s integrity can’t be trusted and this backup needs to be reconstructed, which may take more time than what it would take for us to bring the services back.

We apologize for this inconvenience and downtime! Open / Comment