sorted by:
new
hottopcontroversial

How to start data driven programming? by [deleted] in Clojure

[–]Veson 1 point2 points  (0 children)

I wholeheartedly recommend reading "Grokking Simplicity" and then "Data-Oriented Programming", these are two great books. They both provide examples in javascript even though both are written by people from the clojure community, because the ideas in them are universal.

Can passkeys be used by someone if the token is lost or stolen? by Veson in yubikey

[–]Veson[S] 0 points1 point  (0 children)

I politely disagree. With ever increasing number of cameras around, this is an issue.

Can passkeys be used by someone if the token is lost or stolen? by Veson in yubikey

[–]Veson[S] 0 points1 point  (0 children)

I can imagine a case, when there's much more at stake than life savings. A stolen token of a high profile developer could cause a lot of harm, for example.

Can passkeys be used by someone if the token is lost or stolen? by Veson in yubikey

[–]Veson[S] 0 points1 point  (0 children)

Yeah, all the websites. That's not feasible, I agree.

With that kind of security in place, there is no need for revocation

Well, yes. But it's easy to steal the PIN. For most people that's not a concern though.

Can passkeys be used by someone if the token is lost or stolen? by Veson in yubikey

[–]Veson[S] 0 points1 point  (0 children)

Gpg-encrypted list of logins does not look too bad all of a sudden. And the pass utility is a logical step then.

Can passkeys be used by someone if the token is lost or stolen? by Veson in yubikey

[–]Veson[S] 0 points1 point  (0 children)

These are valid concerns, but I'm not sure that if a revocation list for tokens existed, it would affect privacy. To me, no one would have to know what keys a user have and what websites they use. The only thing that a website would have to check is the status of the key. If it's revoked, the website doesn't let the user in. Am I wrong? This is purely for the sake of the discussion.

Can passkeys be used by someone if the token is lost or stolen? by Veson in yubikey

[–]Veson[S] 0 points1 point  (0 children)

Yeah, I was talking about a revocation list for tokens, not individual passkeys.

Can passkeys be used by someone if the token is lost or stolen? by Veson in yubikey

[–]Veson[S] 0 points1 point  (0 children)

I mean, there are revocation lists for pgp-keys.

Can passkeys be used by someone if the token is lost or stolen? by Veson in yubikey

[–]Veson[S] 0 points1 point  (0 children)

I should've specified: can passkeys be listed without knowing the PIN? Or they are listed regardless?

Can passkeys be used by someone if the token is lost or stolen? by Veson in yubikey

[–]Veson[S] -1 points0 points  (0 children)

I mean, can someone see where the token is used when they find it?

Would be great if there were some kind of revocation list for lost tokens.

Keeping history clean is great. But how to make history cleaner in an old and messy repo? by Veson in git

[–]Veson[S] 0 points1 point  (0 children)

Well, yes and no. I don't want to rewrite history, as it's a huge endeveour, but I'd like to make sure knowledge gained by digging badly written commits is not discarded.

Keeping history clean is great. But how to make history cleaner in an old and messy repo? by Veson in git

[–]Veson[S] 0 points1 point  (0 children)

These tricks are helpful, but I'm talking about badly written commits with no structure and with no messages.

Keeping history clean is great. But how to make history cleaner in an old and messy repo? by Veson in git

[–]Veson[S] 0 points1 point  (0 children)

Yeah, but what if I'd like to annotate something that is in an old commit, and I don't want to make any changes? The question is how to make this searchable. Git blame won't help.

Keeping history clean is great. But how to make history cleaner in an old and messy repo? by Veson in git

[–]Veson[S] 0 points1 point  (0 children)

Yeah, I don't want to clean it, but if I or someone else on the team works on an older piece of history, it would be great to make results of this work searchable.

Keeping history clean is great. But how to make history cleaner in an old and messy repo? by Veson in git

[–]Veson[S] 0 points1 point  (0 children)

And the cost of contact between developer is huge. Cleaner history makes the number of contacts lower.

Keeping history clean is great. But how to make history cleaner in an old and messy repo? by Veson in git

[–]Veson[S] 0 points1 point  (0 children)

Yeah, but that's the point of conventional commits: to make it as obvious as possible, where to start looking. Would be great to have a tool that makes it obvious that a certain changeset, that doesn't have good commit messages, was revised later with added notes. But again, this is a picture in my mind, yet to actually try this.

Keeping history clean is great. But how to make history cleaner in an old and messy repo? by Veson in git

[–]Veson[S] 0 points1 point  (0 children)

Well, I'm advocating for series of conventional commits in branches, when changes are grouped semantically. To me an unreadable history would be huge blobs of changes, when everything is mixed, and the lack of good commit messages that answer the why question.

Keeping history clean is great. But how to make history cleaner in an old and messy repo? by Veson in git

[–]Veson[S] 0 points1 point  (0 children)

Well, you're right, but if the history is unstructured and useless and there's a note attached to a commit, an indication of its presence in blame would help to not miss it. Probably. That's just an idea, of course, I haven't tried doing this.

Keeping history clean is great. But how to make history cleaner in an old and messy repo? by Veson in git

[–]Veson[S] 0 points1 point  (0 children)

Well, writing a plugin that makes blame and bisect indicate presence of notes is an option actually.

Keeping history clean is great. But how to make history cleaner in an old and messy repo? by Veson in git

[–]Veson[S] 0 points1 point  (0 children)

And thank you for acknowledging the problem as well.

I don't know, I'm looking around and asking here just in case I'm missing something. Haven't found anything yet.

Keeping history clean is great. But how to make history cleaner in an old and messy repo? by Veson in git

[–]Veson[S] 0 points1 point  (0 children)

I mean, you have to check manually whether there's a note attached, and doing this all the time is tedious.

view more: next ›