If a user tries to submit a dweet that already exists (i.e. the code is the same), then that dweet should not be accepted as a new dweet, and the user should get a message explaining why

Have a list of users with top accumulated "awesome"? And/or average "awesome" / number of dweets?

When a user posts a new dweet he should receive some kind of positive message about the new dweet. F.ex. "Great! If you want to show off your new dweet, share the following link:"
<shareable link>

Example:

I often find myself wanting to refine a dweet I already posted. For example I want to make them shorter, faster or fix a visual bug. I want to update my existing dweet instead of deleting the old obsolete dweet and posting the refined version as a new dweet. This is because I don't want to lose the likes the dweet had and i also don't want to break the shareable link the dweet had

https://docs.djangoproject.com/en/1.9/topics/pagination/

Something like the reddit ranking algorithm or hackernews ranking algorithm.

Currently leaning towards the reddit one, as the values doesn't decrease over time, meaning you only have to recalculate the score for a single post every time it gets a like.

Use arkt.is encoding :)

When posting a dweet, allow a description that is posted as the first comment. This comment should then be "sticky" and emphasized.

j/k for up and down would be nifty

When a new user arrive dwitter at a link like https://www.dwitter.net/d/123 he/she may understand why the code works, because functions like ´S´ don't seem to be defined. Therefore it would be helpful to have an explanation of variables and functions on that page, just like on the front page.

... so that the score of the new dweet isn't calculated, and the dweet doesn't appear somewhere near the top of the hot list

When I click share, I see an input field with a url. I want this url to be selected when I click the input field.
According to stackoverflow, that isn't too difficult to implement:
http://stackoverflow.com/questions/3150275/jquery-input-select-all-on-focus

This is only on the client side, so a refresh removes it. Still, should be fixed

Even though dweets stop running, they still fill up memory, after scrolling through a couple I easily hit 1GB memory usage on a dwitter tab. Solution would be to free/unload dweets after they have been scrolled away from (say 2 dweets out of screen)

A mode that doesn't run the demoes so you could delete infinite-loop demoes

Attempting to reset you password results in a Server Error (500)

... because the comment input and submit button doesn't seem to appear on those dweets

Gotten some feedback that the fullscreen-link should open in a new tab. Seems like a good idea and easy to implement.

id.scene.org/docs/

In a dweet like http://dweet.dwitter.net/id/246 I used newlines instead of ; for readability purpose.

Problem 1: I am on Windows, hitting Return on a textarea apparently inserts a CRLF. So the site counts 2 characters instead of 1, which isn't economical... :-/
Somehow, there should be a replacement of CRLF by LF internally (and back, if needed).

Problem 2: HTML of textarea forces row="3", so I can't resize the area (on Chrome, at least).

Problem 3: HTML relies on maxlength="140" to ensure the dweet is legal, but as said, it counts end of lines on Windows as two chars. If JS can't fix s/CRLF/LF/, perhaps the limit should be enforced by JS only? With special handling of CRLF sequence, of course.

Problem 4: character counter counts EOL as one char, so we can be stuck at 136/140 when we have 4 EOLs... Puzzling at first.

Cascading deletes? :(

....

Relevant issue: sigvef/arktis-tweet-demo#4

A bug was recently introduced (perhaps by #42): When I try to comment (as staff), I get the confirm that normally pops up when I click delete dweet

Replies should also be demos. Perhaps let a user play with any dweet with the option to post it as a reply

For example, if Froff comments a dweet by lionleaf, the username Froff will become a link that leads to lionleaf's page. Expected behavior: Link leads to Froff's page.

This is not a problem for comments that are placed in the DOM by JS

Should be a "loading ... " when at the bottom to indicate that more items are about to load.

Also consider a fall-back link to manually load more

Using fullscreen APIs to fullscreen the actual canvas instead of opening a new tab

Suggestion: Django-compressor

Dweets that have been made by editing another dweet should indicate it's a remix and link to the original.

Behavior in Chrome: Infinite scroll doesn't work at all
Behavior in FireFox: Infinite scroll loads one new page, but not pages that should come after that

After I submit a comment and the field is automatically cleared, validation kicks in and the field becomes red (browser: Firefox). This isn't a defect per se, but it's slightly distracting.

If one could reset the form into a "pristine" state after submit, that would probably fix the issue.

Or maybe the novalidate attribute could help? http://stackoverflow.com/a/31170547/2319697

This might allow infinite scroll too!

Add a page that explains how to get started

• Some basic techniques (how to draw a filled rectangle, a line, an arc, how to color them, how to draw multiple things, how to clear a frame etc.)
• Examples of the techniques mentioned
• A few words of advice on how to avoid getting in an "infinite loop" state (be careful when editing a for loop)