Parsers often look for a node.data_type of url.path.segment in their gating logic. When the url.path is just one segment long, it isn't broken up into segments, so this logic skips it. This can lead to parsers not triggering when they otherwise should.
Example:
https://infosec.exchange/@RyanDFIR -> username isn't parsed out, as it looks for url.path.segment
https://infosec.exchange/@RyanDFIR/114031098984852327 -> username is parsed, as the relevant part is broken down into a segment.
It'd be possible to fix this one example, but I imagine this occurs many places and a more systemic fix would be better.
Parsers often look for a
node.data_typeofurl.path.segmentin their gating logic. When the url.path is just one segment long, it isn't broken up into segments, so this logic skips it. This can lead to parsers not triggering when they otherwise should.Example:
https://infosec.exchange/@RyanDFIR -> username isn't parsed out, as it looks for
url.path.segmenthttps://infosec.exchange/@RyanDFIR/114031098984852327 -> username is parsed, as the relevant part is broken down into a segment.
It'd be possible to fix this one example, but I imagine this occurs many places and a more systemic fix would be better.