https://www.diyaudio.com/forums/tub...ing-value-coupling-capacitor.html#post5903091
"Image" in post #3 is really a base64 blob.
I decoded the image but the blob seems to have "stuck" the thread so there is no way to reply.
Why are members even able to "attach" base64 code?
"Image" in post #3 is really a base64 blob.
I decoded the image but the blob seems to have "stuck" the thread so there is no way to reply.
Why are members even able to "attach" base64 code?
Attachments
I'll fix it.
Edit... done. The link ran to thousands of characters in length which is why it froze.
Edit... done. The link ran to thousands of characters in length which is why it froze.
> the link ran to tens of thousands of characters
72,231 characters (I still had it open in text-edit).
However I see others were able to reply before the fix; so maybe a limit in _my_ browser?
This is twice in 2 days I have seen a base64 "image" here (and I think you were the fixer both times?). Is this a trend? (I see a lot of base64 blobs on Google Image, are members just drag/dropping?)
72,231 characters (I still had it open in text-edit).
However I see others were able to reply before the fix; so maybe a limit in _my_ browser?
This is twice in 2 days I have seen a base64 "image" here (and I think you were the fixer both times?). Is this a trend? (I see a lot of base64 blobs on Google Image, are members just drag/dropping?)
🙂 Would you believe it if I said this was quite a small one in comparison to some. 1.3 million rings a bell for a fairly recent one.
Different browser/OS do seem to handle things differently. In some cases a thread or page won't even load with a dodgy link like that, or curiously it can prevent other correctly attached images in other posts from displaying.
Different browser/OS do seem to handle things differently. In some cases a thread or page won't even load with a dodgy link like that, or curiously it can prevent other correctly attached images in other posts from displaying.
- Status
- Not open for further replies.