Make this repository obsolete #18
Labels
No labels
bug
confirmed
critical
discussion
documentation
enhancement
merge-upstream
suggestion
support
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
babka/mastodon-babka#18
Loading…
Add table
Add a link
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?
Check out the newest version of Mastodon+Glitch, see that all our patches (i.e. ToS) are now included upstream and upgrade babka.social to the new upstream Mastodon +Glitch image.
assigned to @CSDUMMI
I was almost done writing the update instructions for switching from Mastodon +Babka to Glitch, until I found what I think is a deal-breaker for us with the new Terms of Service feature of Mastodon.
The update process was pretty smooth. I'd setup a server using Mastodon +Babka v4.3.8 and after switching the image urls to glitch and runnig pre- and post-deployment migrations in accordance with the v4.4.0 update guide, the server started on glitch without any problems.
After having a working Glitch server up and running, I tried to add terms of service using the new ToS managment feature of Mastodon. I was able to copy and paste
config/tos.htmlinto the right fields, set an effective date (which had to be at least today) and was given the option to notify existing users with an email of the "new" ToS.Then I tried to sign up as a new user. As it turns out: New users are not required to accept the terms of service before sign up.
That'd be a huge step back from our current, hacky ToS which are presented as scroll-through to any new sign ups and are required prior to sign up.
I'll follow the usual update procedure for now. @emacsen should we report this as a bug to Mastodon and wait for them to add a second checkbox to the sign up for now?