Bug overview description.
Links ending with "/" used to indicate the end of a external link.
Now something has recently changed and that isn't the case anymore, this resulted in a lot of links (particularly from my own posts' descriptions) to become broken if their ends have syntax like

[/b]

or

[/i]

.

What part(s) of the site page(s) are affected?
Post descriptions for me afaik.
Edit: Post comments, Wiki pages

What is the expected behavior?

[b]"Example":https://www.google.com/[/b]

Example

What actual behavior is given instead?

[b]"Example":https://www.google.com/[/b]

Example]

Time of incident (if applicable).
21:32:26 UTC
Friday, 15 February 2019

Can you reproduce the bug every time?
Yes.

What steps did you take to replicate this bug?
Just try creating a link with an additional syntax behind it without spacing.

Errors or other messages returned (if any).
None.

https://e621.net/comment/show/3797860

I guess that's why my comment currently looks this way at the end.

Cane751 said:
https://e621.net/comment/show/3797860

I guess that's why my comment currently looks this way at the end.

Odd, I'm getting 403 Access Denied errors.
It's your comment on post #1509345, yes?

Seems to be affecting comments as well. :/

TheGreatWolfgang said:
Bug overview description.
Links ending with "/" used to indicate the end of a external link.
Now something has recently changed and that isn't the case anymore, this resulted in a lot of links (particularly from my own posts' descriptions) to become broken if their ends have syntax like

[/b]

or

[/i]

.

What part(s) of the site page(s) are affected?
Post descriptions for me afaik.

What is the expected behavior?

[b]"Example":https://www.google.com/[/b]

What actual behavior is given instead?

[b]"Example":https://www.google.com/[/b]

Time of incident (if applicable).
21:32:26 UTC
Friday, 15 February 2019

Can you reproduce the bug every time?
Yes.

What steps did you take to replicate this bug?
Just try creating a link with an additional syntax behind it without spacing.

Errors or other messages returned (if any).
None.

you're formatting it wrong, it's

"[b]example[/b]": https://www.google.com/

example

not

[b]"Example":https://www.google.com/[/b]

Example]If you add to a URL the added context becomes apart of the URL, which coud either brakes it, or makes it a dead gateway. Lest the gateway has formatted in added context like twitter.

Cane751 said:
https://e621.net/comment/show/3797860

I guess that's why my comment currently looks this way at the end.

https://e621.net/comment/show/3707880%3C/span%3E.[/spoiler
Stop. Think. Follow these wise words: Don't feed trolls]intended effect:

[spoiler]Stop. Think. Follow these wise words: "Don't feed trolls[/spoiler]":https://e621.net/comment/show/3707880 

Versperus said:
you're matting it wrong, it's
"[b ] example [ /b]": https://www.google.com/
example
not
[b ]"Example": https://www.google.com/ [ /b]
Example]If you add to a URL the added context becomes apart of the URL, which coud either brakes it, or makes it a dead gateway. Lest the gateway has formatted in added context like twitter.

The old formatting used to work, now since it has changed everything broke.
Welp, the new way of formatting seems make it a tad bit complicated now.

Now I have to do this,

[b]Please support the artist[/b] "[b]here![/b]":https://www.google.com/

instead of

[b]Please support the artist "here!":https://www.google.com/[/b]

to get this,

Please support the artist here!

TheGreatWolfgang said:
The old formatting used to work, now since it has changed everything broke.
Welp, the new way of formatting seems make it a tad bit complicated now.

Now I have to do this,

[b]Please support the artist[/b] "[b]here![/b]":https://www.google.com/

to get this,

h6.Please support the artist "Here":https://www.google.com/ 

Please support the artist Here

Versperus said:

h6.Please support the artist "Here":https://www.google.com/ 

Please support the artist Here

Headers could work for bold text, but it would be still be the same case if I wanted to italicize the sentence.

I know you can also just format it as

[b]Please support the artist "here!":https://www.google.com/ [/b]

to get the same effect, but that's not the main issue.

The main issue is that a lot of older post descriptions and comments* that are caught in this bug now need to be reformatted.
^{*old comments cannot be edited}

Versperus said:
Ironically enough, the way you built it still ended up working though, because it makes it look like you trolled people into clicking the link

It's weird. I know for sure I typed [/spoiler] at the end.

Cane751 said:
It's weird. I know for sure I typed [/spoiler] at the end.

you did, it connected to the link.

Cane751 said:
It's weird. I know for sure I typed [/spoiler] at the end.

As mentioned above, ye gotta put the last bit in the quotation marks. It doesn't matter if the first bit isn't.

\Text part - "Link part":\/comment/show/3797860

    ↓

 
   Text part - Link part[/spoiler]

Reading all of this just makes me question why is this even in use to begin with.
Markdown is good for IMs, Bbcode is already semi-standartized system for forums and sites, so why make bastardization combining worst of both worlds?

Unfortunately this was changed as part of a security fix, so it was done quickly and resolving it was more important than ensuring that it was compatible with existing dtext.

I'm pretty much on board with Mairo at this point, I really really hate DText because it is not regular or predictable and there is an enormous amount of conflicted syntax happening all at once.

When I get more time I will see if I can resolve some of the pending issues surrounding links and nesting of syntax.

Mairo said:
Reading all of this just makes me question why is this even in use to begin with.
Markdown is good for IMs, Bbcode is already semi-standartized system for forums and sites, so why make bastardization combining worst of both worlds?

• You haven't thought systematically about what is needed. "We need a formatting system. I have some ideas for a formatting system!"
• Of course your system is better, it will have exactly the things that are needed and (subtly fail to) work in exactly the way that is needed.
• You lack experience and thus your judgement of what a good design is is lacking. You don't understand how important robustness is, not that that would help because you don't know what specific qualities create robustness anyway.
• You regard your system as usable because you personally understand how to use it.
• Just implementing someone else's spec is boring and gives no opportunity to inflate your own ego.

Hey, I'm not sure if this specific issue has been mentioned, or if it was even caused by the DText update, but I noticed something odd with trailing periods. It appears as though text is treated differently when it ends with certain characters, this behaviour changes further when there is period after that character.

("index":/post/index)
{"index":/post/index}
["index":/post/index]

("index":/post/index).
{"index":/post/index}.
["index":/post/index].

(index)
{index}
[index]

(index.
{index.
[index.