Howdy, Stranger!
We are about to switch to a new forum software. Until then we have removed the registration on this forum.
Categories
- All Categories 25.7K
- Announcements & Guidelines 13
- Common Questions 30
- Using Processing 22.1K
- Programming Questions 12.2K
- Questions about Code 6.4K
- How To... 4.2K
- Hello Processing 72
- GLSL / Shaders 292
- Library Questions 4K
- Hardware, Integration & Other Languages 2.7K
- Kinect 668
- Arduino 1K
- Raspberry PI 188
- Questions about Modes 2K
- Android Mode 1.3K
- JavaScript Mode 413
- Python Mode 205
- Questions about Tools 100
- Espanol 5
- Developing Processing 548
- Create & Announce Libraries 211
- Create & Announce Modes 19
- Create & Announce Tools 29
- Summer of Code 2018 93
- Rails Girls Summer of Code 2017 3
- Summer of Code 2017 49
- Summer of Code 2016 4
- Summer of Code 2015 40
- Summer of Code 2014 22
- p5.js 1.6K
- p5.js Programming Questions 947
- p5.js Library Questions 315
- p5.js Development Questions 31
- General 1.4K
- Events & Opportunities 288
- General Discussion 365
Forum error when posting (the one duplicating our posts..)
Usually I get a
String could not be parsed as XML
when I hit post. But the post is done anyway... I'm used to that :) But this time I got a different error message, so I'm pasting it here in the hope it helps fixing this annoying bug :P
this is it:
Error connecting to host: 48e7bc3c7a6a.rest.akismet.com Error number: 105 Error message: No buffer space available
Answers
Akismet is a PHP library to fight spam, based on some remote server, so if there is some connection issue between the two servers, it might result in rejected messages. Hopefully it is a temporary issue.
Well this might be something, I noticed that posting is much slower than just refreshing the discussion page. Perhaps the performance of kismet is confusing the forum program...
"(the one duplicating our posts..)"
Well, that's not the bug that duplicate your posts! That's the users seeing the error and hitting send again, without checking if the first message was actually sent (just a refresh of the page). But I admit the error message is confusing.