Four of the bundled examples still produce a share link over Discord's 2,000 character limit, after the payload shrink in #43:
spotify 2398
netflix 2306
discord 2133
uber 2115
Everything else clears it, the largest of them at 1,999. A hand-built design with many nodes or a lot of annotation text will land in the same place these four do.
The failure mode is the problem rather than the length. Pasting an over-limit link into Discord does not produce a truncated link or an error, it silently becomes a message.txt attachment, and the recipient has to download a file and paste its contents by hand. The person sharing has no idea it happened.
What to decide
Whether a link that cannot be pasted should be created at all.
.breakscale export already exists and handles any size. A share button that says "this design is too big to link, export it instead" is honest about what happened. One that hands over a link which breaks in the recipient's client is not.
Against that: the limit belongs to Discord, not to the link. The same string pastes fine into a document, a mail, an issue, or a chat with a higher limit, and refusing to produce it makes the tool worse everywhere else to protect one destination.
A middle option is to produce the link and say what it is: a note next to the copy button when the result is over 2,000, naming the limit it will not survive. That keeps the link working where it works, and removes the silent part, which is the actual bug.
Not deciding here
Whether to add a backend. That was the other half of #36 and the numbers now argue against it: 19 of 23 examples fit, so storage would exist to serve the tail. It stays off the table until something makes the tail the common case.
Four of the bundled examples still produce a share link over Discord's 2,000 character limit, after the payload shrink in #43:
Everything else clears it, the largest of them at 1,999. A hand-built design with many nodes or a lot of annotation text will land in the same place these four do.
The failure mode is the problem rather than the length. Pasting an over-limit link into Discord does not produce a truncated link or an error, it silently becomes a
message.txtattachment, and the recipient has to download a file and paste its contents by hand. The person sharing has no idea it happened.What to decide
Whether a link that cannot be pasted should be created at all.
.breakscaleexport already exists and handles any size. A share button that says "this design is too big to link, export it instead" is honest about what happened. One that hands over a link which breaks in the recipient's client is not.Against that: the limit belongs to Discord, not to the link. The same string pastes fine into a document, a mail, an issue, or a chat with a higher limit, and refusing to produce it makes the tool worse everywhere else to protect one destination.
A middle option is to produce the link and say what it is: a note next to the copy button when the result is over 2,000, naming the limit it will not survive. That keeps the link working where it works, and removes the silent part, which is the actual bug.
Not deciding here
Whether to add a backend. That was the other half of #36 and the numbers now argue against it: 19 of 23 examples fit, so storage would exist to serve the tail. It stays off the table until something makes the tail the common case.