Jørn Wildt

And now we are bashing privacy issues, then I believe your recommended usage is just as bad. The code example starts with this line: And that is needed on ALL...

I could(!) reproduce it somewhat consistently on for instance https://solidrc.azurewebsites.net/home/login# which is running an older version of "login.html". But it is not easy - you have to use the old...

If it "works for you" then try running the new server version on localhost and add a couple of entries for 127.0.0.1 in the "hosts" file, such that you can...

I just tried a few logins on dev.inrupt.net (for instance https://aviana.dev.inrupt.net/common/popup.html) and PB blocks https://solid.community/.well-known/openid-configuration when I click "Login" and "Solid community". So the new server has the same issue...

Tried it and got: **** ACTION_MAP for solid.community elfisk.solid.community { "dnt": false, "heuristicAction": "block", "nextUpdateTime": 1543923490370, "userAction": "user_allow" } solid.community { "dnt": false, "heuristicAction": "block", "nextUpdateTime": 1544823052811, "userAction": "" }...

We still need to know why PB ends up with "heuristicAction": "block". My best guess is the "fetch" request to solid.community/.well-known/...

> I only see a problem with this. The self link of the error is tricky to implement as it's a "volatile" resource. Seems to me like a really good...

> Are you definately awaiting any async calls in your views/templates? Sorry, can't answer that - that is rather difficult to verify. > Is this an intermittent issue, or does...

Looking into "mganss", there error is here: https://github.com/mganss/HtmlSanitizer/blob/master/src/HtmlSanitizer/HtmlSanitizer.cs#L638 ``` private bool IsAllowedAttribute(IAttr attribute) { return AllowedAttributes.Contains(attribute.Name) // test html5 data- attributes || (AllowDataAttributes && attribute.Name != null && attribute.Name.StartsWith("data-", StringComparison.OrdinalIgnoreCase));...

> I don't see why there would be a concurrency issue with the HashSet unless it was being altered while the check was being made Now, I haven't experienced it...