Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
biarity
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
9 ms
·
1.
▲
by
biarity
8y ago
We're getting there!
2.
▲
by
biarity
9y ago
Don't any of the langauges you support have options to keep all dependencies up to date? Eg. By putting wildcards in version numbers
3.
▲
An argument for passwordless
(biarity.gitlab.io)
2 points
by
biarity
9y ago
|
0 comments
4.
▲
At what point do passwords become impractical?
(biarity.gitlab.io)
3 points
by
biarity
9y ago
|
0 comments
5.
▲
by
biarity
9y ago
I think your method is much cleaner actually. Just updated :)!
6.
▲
by
biarity
9y ago
I agree! I find this especially useful when I have to set things like a UserId associated with an entity or with more complex entities where some data comes from injected services. I know you can create a service that handles creating the e
7.
▲
by
biarity
9y ago
I myself really dislike that piece of code (searching in exception strings isn't secure for many reasons, for example someone could use this to reverse-engineer information about my database). But the only alternative that comes to min
8.
▲
by
biarity
9y ago
Yes, that is the usual way of doing it. However, the point of this post was to showcase some ways of reducing duplicate code in large projects. Doing it normally (by checking if the entity already exists) can get repetitive if you have many
9.
▲
by
biarity
9y ago
I know, I just couldn't find a cross-db solution since I can't seem to find any standardized error codes in the exception. Do you know of a better way of doing this?
10.
▲
by
biarity
9y ago
Well the server was going to return an error anyways, instead of checking if the entity exists then trying to create it, you just go ahead and try to create it. This way if the entity doesn't exist then you've saved a trip to the
11.
▲
A todo list for new ASP.NET Core projects
(biarity.gitlab.io)
150 points
by
biarity
9y ago
|
63 comments
12.
▲
Show HN: Sort/filter/paginate framework for ASP.NET Core
(github.com)
5 points
by
biarity
9y ago
|
0 comments
13.
▲
by
biarity
9y ago
Cierge also uses magic links, making the code invisible to keyloggers. You can configure it to use magic links exclusively.
14.
▲
by
biarity
9y ago
Wouldn't that also present an issue with usual password logins?
15.
▲
by
biarity
9y ago
Cierge is stateless so it doesn't matter if you have 100 login tabs open, it'll always work - and once the code is entered it is automatically invalidated.
16.
▲
by
biarity
9y ago
Cierge is an OpenID Connect sever (which is based on OAuth 2), so your website would interact with it just as it would with non-passwordless solutions.
17.
▲
by
biarity
9y ago
Hi there! Cierge is an OpenID Connect server that handles user signup, login, profiles, management, social logins, and more. Instead of storing passwords, Cirege uses magic links/codes and external logins to authenticate your users. Yo
18.
▲
Cierge – Email-based passwordless authentication service
(github.com)
3 points
by
biarity
9y ago
|
1 comments
19.
▲
by
biarity
9y ago
Sadly nothing out of the box for AD. However, Cierge uses OpenIddict, so this might be helpful: https://stackoverflow.com/questions/38470683/is-it-possible-...
20.
▲
by
biarity
9y ago
Hi there! Cierge is an OpenID Connect server that handles user signup, login, profiles, management, social logins, and more. Instead of storing passwords, Cirege uses magic links/codes and external logins to authenticate your users. Yo
21.
▲
Show HN: Easy magic-link authentication – Cierge
(github.com)
11 points
by
biarity
9y ago
|
4 comments
22.
▲
Show HN: Easy magic-link authentication – Cierge
(github.com)
2 points
by
biarity
9y ago
|
0 comments
23.
▲
Magic link authentication server – Cierge
(github.com)
1 points
by
biarity
9y ago
|
0 comments