-
Notifications
You must be signed in to change notification settings - Fork 85
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
JSON Blob is undergoing some server maintenance. Sorry for any turbulence. #83
Comments
same here. |
@tburch can you please look into this :( |
Hi, @mawais91 and @Prabesh01 Do you have IDs? There have been some people abusing the API, which caused it to lose some data Monday afternoon through Monday night (US time). |
Yes @tburch I do have ids of blob I use in my applications.. |
Yeah I too have. |
@mawais91 @Prabesh01 can you email those to my Github username @jsonblob.com? |
@tburch i have just sent you email that contains ids i am using. |
@mawais91 and @Prabesh01 this should be fixed. Please re-open if it's not. |
@tburch And I noticed that you changed new blob ids from random alpha-numeric to numbers. Why so? |
@Prabesh01 can you elaborate on blobs not being saved? As far as I can tell, both the UI and API are working as expected (the UI just uses the API).
The blob IDs have changed throughout the years... at first, they were MongoDB ObjectIds, then type-1 UUIDs, and now they're SnowFlake IDs. I made the change to support running more than 1 instance of JSONBlob to avoid type-1 UUID conflicts on object creation. |
Here's a blobs I am not able to edit and save: https://jsonblob.com/b8dc3f9f-cb86-11eb-84c9-3b6f8e6f54e3 More blobs I am using have this issue, am just sharing one. |
@tburch |
@tburch |
Interesting. I can confirm it's not saving. I'll take a look and see what's going on. |
OK Update the progress in #91 |
@Prabesh01 fixed #91. |
I had few links on JsonBlob those were live from quite long time. Now I am getting 404 against those links. Any kind of help would be appreciated. Thanks
The text was updated successfully, but these errors were encountered: