| Age | Commit message (Collapse) | Author |
|---|
|
otherwise pods can exist multiple times with mixed case
|
|
The unique index doesn't work when the port is `NULL`. So use `-1`
instead for when using the default ports (80/443), as if we would use
the real ports, we could still have both 80 and 443 in the database at
the same time.
|
|
|
|
|
|
Also remove authentication_token from database
|
|
|
|
If the migration contains a new remote_photo_path migrate all photos of
the old person to this path. If the person was local before, cleanup old
uploaded files of the photos.
closes #8314
|
|
|
|
That way it can be re-used when sending the AccountMigrations to other
pods again if a message for the migrated account is received.
fixes #7902
closes #8309
|
|
|
|
closes #8303
|
|
Enforce lowercase tags and migrate existing uppercase tags for Postgres.
|
|
|
|
|
|
|
|
As per discussion on https://discourse.diasporafoundation.org/t/removing-diaspora-s-current-chat-integration/2718, nobody raised serious concerns or objections. Given future plans, we do not think having an unfinished implementation of something that likely will not get finished in the current form is worth it. So let's get rid of it.
|
|
|
|
fixes #8043
closes #8044
|
|
This is not (and as far as I know, was never) used. If we want to make
standalone photos commentable, we can always add it back, but it would
also need to change federation for it to work, because comments support
only posts there. But for now it makes the code cleaner and easier to
remove it.
|
|
It doesn't add any security to have this encrypted, but it adds
complexity for podmins, because they need to backup the key.
closes #8014
|
|
closes #8012
|
|
|
|
|
|
|
|
closes #7944
|
|
Facebook removed the API and facebook integration is broken now, so lets
remove it.
closes #7874
|
|
closes #7822
|
|
Use completed_at datetime field as an indication of a performed migration
closes #7805
|
|
Previously we had only a Rails validation which ensured poll participation
uniqueness but this adds uniqueness control to the database level, so that
uniqueness is guaranteed even when changing data with avoiding Rails
validations.
closes #7798
|
|
This feature only worked on the same pod and was more confusing than
useful.
|
|
Some relayables from redmatrix and hubzilla have empty signatures. They
are invalid and break therefore the user data export.
closes #7644
|
|
Cleans invalid contacts where the referenced user was deleted from the DB or where
the referenced person owner was deleted from the DB.
closes #7632
|
|
When we should have the signature but don't have it, the user data
export fails. There are a few comments from back in 2011 where the
signature is missing.
Also some podmins maybe messed with signatures in their database, which
would also break the exports now.
closes #7637
|
|
closes #7630
|
|
There are a few old oEmbed caches which have the title saved in binary
(because they contain Chinese characters). This fails with
`ActionView::Template::Error ("å" from ASCII-8BIT to UTF-8)`. Since I
found only very old OEmbed caches with this problem (newest from 2012),
I think we can just remove these. When I create a new oEmbed cache for
the same URL it creates it without `!binary`.
closes #7620
|
|
|
|
closes #7614
|
|
|
|
This was added by accident in 4e18f3849dcc5d36bda93e68b597b869735d5517.
closes #7598
|
|
This was a leftover from rails_admin which was removed in #7440.
closes #7597
|
|
|
|
closes #7580
|
|
And cleanup old reshares with deleted root posts
closes #7578
|
|
This commit introduces support for AccountMigration federation message
receive. It covers the cases when the new home pod for a user is remote
respective to the recepient pod of the message. It also allows to initiate
migration locally by a podmin from the rails console. This will give the
pods a possibility to understand the account migration event on the
federation level and thus future version which will implement migration
will be backward compatible with the pods starting from this commit.
|
|
|
|
|
|
|
|
See #7234
|
|
|
|
|
