Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Links don't auto-record solutions if a / is added at the end #26

Open
edderiofer opened this issue Feb 2, 2021 · 2 comments
Open

Links don't auto-record solutions if a / is added at the end #26

edderiofer opened this issue Feb 2, 2021 · 2 comments

Comments

@edderiofer
Copy link

As per the title. Open any puzzle in the database (e.g. this one: https://twitter.com/efzoz/status/1356173867400785921). Edit the URL to place a / at the end (so https://puzz.link/p?icebarn/11/11/badpuzzlebadpuzzlelollol27437366336zzzj/ instead of https://puzz.link/p?icebarn/11/11/badpuzzlebadpuzzlelollol27437366336zzzj). Solve the resulting puzzle (identical to the original puzzle). The database will not mark this as a solve.

I suspect it may also be the case that these two different puzzles may end up having separate entries in the DB if someone posts a link with the / to Twitter.

@robx
Copy link
Owner

robx commented Sep 1, 2022

This seems fine to me. Does it happen often that the same puzzle gets posted with different URLs?

(It's not impossible to attempt to normalize the URLs, I just don't see that it's necessarily worth the effort.)

@edderiofer
Copy link
Author

I haven't yet come across such a case where two identical puzzles with slightly different URLs like this both end up in the DB, but it does happen sometimes that someone links e.g. https://puzz.link/p?icebarn/11/11/badpuzzlebadpuzzlelollol27437366336zzzj/ elsewhere (such as on Discord) when the URL in the database was https://puzz.link/p?icebarn/11/11/badpuzzlebadpuzzlelollol27437366336zzzj.

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

No branches or pull requests

2 participants