But why!
aaronsnoswell opened this issue · comments
:O Oh the horror!
Seriously, thanks for the laugh though :P You're on HN
Every day we stray further from god's light...
IFRAME + INPUT element = No JS (and doesn't lose chat history)
...except it would be much more user-friendly with keyboard support.
Actually this is extremely useful for privacy and security if someone was running a TOR browser with javascript disabled and wanted to use an instant chat. Only problem is its written in ruby 🤢
man I wish CSS/HTML had better options for variable URL names, could actually make this decently accessible.
IFRAME + INPUT element = No JS (and doesn't lose chat history) ...except it would be much more user-friendly with keyboard support.
Yeah this is a great point. Only thing is, then it wouldn't TECHNICALLY be an "instant" chat through things like TOR as things like reloading a page take a lot longer then receiving writes. I suppose having the received messages be through long-polling and the send message be through an iframe would be the best trade-off.
Only thing is, then it wouldn't TECHNICALLY be an "instant" chat through things like TOR as things like reloading a page take a lot longer then receiving writes.
Using an iframe for chat output (long polling) and an input (in another iframe, so the whole page doesn't reload) would be significantly quicker than this, no matter the connection.
This project sends a new request every keypress... er... key click. I suspect (but could be wrong) that this was more to highlight the possibilities of CSS, rather than designed to be a real world example.
Because it's the only messaging "platform" that works cross-platform from a DS if you don't have a phone but your friends do...