I came here to ask this exact same thing. Recently used Cactus to develop a pretty big static website. Plugins made it very fun and easy to build more complex cases. Thanks for the great work!
django-websocket-request doesn't really know anything about websockets specifically. The example I provided uses sockjs which provides websocket emulation and does upgrades to other methods if supported.
I did look into django-socketio when doing research, but never actually used it. django-websocket-request is way more simple, because it does way less and doesn't cover as much as django-socketio. For example, django-socketio is bound to only using socket.io, but it also includes a whole channel subscription and broadcast system so you can send messages from the server to specific channels. django-websocket-request only enables you to add a WebSocket layer over your already existing REST API / Views. I'll eventually have to look into doing things that django-socketio does.
This is always hard even when naming variables, functions, and classes. I always try to be as verbose as possible and sometimes spend like 10 minutes just pondering of a name.
I just noticed that and sent them a message about it. Thats definitely weird and not inviting at all. You can actually get more cloud servers once you signup.
I'm currently using Ubiquity SSD Cloud Servers and I'm happy with them, but still find it weird that its not that popular. Anyone else using them? Any difference between them and DO?