joekrill

I thought this would be something more specific, but it's just a fairly generic website that lets anyone create a countdown clock. Not only that, but this seems to be counting down to 5:00 PM EST (for me, at least), and the inauguration is at 12:00 PM EST. So I'm guessing this website doesn't even account for timezone differences?

Congrats on the latest release! I'm really excited to see this space getting a lot of attention and traction lately. I think it's one of those things that basically every app has to "reinvent" to some extent, and I would love to just be able to spin up a container that handles a lot of this stuff. Especially considering the security implications.

I dug into this space recently and Keycloak is really the best, most full-featured (open source) solution at the moment. But it's a hefty and can be difficult to work with at times (documentation can be lacking and confusing, customizations difficult). It doesn't seem to jive well with a modern containerized stack, either.

Ory and Supertokens are the two open source projects that I've been keeping an eye on and I think are making great progress and will be real viable alternatives to Keycloak soon. Last I checked they weren't _quite_ ready for real production usage (for various reasons, I'll have to revisit my notes), but they both seem to be moving quickly so looking forward to trying them again soon.

Well that's when you get a lawyer to review it for you. I realize there is a cost involved here, but when you're talking about something like this it's usually well worth it - if only to know exactly what you are agreeing to.

It's absolutely astounding to me how many folks blindly sign legal documents. Especially employment related. Whenever I've pushed back on an employment contract, NDA, or similar it's always met with sudden confusion - as though this has never happened before. In fairness, it's almost never met with negatively. But it shows that no one else has ever bothered to question it. And when I talk to colleagues I definitely get the sense that no one ever really reads these things or questions them.

Hooks are not some panacea that's going to fix a defunct development process or poor code organization and management.

Any codebase, using any language, framework, feature, and technology, needs to be managed properly. There's really no getting around that. And without that, you're almost always going to end up with things turning into something along the lines of "complete untestable spaghetti". Especially when you have junior developers involved. Hooks are no different, nor is the entire Javascript landscape.

In general these complaints are getting tiring and often feel like they are coming from folks who don't have the appropriate level of experience or knowledge in a particular subject area to be making these generalizations. I don't know what your level of competence is, but this line:

> Look, I get that Redux was a pain in the ass with all the boilerplate, but how did we throw the baby (unidirectional data flow) out with the bathwater.

gives me pause, because Hooks aren't meant to replace Redux in any way. There are hooks that maintain state, sure, but generally they're meant to replace class component lifecycle functions. Hooks and Redux still coexist quite well.

It's really hard to tell from the wording of all of this what exactly this applies to. It talks about medicine and food allergies, but also says those who carry an an adrenaline autoinjector. Does that mean those that carry the adrenaline autoinjector for medicine and food allergies? Or anyone who carries one AT ALL? For example, someone who has one for bee stings - should they avoid the vaccine?

I've been using ZFS for a few years now and it's just been amazing. Storage is so cheap these days that it's just much simpler and straight-forward to use mirrored vdevs. If a single drive fails, the pool is still completely usable, and all I have to do is swap out the bad drive (when I get around to it, no hurry usually) and resilver. Resilvering can take a while, but everything is still completely usable while it's happening so it just runs in the background and I don't even notice.

I just upgraded a pool of 4 drives from 4TB each to 10TB - I'd never done anything like that before and was rather nervous, but it was just so simple with the mirrored set up - just swap out each drive and resilver one- by-one.

It's a buzzword, but that doesn't mean that what people think of as "organic" - in the good sense - doesn't exist. I'm sure you didn't mean it, but your comment gives the impression that all "organic" food is a shame. There are plenty of sustainable farms that don't use harmful pesticides. It's unfortunate the word has become what it has, but it's not a catch-all one way or the other.

This article makes some really great points, and comes to a great conclusion that I 100% agree with:

> before committing to a piece of technology, it’s crucial to understand the problems it solves, and the context in which the solution was made.

On the other hand, I think the title is doing it a huge disservice. Because, unfortunately, a lot of people don't read beyond the title, and that only helps to perpetuate the anti-k8s/Istio/devops sentiment that has become so popular and pervasive lately.

Are there a lot of situations where a service mesh complicates things and causes more problems than it's worth? Absolutely. Are there a lot of situations where a service mesh will really help? Without a doubt. Should you use it when you build your personal niche side-project? Probably not. But maybe a goal of your side project is to learn Istio - in which case, you totally should use it.

I'm in the same situation. This used to happen often, years ago when they first introduced GAFYD, and I haven't had an issue in a long time. But looks like things are reverting back now.

Not to derail the conversation, but I'm curious about how you soundproofed your home office. Do you have any information about how you went about that and what was involved? I've been looking into this myself recently.

I checked it out and created a diagram, then I clicked the icon in the upper left corner thinking it was some sort of menu. But it just took me to the main home page -- but without saving anything at all or even prompting me. So I basically lost all the work I did without warning. Is that supposed to happen?

> Create as many diagrams as you want. Save your diagrams locally to pause and continue later.

I found the save button, but it seems to just take a single snapshot and reload that automatically if I leave and return. So it seems like you can only have one diagram going at a time? But even if I want to start a new diagram, I can't figure out how to do that without manually clicking each individual icon and deleting them, one-by-one.

Maybe I need to signup for this additional functionality to work?

That's debatable. Perhaps not the most secure, but possibly the best quality and most reliable (to this point, at least). Depends how you define quality, but the ease of use and high quality video are perhaps the leading factor in their huge success.

But they do once the consumer spends that gift card. So charing 30% for the gift card would sort of be charging the Apple tax twice, wouldn't it?

> Little known fact: if you buy anything on Amazon, DuckDuckGo gets to know exactly (the precise item) you bought as part of the Amazon affiliate program.

This isn't specific to DuckDuckGo in any way whatsoever. This happens for ANY affiliate. I've used the Amazon affiliate program, and every month I would get reports of the exact items people were purchasing. I couldn't link those purchases to any particular individual, mind you, but I could see exact items.

But this specific article makes no mention about it.

This is a very naive response. Rarely is anything "trivially implemented". And if it's so trivially implemented, why haven't we seen a browser vendor implement something already? Websites have been circumventing attempts to prevent fingerprinting for a long, long time. To act like this is some simple task is hugely misleading.

I've been reading this book "Breath: The New Science of a Lost Art" by James Nestor. He attributes this sort of thing to, effectively, "mouth breathing", and suggests it can be fixed by learning to breath correctly (through the nose).

I have no idea if it's bullshit or not, but it's compelling. Would love to hear from anyone that has insight into this.

I wasn't commenting in any way on the legalities. IANAL and, frankly, I just don't think it's germane to my point.

Netsential clearly had a massive security vulnerability in their system that allowed one user to access the data of all other users. That's very much on them.

Consider a company that provides physical storage units and advertises that they are secure and can only be accessed by their owner. Then it turns out that there was a back alleyway running behind all the units that allowed any owner who had access to one unit the ability to access any other unit, without a key. I don't think anyone would suggest that would be anything other than a massive security oversight by the storage company. Yes, what the thief did was illegal and should be dealt with. But you'd have a hard time convincing me that the company itself wasn't primarily at fault for such a huge oversight in the first place. And I certainly would never use them again.

That's the first thing I thought, too - sounds like they are trying to spin it as some malicious user "broke in". If a "customer user account" is able to upload a malicious payload and exfiltrate huge amounts of other customers' data, there's a much larger, underlying problem here. Hard to see how Netsential could get through this fiasco and still have any business.

It's not a scenario where you can look at "absolute years from inception". It's all relative. With the JS ecosystem, you have rapidly changing Web APIs and standards, varying degrees of browser support and Node versions. And no real "central authority" to guide things in a specific direction. With Android you have a much more managed platform, with Google providing at least some guidance on best practices (explicitly or not). I'm sure the recent introduction of Kotlin added some complexities and confusion to that system. But I still don't think things are changing as rapidly as they are in the JS world, and from so many different angles.

This sounds like the sort of thing I hear from folks who have only passively dealt with the Javascript ecosystem but somehow still seem to think they have a really great handle on the entire situation, how it got there, what exactly the root of the problems are, and (sometimes) how it can be fixed.

And while I partially agree in some cases, I don't think this is in any way a problem specific to the JS ecosystem. There is definitely a lack of quality in a whole lot of JavaScript code out there. But I've also seen TONS of horribly written Ruby gems, .Net libraries, Java apps, even Dockerfiles.

It is just much more prevalent when those ecosystems are still "maturing" - which I think JS, Node, NPM, etc still very much are. Even the early Android days were plagued with tons of horrible options for networking libraries, SQLite helpers, or whatever else wasn't fleshed out well. And that was just the _platform_ maturing with a language that was already quite mature. With JS you have not only the language itself maturing and changing rather quickly, but also all the underlying platforms, package management systems, security issues, etc.

Patterns, best practices, and standards often take quite a while to surface and become established. And they seem so obvious in hindsight! Which is why I think we get a lot of people coming from other ecosystems who seem to have selectively forgotten about that happening in their own established tech niche.

From a Forbes interview[1]:

> Weinberg: We make money the same way other search engines make money. When you type in “car,” you get a car ad. We syndicate Microsoft and Yahoo ads through the Microsoft Yahoo Search Alliance.

[1] https://www.forbes.com/sites/forbestreptalks/2016/02/19/the-...

Is anyone working on solving the noise problem with drones? Is it even really solvable in any realistic way? What would it take to have a "silent" drone?

> I recently asked a front-end dev why they chose React for a simple app over simple server-side templating

I don't really get this argument. What makes "simple server-side templating" better than React components? I'd argue that these React components effectively are templates. If someone is proficient in React, why are we suggesting they have to learn some other random templating language? Not to mention deal with additional things like file organization, transpiling, etc.

I don't think it's quite that simple. Ignoring the fact that I'm not in the EU, the company would also have to have some sort of presence in the EU for that to have any effect. And then which company do I send it to? The original one? Or the one they shared my address with and is now spamming me? Presumably the latter, since they are the one sending the spam. But if the initial company shared my email address with that company, they probably shared it with a lot of others, too. And what are the chances someone who has resorted to these sorts of tactics is going to care anyway?

I use gmail, so I just use the "Report as spam" option. I'm assuming Google uses that information in some way when calculating spam scores. So if enough people do the same, those emails will just start getting sent to spam automatically for huge amounts of people, and therefore punishing those folks for doing it in the first place. That seems more effective to me.

And I just never really had that big of an issue with spam where I needed to black-hole a specific email address. So for me it just wasn't worth the effort.

I did this for a while. I gave up because it just wasn't worth the effort. I would run into exceptions to my permutation rule maybe. Or I signed up for an account and forgot which email I used so couldn't reset the password. Things like that.

> This has two benefits: I can easily route/filter incoming email from that vendor, and if I ever receive spam at that address I know which vendor sold my info.

There's just nothing actionable to do with this information. OK, so I caught badcompany.com giving my email address to marketingfirm.com. But the damage is already done. Sure, I can send them a nasty email, but it'll just get ignored or whatever.

I hate when things pop up when I select text, because I have a tendency to randomly highlight text as I'm reading it.

This little speaker pops up, so I clicked it out of curiosity, and it started to speak the text. The icon choice is a little unusual (I'd expect a play button or something, but that icon is typically used to control volume). But then I couldn't get it to stop playing. I even closed the tab and it was still playing. And for some reason Chrome doesn't show that tab as even playing audio so I could mute it. What the heck is going on there?

I think they've iterated on the design a bit over the years, but my primary criticism is that it can be hard to distinguish that an input is, in fact, an input. I think Google has since changed their design to have a filled background or border, which definitely helps - but this particular implementation doesn't seem to do that (except when the input is disabled, which sort of defeats the point).

There's also a lot of problems around how the placeholders and labels work - particularly in distinguishing them from each other.