That may be quite close to the truth. Here are pictures from some abandones pavilions from the 2000 World Expo in Hannover. Sad to see this, as I lived in Hannover at that time and had a really good time at the Expo.
> The official Zen browser repo got flagged by GitHub, in turn its currently unavailable for you.
> There is no code loss, We just waiting on a review by GitHub.
> Also affected is Mods download, Binaries download, Docs website and Update-Server.
This is concerning because it suggests they somehow violated the terms of service. However, I wouldn't be surprised if it's a ploy by the project author to forcefully close all the opened issues again.
I'm assuming the project is burdened with technical debt yet again, since most of the bug "fixes" are just monkey-patches. They're mostly superficial, where the root cause is usually never addressed, which creates more issues when new features are implemented, this additionally causes many regressions, with previously fixed issues resurfacing.
This is completely unrelated to recent events. Before initial invasion in 2014 many Russian IT companies had huge presence in Ukraine and many Yandex services including search had localized versions and own search ranking, etc. Yandex still have versions for Belarus, Kazahstan, other ex-USSR countries and even Turkey. But chances for international expansion was pretty much destroyd by political situation.
Also keep in mind Yandex was different company a decade ago. Back then Ilya Segalovich been CTO there (he died of cancer in 2013) and he supported opposition and even participated in street protests in Moscow.
I'm the guy who made the Twitter post and wanted to clarify a few things because this Tweet keep coming back every year with the same comments.
1. About the thread:
First, I would like to say that this thread was purposely dramatic with the only goal to get a quick answer from Digital Ocean. We did not have a communication channel with them after their last ban email, and it was a way for us to promptly establish a communication through social pressure. And with hindsight, probably a bit of immature social-media revenge of creating a shitstorm on social media.
DO did not kill our company, they put us in an uncomfortable position. We did have two Fortune 500 clients at that time, but we had no critical data, just a few configuration variables that we were aware of and could probably recreate from our memory.
2. About the backups:
We had two database backup, DO automatic disk backup and a backup script that uploaded to DO object storage.
YES, IT WAS A MISTAKE to have all our data with a single provider. I've learned from this, and it was a valuable lesson for all the people that followed this story.
At the time, I was the only person with tech skills in a two-person company. My tasks ranged from UI/UX to NLP to DevOps, I had professional experience with frontend / backend, but it was my first role where I had to handle system administration. I think I did a fantastic job with it for a junior, outside not setting up multi-provider backups.
3. About what we did to get ban:
It really was a python script that had to process ~500k records and fuzzy match them against another DB with 1M records. It was pure business logic and nothing illegal / shady / or against DO TOS.
As stated in the postmortem, we did not have a payment history with DO, as we were still on free credit at this time. We had no malicious intent to avoid payment and had the mean to pay for what we used once the credit ran off.
4. About Digital Ocean:
I do not hold any grief against DO, it was a human a process error, it happens to everyone, big and small companies. What matters is that they fixed quickly, did a postmortem on it, and acted to prevent this situation in the future. Nobody got killed, no data got lost, and we all learned from this event.
Hope this clarifies the story a bit. And please stop harassing me about multi-cloud backups :s
As a person that has been watching this kind of horror stories from outside, I just wonder why people choose to make business with companies that have no human in the loop when stuff gets serious.
AFAIK, for AWS for example, when things get serious you are prompted to upgrade to a the big boi support plan (1.5k$/month) and are assigned a TAM (Technical Account Manager). In a situation like that, if you were running on AWS, a TAM or any human in general would have probably fixed the whole thing in like 30 minutes (if anything, because they would know you and that your usage is legitimate).
Tiptap is great, I made a few custom extensions for it to build an interstitial journaling app (https://heedful.app). The documentation is still lacking to some extent, but the source code is easy to understand.
