Would a publicly accessible web-forum that permits ink-based posts as GIF files run into unmanageable spam problems?
Would the problems be mitigated if ink was publishable in a more recognizable and benign form such as XML? Seems like it would be.
Would a publicly accessible web-forum that permits ink-based posts as GIF files run into unmanageable spam problems?
Would the problems be mitigated if ink was publishable in a more recognizable and benign form such as XML? Seems like it would be.
Maybe the GIFs could be verified as containing ink using the ink data stored in them. I haven’t tried it — just a thought.
Good idea.
If your question is “What if people upload spam / porn images” I don’t think you’re going to be able to avoid that possibility just by converting the ink to an XML format such as, say, SVG. As far as content goes, I don’t think there’s a magic bullet solution other than membership and moderation.
What I’m planning to do on InkPositive is store pages / blogs / wiki pages content in both ink and “flattened” to a graphics. Since browsers send up a list of MIME types they can render with every request, it’s a simple matter to send down ink if the browser understands ink, and a graphic if the browser doesn’t.