Skip to content

Commit f510e7a

Browse files
ildyriad7415
andauthored
Update docs/releases.md
Co-authored-by: Martin Stone <[email protected]>
1 parent 1f67ec4 commit f510e7a

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

docs/releases.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -45,8 +45,8 @@ This fallback process has been extremely useful to us when we deployed the versi
4545

4646
One may wonder why we decided to do this change, and to that there are two big reasons:
4747

48-
- We no longer will need to maintain a legacy compatibility. Cleaning old code bases is part of the life cycle of a project, and we are now at the point where we can do this. The second reason is that we are planning to refactor the way images are attached to albums.
49-
- We decided to go in the direction of a many-to-many relationship. In layman terms, this means that a photo can be in multiple albums at the same time. This behaviour is not compatible with the API v1 definitions. This relationship change is going to have significant impact on the way photos access rights are handled, but we are confident this will also enable us to provide more interesting features in the future.
48+
- We no longer will need to maintain a legacy compatibility. Cleaning old code bases is part of the life cycle of a project, and we are now at the point where we can do this.
49+
- We are planning to refactor the way images are attached to albums. We decided to go in the direction of a many-to-many relationship. In layman terms, this means that a photo can be in multiple albums at the same time. This behaviour is not compatible with the API v1 definitions. This relationship change is going to have significant impact on the way photos access rights are handled, but we are confident this will also enable us to provide more interesting features in the future.
5050

5151
Now moving on from this 45 000 lines of code removal, we also simplified the way photos are shared. In the past in order to avoid hot-links we had to create symbolic links that expired. This was a bit of a hack. We now provide the option to use signed urls. This ensures that the photo is only available for a limited amount of time. Our SE users will also be happy to know that the url of the photo can also be encrypted, making sure that nobody can access the photo by guessworks.
5252

0 commit comments

Comments
 (0)