nitnelave

6 ms·

31.
by nitnelave 3y ago
My wife's last name is only 2 letters long. Some websites don't accept that as it's too short (take that, Xi Jinping!) Conversely, I've had to fill forms in Korea that included space for only 4 letters, including both fi
32.
by nitnelave 3y ago
It's kinda what Rust forces you to do, except that std::move is implied. Anything taken by value is equivalent to taking by && unless the type is explicitly marked as Copy (i.e. it can be trivially copied and the copies are imp
33.
by nitnelave 3y ago
I wrote LLDAP ( https://github.com/lldap/lldap ) after struggling to install and configure openLdap on my homelab. It's a simple and light LDAP server that only handles users and groups (which is all you need on a h
34.
by nitnelave 3y ago
I like the expression "Bad News Fast": it gets the message across very efficiently, and if it's correctly incentivized (even just verbal praise) it can be a powerful tool to have an accurate view of the situation.
35.
by nitnelave 3y ago
To all the great answers here, I'd add another use case: sharing a password securely with family/team, and keeping it up to date when changing. I set up my family in a bitwarden organization, and I can share a password with severa
36.
by nitnelave 3y ago
Yes, in new code you should be able to replace almost all new and delete with unique_ptr, vector or, more rarely, shared_ptr. Placement new can still be useful, but delete not really. There are some patterns where you use new without a dele
37.
by nitnelave 3y ago
Leave it to a French revolutionary to theorize about the decomposition of a group into left and right Cosettes
38.
by nitnelave 3y ago
Have you had a look at LLDAP for a super simple LDAP backend with SQL behind? That or kanidm if you want OIDC built in.
39.
by nitnelave 3y ago
For single operations, maybe (and still it's a style, you get used to it), but the value comes from chaining. For me, the user/ageNext example is much more readable with monads. That might also be because I'm used to monads w
40.
Lldap Release 0.5.0(github.com)
2 points by nitnelave 3y ago|0 comments
41.
by nitnelave 3y ago
You could argue that an implementation of a function to which you added asserts to make sure that logical invariants are maintained is different from the implementation without. The asserts will never trigger because they enforce properties
42.
by nitnelave 3y ago
As a side note, I actually do use an ORM to support multiple databases with LLDAP, since it's a self-hosted application that can be used with either SQlite (for the most light-weight), or PG/MySQL for a more HA-friendly setup.
43.
by nitnelave 3y ago
Note that if you want to use KeyCloak for the OpenID but want to still have a LDAP source of truth, you can use LLDAP + KeyCloak together, with LLDAP as the source of truth and KeyCloak giving you the fancy features: https://gith
44.
by nitnelave 3y ago
LLDAP author here, I'm glad to see it's useful! A homelab is exactly the use case it was built for, and low resources is among the goals.
45.
by nitnelave 4y ago
I'm planning on continuing this vulgarization series of "Simply explained", for instance to cover how computers communicate, keep an eye out for them! Regarding the speculation/destroy society, I was directly answering q
46.
by nitnelave 4y ago
I was trying to keep the article at a level that everyone understands, from middle school up. I thought about going a bit deeper in the structure and mentioning attention, but my problem is that the intuitive concept of "attention&quot
47.
Simply explained: How does GPT work?(confusedbit.dev)
410 points by nitnelave 4y ago|382 comments
48.
Binance suspended withdrawals for intitutional accounts(twitter.com)
3 points by nitnelave 4y ago|0 comments
49.
Lldap v0.4.2 Released(github.com)
1 points by nitnelave 4y ago|0 comments
50.
by nitnelave 4y ago
That's true, but they both come down to some translation from the source code to instructions: one is done in advance, and the other on the fly. I felt that the difference was not crucial for this article, but it's a good point.
51.
Simply explained: Where do programming languages come from?(confusedbit.dev)
1 points by nitnelave 4y ago|2 comments
52.
by nitnelave 4y ago
Not quite yet, but I'm working on a feature that will enable that: https://github.com/nitnelave/lldap/issues/67
53.
by nitnelave 4y ago
I got fed up installing OpenLDAP for user management, so I made LLDAP, targeting the Goldilocks zone of the article: simple to setup/manage, but powerful enough for most self-hosting needs.
54.
Teaching the Rust Borrow Checker(confusedbit.dev)
4 points by nitnelave 4y ago|0 comments
55.
by nitnelave 4y ago
I think it stands for OOPerational Surprise.
56.
by nitnelave 4y ago
I'm still hacking away at LLDAP ( https://github.com/nitnelave/lldap ), a light and secure mini-LDAP server made to be easy to configure. It's targeted at self-hosters, potentially on small hosts. We have a gro
57.
by nitnelave 4y ago
Since we're being pedantic, I'd point out that pulchritudinous is only used for people of great physical beauty, it's not a generic replacement for beautiful.
58.
by nitnelave 4y ago
I hear you, I initially didn't want to reimplement a whole server for that. And there are arguments for scrapping the API I slapped in front of it and make everything go through LDAP. Eventually, what drove me to create this is that it
59.
by nitnelave 4y ago
It only implements read-only queries and bind, plus password modification. User creation has to go through the web UI or API, and custom schemas are not supported. Any esoteric feature is probably also not implemented.
60.
by nitnelave 4y ago
I'm not a DB expert so I don't know much about stored procedures. Given that I'm trying to stay compatible with all of sqlite/mysql/postgresql, it might be difficult to rely on stored procedures horizontally. A read

More ›