ebfc248ff6
Fix OAuth and Realtime issues introduced in 9a515b9234eeb2e500e88899fb31f64535b618cc [DATABASE] Fix an empty default value mistake introduced in fde929b151f2b286cb60d226c47570209199c9c5 [DATABASE][PostgreSQL] Avoid use of pg_constraint.consrc, which was removed in PostgreSQL 12. [DATABASE][MariaDB] Fix a typo introduced in aed2344bd4c512dae48d1a5bd2eda218f914ae11 [DAEMON] Wrap an assignment inside "switch": a follow-up to adc689cb15d611c83ebb9c5aaeaa1008ec14da28
As of StatusNet 1.0.x, actual formatting of the notices is done server-side, loaded by AJAX after the real-time notification comes in. This has the drawback that we may make extra HTTP requests and delay incoming notices a little, but means that formatting and internationalization is consistent.
== TODO ==
- Update mark behaviour (on notice send)
- Pause, Send a notice ~ should not update counter
- Pause ~ retain up to 50-100 most recent notices
- Make it work for Conversation page (perhaps a little tricky)
- IE is updating the counter in document title all the time (Not sure if this is still an issue)
- Reconsider the timestamp approach