> This means in some sense RIPE's security policies reflect what European ISPs and similar wanted, for good or ill.
Traditional routing has always been very, very open. Like a club where anyone is welcome and if new folks mess stuff up it just gets fixed.
Several IRRs used to allow RPSL changes by email to their systems with only maintainer auth and no verification of route ownership (e.g. you register with the IRR, then publish Google routes).
It’s all getting hardened nowadays with things like no more email, layers of verification, RPKI, etc.
It’s not necessarily what folks want but how this stuff had traditionally been handled. Thankfully it’s all changing because of events like this.
Love it. I do think that the "learn" section should always be open. For me (FF) after the first challenge it's closed by default which leaves just a command line and no clear direction.
If you're working on code for most of the day, you will absolutely be making decisions that enhance your experience.
Could be an editor, monitor, chair, etc. It might not seem like some of those little things matter -- if I can sit in the chair, it works for me! -- but they do to some and typography is one of those things.
I don't understand folks who don't understand this. I get it if you don't personally care about typography but every developer is making QOL decisions.
You are pushing this idea so hard and blasting this thread with copy/paste comments. It's obvious you're excited about it and that's great but there is a lot that isn't shown and that's where the real work is being done.
Just because it looks like magic, doesn't mean there isn't someone pulling some strings somewhere else to aid the illusion.
You might give ActiveCollab a shot. I've spent 16 years going through various project/product management systems and it's one of the only ones that springs to mind when you mention sharing client access like that and trying to keep things user-friendly.
That said, if you're using the service desk stuff from Jira I might stay with it. I understand the pain of having to administer Jira and how it creates project-specific EVERYTHING on the backend (workflows, et al.) but it's great for end users and it's super flexible.
Traditional routing has always been very, very open. Like a club where anyone is welcome and if new folks mess stuff up it just gets fixed.
Several IRRs used to allow RPSL changes by email to their systems with only maintainer auth and no verification of route ownership (e.g. you register with the IRR, then publish Google routes).
It’s all getting hardened nowadays with things like no more email, layers of verification, RPKI, etc.
It’s not necessarily what folks want but how this stuff had traditionally been handled. Thankfully it’s all changing because of events like this.