Skip to content
This repository was archived by the owner on Feb 5, 2024. It is now read-only.

Use snowflakes #8

Closed
spotlightishere opened this issue Dec 3, 2017 · 8 comments
Closed

Use snowflakes #8

spotlightishere opened this issue Dec 3, 2017 · 8 comments

Comments

@spotlightishere
Copy link
Contributor

spotlightishere commented Dec 3, 2017

It's been discussed to use snowflakes.
Observe the following:
Screenshot of database

If we used a snowflake, we could strike mail_id and timestamp out with one INT(18).

@spotlightishere
Copy link
Contributor Author

https://github.com/bwmarrin/snowflake seems like an extremely good candidate.

@spotlightishere
Copy link
Contributor Author

This would still be nice to have. We potentially could eradicate meaningful message IDs. A migration plan should be made.

@Artuto
Copy link
Contributor

Artuto commented Nov 1, 2020

image

@Artuto
Copy link
Contributor

Artuto commented Nov 1, 2020

Thats not even what it was suggested for

@KcrPL
Copy link
Contributor

KcrPL commented Nov 2, 2020

What kind of sorcery is this?

@larsenv
Copy link
Contributor

larsenv commented Nov 2, 2020

What a great way to revive an issue that was made 2 years ago. 🙄

@larsenv
Copy link
Contributor

larsenv commented Nov 2, 2020

By the way, snowflakes suck. Although we don't use it, each piece of mail has 2 UUIDs to associate the mail with, so we don't really need snowflakes.

@larsenv larsenv closed this as completed Nov 2, 2020
@spotlightishere
Copy link
Contributor Author

spotlightishere commented Nov 2, 2020

Primarily, snowflakes (if used) would coincide best with #5 and #6, in which the mail system formulates mail to be delivered, stripping most user-provided content that could be abused (i.e. various headers). Obviously this was never implemented, but it may be worth keeping it open or mentioning within #5 as a design hint in case such ever happens.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants