Releases: thenetcircle/dino
Releases · thenetcircle/dino
Version 0.21.10
Version 0.20.0
Python 3.9 support.
Version 0.18.38
v0.18.38 tagging version 0.18.38
Version 0.12.39
- sentry integration,
- async queue posting,
- python 3.6
Version 0.12.3
Changes since 0.12.2:
- better socket api error codes,
- retry for external queue publish,
- remove channels in web admin,
- single admin room instead of one per channel,
- report messages,
- deletes the user's messages in the room when banned,
- remove rooms using socket api,
- temporary rooms; when the last owner leaves a room they created, everyone is kicked and the room is removed,
- rest api for set/unset super users,
- simple install and deploy scripts using systemd,
- invisibility for admins,
- lots of minor fixes.
Version 0.12.2
Changes since 0.12.1:
- second login will replace first login, based on user ID instead of IP,
- no user information for ban/kick events to users, they have the information already,
- event sent to clients when a new room is created,
- the user who is banned receives an event with details about duration and the reason,
- messages matching the blacklist are silently dropped, sender sees message as delivered.
Version 0.12.1
Fix release for 0.12.0, tests were failing.
Version 0.12.0
Changes since 0.11.0:
- many fixes and improvements
- test coverage to 80%+
- stats
- use statsd for metrics
- send successful login events and disconnect events to a message queue
- decouple api actions
- using hooks to respond to api events
- using plugins for validation
- docker
- include Dockerfile and documentation about how to run
Version 0.11.0
Changes since 0.10.0:
- invite
- invite user from other rooms
- base64 all free-text
- message body
- room/channel/user names
- request admin
- an admin room is automatically created when a channel is created
- request admin will send an invite to the admin room in that channel
- can make admins aware of potential problems in rooms
- whisper
- send message to only one user in a room
- identical to event "message", but set "verb" to "whisper" instead of "send"
- unique error codes
- so tests can know an api calls failed for the right reason, and clients can know what went wrong
- use defined response codes for front-end to be able to display correct error messages
- emit event on socket for kick/ban from ui
- when banning or kicking in the admin ui, a socket event will be sent to relevant clients
- rest interface
- get list of banned users
- get a list of rooms that a list of users are in
Version 0.10.0
Changes since 0.9.0:
- switched async engine
- using gevent instead of eventlet
- monkey patching sqlalchemy and psycopg2
- last read timestamp for group
- if online, store timestamp of last read message in group for user
- if later comes online, client asks for messages since last read timestamp
- backend admin interface
- for fixing things
- listing users in rooms
- list rooms in channels
- list channels
- create channels/rooms
- ban users
- kick users
- listing bans and remaining time, remove if needed
- create admin users manually
- manage list of admins as user ids
- change ownership/moderator status for users in channels/rooms
- redo permissions
- able to set different permissions on rooms/channels based on the api action
- ACLs on channels for who can create rooms in the channel
- e.g. some types of users can not join (channel or room), like paying members only etc.
- ability to choose to filter out rooms list, not displaying rooms that a user is not allowed to join