Deprecate riot.data.coop #161
Labels
No labels
Blocked
Existing Service
Infrastructure Issue
Refactor
Security Hardening
Security Issue
Service Idea
Service Removal
Upgrade service
No milestone
No project
No assignees
4 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: data.coop/ansible#161
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
We should deprecate the domain
riot.data.coop
used for Element Web. There's no need to have two domains for the same service, and the name 'Riot' isn't the application's name anymore.We can use HTTP 301 for a month and then remove it?
Sounds like a good idea 👍
It is worth having in mind that existing logins for matrix through riot.data.coop will not work on element.data.coop. That is, users using riot.data.coop would have to log in again on element.data.coop resulting in a new session. This is rather annoying (it took me quite some time before I migrated to element.data.coop because of this).
I think that we should announce that we are removing riot.data.coop and set a date for when we remove it. This way anyone using it should have time to move over to element.data.coop
@valberg I think that's a good approach, that'll make everyone happy.
The domain was removed in #178.