
If you read my post from yesterday, you know that I ran into a sort of snafu at the end of it. If you didn't see it. You can check it out here. As I was getting ready to wrap up my post with a few more photos, I got an error message that I had reached my limit of photo uploads or that I only had a certain amount left and the photo I was trying to upload was too big.
I wasn't sure if it was a HIVE issue or a PeakD specific issue, so I jumped over to the PeakD Discord server and asked about it. It wasn't as immediate as I expected, but a short time later, I had a ticket opened on the server by @asgarth. I wish I had taken a screenshot of the text exchange now, but the TL:DR of it was that "asgarth" was offering me help.
I was immediately skeptical, so I took a look at the profile and noticed that "asgarth" only shared one server with me which was the PeakD server. That seemed weird, since both @asgarth and I have been on the chain for quite some time now, it seems like we probably would have more servers in common than than.

I explained that I was getting an error message and then "asgarth" gave me a big long explanation with all kinds of meaningless fancy words. Like I said, I wish I had taken a screenshot so you could see how ridiculous it sounded. Once again, the TL:DR of this part of the exchange was that I needed to manually reset my HIVE account and he would be more than willing to help me with that.
Of course you would!
I had already looked in some of the other servers and noticed that @asgarth and I actually shared five servers in common, so if there was still any doubt that this was a scammer (which there wasn't), it was verified after that. Needless to say I tagged the real asgarth, closed the chat, and waited for a reply.
Sure enough, later in the day, I got this explanation from the real asgarth:

Obviously, I understand why they are doing this, but it's going to be a bit of a bummer if I am going to start being limited to how many images I post on HIVE at one time. Like I said yesterday, I already cut the size of my images down by 40% to make them load faster and take up less space on the servers, but if I have to cut them down anymore, or use less of them, I am worried that the quality of my blogs might suffer.

Of course, I'm not jumping the gun just yet. As you can see from the message, it's just something they are starting to monitor. I don't think there are any real hard and fast limits at this time, but it's something that we might need to be acutely aware of in the future. If you don't already resize your photos before posting them on HIVE, you might want to start doing that. You might need to start doing that.
It also might mean I need to be a bit more selective about the photos I share on HIVE in the first place. Of course, I could always use a different front end, but I really like what PeakD has built, and while I feel the DHF ask might be a little inflated, I do appreciate what they do for the blockchain.
As you can see, I am posting the rest of the photos that I didn't get the chance to share yesterday in this post today. I figured it was the least I could do.
Have you gotten the same error I got yesterday on HIVE? Do you plan on changing how you post or what front end you post with because of it?
Let's talk about it in the comments!

I saw your query yesterday on discord, but didn't see the scam one. Great one on spotting the scam, too many of them around now.
My posts are quite image heavy even though I try to restrict them, hopefully I went get this problem as having to resize them is a lot of work
They made an update and the limit is higher now. You can also check your limit in the post creation screen. I use a program that batch converts all my images, so I just put them in a folder, then press a button. It can resize a couple hundred photos in a minute or two.
Hey, higher upload limits are already live. Give it a try and let me know if you still notice this problem.
BTW there is a small new thing here that you can use to verify the daily upload limits for your account:
I had just clicked publish when your message came through on Discord. I'll be sure to point that out in my post tomorrow. Thanks for the update!