> 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.
1: Find logos you like, and a few from your industry.
2: Pick a few colors you like, and a few in your industry.
3: Pick a few fonts you like, and a few in your industry.
4: Find icons/shapes related to your business (google images: "[business type] icon" as a start, then branch from there based on what you find).
5: Mash it all together as many different ways a possible.
6: See what you like/dislike. Repeat as needed.
That's it, that's the secret. Get stuff you like and stuff that works and mash it together to see what happens. Then take your mash-ups and keep mashing and playing until you find something that fits. You don't have to love it, just get something that works. A lot of folks don't like their branding initially.
What designers won't tell you is that the process is sometimes just brute-forcing creativity and that's totally okay. You can't always feel inspired or have that "one perfect idea" and you've still gotta get stuff done.
1) Why are all buildings the same? Light switches are often in similar places and the space between the floor and ceiling is pretty standard.
2) Why are all vehicles the same? Mirrors are always in the same spots and seat belts all work the same.
3) Why are all laptops the same? Keyboard center on the bottom with a trackpad or nub near the center. Screen on top, ports and stuff on the sides.
There are components that are common in all facets of our lives that when different can cause problems or surprise which could be good or bad. We need to join two floors of a building. Use stairs! People understand stairs. We need to showcase a collection of clickable images. Use a grid! People understand link grids.
If you want to make your website usable you have to lean on expectations and those are pretty well defined nowadays. Imagine walking into a room and turning on the lights using a switch in the middle of the floor or plugging in your laptop's power cord at the top/back of the screen.
Most companies spending money on a website want them to feel fresh and creative and engaging but they also have to temper that with usability and expectations. That's why all websites "look the same" or at least why the author thinks they do.
Just because certain elements are in the same spot(s) or behave similarly doesn't mean things are the same. Or, at least, to me they aren't.
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.