mwalser

It's interesting to see that the UX issues that are annoying me when using Azure DevOps are finding their way into GitHub.

In case they are truly chasing Azure DevOps level UX, I would recommend they implement an HTML editor for issues that, depending on whether the user has dark mode or light mode enabled, saves some CSS of the respective mode and makes it unreadable if read within the other mode.

Ah, thanks for the link.

While I don't remember seeing the notification, I think a yearly (!) system notification doesn't exactly qualify as pestering.

I'm using KDE as my daily driver and haven't noticed any ads so far. Where can I find these pester-ads?

And the naming restrictions and maximum name lengths are all over the place: https://learn.microsoft.com/en-us/azure/azure-resource-manag...

Storage accounts are one of the worst offenders here. I would really like to know what kind of internal shenanigans are going on there that prevent dashes to be used within storage account names.

> If I read it correctly (but could be mistaken), it runs with setuid root

I am certain you are mistaken. I couldn't find anything that hints at notepad running with elevated privileges.

I wouldn't say that multiple implementations are duplicating the attack surface since most users will not end up running them in parallel.

The debian security announcement for stretch says

> For the oldstable distribution (jessie), this problem will be fixed in a separate update.

You can check https://security-tracker.debian.org/tracker/CVE-2017-5754 whether the KPTI patch has been released for jessie.