APIsex: API security for elixir

That’s of course your prerogative. But I’d just like to say that many of us are simply trying to build this community on (and in fact it was started with) the principle of being considerate and mature. This is reflected in the Elixir CoC and these are the sort of ideals that we strive for on the forum.

Sticking to these ideals of course also helps ensure the focus remains on the library itself rather than its name, as well as increases the chances of it being adopted and used by others - which is something I’m sure most library authors would prefer.

As the OP has stated he is going to rename the library (and is welcome to post a new thread once he’s done that) I think it’s time to close this thread. Thank you @tangui and thank you everyone who left feedback

Offended virtue signalling people offend me says person virtue signalling on forum.

I hope You don’t believe I am offended

Fantastic - thanks @tangui

Feel free to post a new thread thread in this section for it when you’ve changed it

Will change to something more neutral like APISec as suggested!

Also this is part of a bigger project I’m working on and as far as I seen few people use external OAuth2 servers, so I published that just in case it’d be useful to someone out there but there already are plugs for 99% of common use-cases (cookie-based, JWT based, etc.). So lesson learned: not being to playful with lib names

Also, I remember talking to architects about API Gateways and they actually quite often ended up having an instance of the API Gateway installed on each API instance, especially in micro-service / docker deployment contexts. And these API gateway instances mainly did security stuff (also cache and SLA management). So I’m wondering if on Erlang/Elixir stack API Gateways are needed at all.

HAPPYsex…?

but seriously, there are far too many people getting offended at the possibility of someone else finding the name offensive. There’s another thread about why people are leaving Elixir and the community of SJWs and virtue signallers is high up on my list.

You really should change your library name…

What about Happy instead of API?

The consensus seems to be: please change the name. Make it APIXex, that would be my preference. Can be read X as in cross and ex same as elixir extension. And, it can be read as sex still.

If i as an employer Chose this library and some intern or woke person would see this. I`d be having focus on something else than getting work done. Also I’d second this Ningi’s comment as people do get fired for this. Also, some programmers have wife’s that are not technical

And just to point out , you haven’t gotten a single serious reply on what you were asking for. The code, the library itself.

When choosing a name for your library, please consider search engines. There is a package I quite like called “assertions”. Try to google “elixir assertions”, no chance you will find it o the first 3 google pages. “API sex”, I don’t want to have in my search history to be honest. Avoid words like “sex” “boob” “cock” “dick” or anything along that line if you want your library to be used.

Edit: to clearify, I don’t have a problem with porn, sex, homosexual intercourse, dickpicks or anything someone might bring up. I just do not want to use the keyword “sex” in the search engine I use for work. Because that will lead to other things showing up when I search for api. Or sex. Don’t judge me.