holtalanm

7 ms·

1.
by holtalanm 5y ago
then you're hitting the db on every request just to do auth. if you _had_ to do that, I would put the counter into something like redis instead.
2.
by holtalanm 5y ago
watched the whole thing. was very informative. Actually havent used RSA in any capacity in years (AES is a lot easier to use), but always viewed RSA as a battle-tested encryption method/alg. I suppose with anything there are ways to
3.
by holtalanm 5y ago
> 1. Massively increases server strain and bandwidth usage A short-lived JWT that fits into an HTTP Header is not going to _massively_ increase your bandwidth usage. At most, you will end up with a single refresh request every few minut
4.
by holtalanm 5y ago
that would be insanely illegal.
5.
by holtalanm 5y ago
Yeah, if you need that kind of control over token access, then im not certain a jwt is the right tool for the job. For most use-cases a short-lived jwt is fine, as it expires in a matter of minutes, or even seconds, depending on configurat
6.
by holtalanm 5y ago
I can see that. I suppose when people say they need 'server-side session storage' I start thinking of app state, but in reality it could be as simple as storing a jwt refresh token that would be considered valid.
7.
by holtalanm 5y ago
i have never seen anything anywhere advocating for moving away from RSA. i'm curious to see what their sources are for this claim.
8.
by holtalanm 5y ago
> in reality you still need server side state for useful features like logging out im curious about this. normally 'logging out' just involves deleting the secure http-only cookie where the jwt was stored. is there something
9.
by holtalanm 5y ago
well, good luck getting buy-in from the cli tool devs, then? the other option requires absolutely zero buy-in from homebrew, gatsby, dotnet, or any other cli.
10.
by holtalanm 5y ago
are there documented cases of these cli tools abusing their telemetry? are they entirely used to pinpoint performance issues and bugs within the tools that implement this telemetry tracking? if it is the former, i can see there being cause
11.
by holtalanm 5y ago
my question here is: are we really concerned about console tools overreaching their telemetry? personally, I am not. I would love to know why others think this is some kind of huge issue, without a bunch of 'what-if' scenarios.
12.
by holtalanm 5y ago
I liked the Gatsby comment/suggestion a lot better: a tool for automatically setting the do-not-track env flags for all different dev tools.
13.
by holtalanm 5y ago
you don't have to clone it. cloning the object and putting it in Vuex will still result in it being reactive. `Object.freeze` is what I used. This causes Vuex to not traverse the object for changes. in my case, the objects I was pus
14.
by holtalanm 5y ago
> In my experience it has never, ever been the JS rendering layer which has caused unresponsiveness in an application. Implemented a undo/redo stack on top of Vuex once that worked on some very large data structures. Got unresponsiv
15.
by holtalanm 5y ago
> The site is called "JavaScript Is Weird", not "Weird Javascript" am i being punkd?
16.
by holtalanm 5y ago
> Calling these things weird is fair enough but I can't help thinking this is code you'd never actually write outside of the context of a "Look how weird JS is!" post. That is the whole premise of the site, though. T
17.
by holtalanm 5y ago
Most of the comments are completely dunking on Amazon for this, though.
18.
by holtalanm 5y ago
best solution is to use int/long primary keys, with a uuid column that has a unique index. then the uuid can be used with public-facing apis.
19.
by holtalanm 5y ago
Doesnt this just mean that 80% of orgs that were hit with ransomware attacks just didn't bother to fix their infosec, and got hit again because they left the same holes open to be exploited? Fool me once, shame on you. Fool me twice,
20.
by holtalanm 5y ago
almost like having competition drives innovation up and prices down. too bad most ISPs have literal monopolies over entire regions of people.
21.
by holtalanm 5y ago
Might explain why Reason seemed to have fallen off the face of the earth for me. I wasn't really keeping heavy tabs on it, but was more waiting for its tooling to be more mature. Will have to check it out again, I suppose.
22.
by holtalanm 5y ago
> I like where Skypack is headed and this seems like the opposite direction. I did a quick google search because I had never heard of Skypack. Skypack seems to be a far cry away from what WebContainers is claiming to do. Like, they&#x27
23.
by holtalanm 5y ago
I'm not sure what the complaint is here. Isn't it something like 90% of the browser market is chromium-based, now that edge is on the bandwagon? Supporting chrome/chromium doesn't seem like a bad place to start with a pr
24.
by holtalanm 5y ago
Yeah, now that you mention it, yeah. Elm is the natural progression down the functional programming rabbit hole for the frontend. Either that, or ReasonML, which I haven't seen much news for recently.
25.
by holtalanm 5y ago
completely agree. every React app that I have ran across that used 'best practices' for React development has been an unmaintainable dumpster fire.
26.
by holtalanm 5y ago
https://xkcd.com/927/ seems relevant. On a more on-topic note -- this data-oriented structure seemed to be at the core of the goals of Vue 3, to the point where you don't even need to use their Flux implementation
27.
by holtalanm 5y ago
> A new layout mode (like CSS Grid) isn't available yet? This allows someone to write a polyfill for it. That's neat! this was my first thought, too. We have polyfills for js features that don't yet exist in a lot of brow
28.
by holtalanm 5y ago
This. Your resolvers should still do access control. No different than a REST api would.
29.
by holtalanm 5y ago
I honestly dont see any different between graphql and a REST api, in terms of what data is available where. if you have data you don't want publicly available, just.....don't include it in the model, and make sure your server impl
30.
by holtalanm 5y ago
where I live, having reliable transportation (i.e. owning a car) is pretty much a job requirement wherever you work. a lot of people don't exactly understand just how _sprawling_ the US is.

More ›