Griatch

> For arbitrary data, adding a JSONField to the core models would solve these specific needs just the same. I'm pretty sure a JSONField is postgresql specific, so that won't...

@strikaco, @TehomCD I have a prototype for a `Link` model of the following form: ``` Link: key (str)

@strikaco Messages and Channels have specific usages. The point here is that `Tags` are _definitely_ not meant for such storage and still you (and others) find it necessary to use...

@strikaco - I'm open to alternative name suggestions to `Link`, but it's not a `bucket` or `group`. Maybe `Collection` but ... not sure. - The idea is to have `.data`...

Yes, I know about the advantage of JSONFields, I use them daily for postgres. Unfortunately, from what I read, you need to compile sqlite3 especially to support Django 3.2's JSONField....

While I have a working prototype of this, I'm stalling development of Links/DataLinks/Whatever for now. Too much new stuff going into next release as it is.

`recommonmark` provided a `url_resolver` feature, where one could provide a custom handler to pre-process whatever is parsed as the url. ``` def url_resolver(url): ... return url ``` This made it...

@chrisjsewell While one can achieve the outcomes like you suggest, it requires quite a lot of changes to (in my case) vast amounts of already written Markdown documentation using `recommonmark`....

@jpmckinney I don't expect `[hyperlink text](issue:123)` to carry any particular meaning at all out of the box. With `url_resolver` it would be up to me to parse the string `"issue:123"`...

@gtaylor Don't think anything was done on this. Something for Hacktoberfest maybe? ;)