New concept for eliminating compression (280 byte limit)

Nobody has claimed this yet.

I've put some thought into this over the 1000 or so dweets I've published and here's my suggestion, it's very simple.

Change the limit to 280 bytes. There are many benefits to this...

- Since bytes are counted rather then characters, unicode character compression would no longer be necessary.
- Makes it much easier to newcomers to understand what is going on.
- Legacy dweets are still be allowed, most will probably be below 280 bytes.
- Special category/icon for dweets that are 140 bytes or less called "half dweets".
- All current uncompressed dweets would fall into the category of half-dweet.
- You can sort by full or half dweets.
- Breathe some new life into dwitter, let's see what else is possible with more code.
- New challenges to fit things without using compression, maybe there are new tricks we can discover.
- Get more exposure for dwitter because we would be able to make cooler stuff.
- We can still keep the uncompress button to show up for legacy dweets. Or maybe it would make more sense to just automatically uncompress them.

That's my idea! It's pretty simple, just a change code length to be counted by bytes and up the limit to 280 (needs to be changed on both front and back end), old dweets will still work.

Start by tracing how dweet length, compression, and legacy uncompression are handled on both the front end and back end. Review the existing behavior for current dweets and the proposed 280-byte and 140-byte limits. Done should preserve legacy dweets while consistently enforcing the new byte-based limit and supporting the requested half-dweet behavior.

Written by the indexing model from the issue text.