Re: Link rel=\
Reply #2 –
I envisioned the allowList as a list of Domains that the site wanted to allow following.
Example, if you had a fan site for Kia cars, you could put Kia.com in the allow list, or perhaps a site you were affiliated with that sold Kia parts, like kiastuff.com that you get a affiliate payment or whatever.
Going the membergroup permission route you would have to a) be in that group and then b) use a url like like [url url=somesite.com follow=true]yowsa[/url] and I just don't feel members would remember or bother to do that. There is also the complication of auto embedded urls which is, again my experience, what most member do (cut/paste). Those could be handled automagically with an allowList but not really with permissions.
Re: Link rel=\
Reply #3 –
Here is where I ended up on this.
All links by default get a rel="noopener noreferrer nofollow ugc"
If you allowList a domain you get rel="noopener noreferrer ugc"
If you have permission and use [url url=somesite.com follow=true]somesite[/url] you get rel="noopener noreferrer ugc" You can also set that to false to override the allowList on a per link basis
I'm thinking of dropping the noreferrer from the allowed to follow links, I don't see the harm with passing the site info to the link you are following.