dynamite-ready

The difference is in how sure the officials are about what they can rule out. That's what's very different here.

'We're not sure what it might be', is very different from the usual 'No comment' that we'd been so accustomed to.

You'd wonder whether that's because of:

A: Misdirection B: Genuine uncertainty C: A new policy with which to address social media

But you know, just the need to shoot something down, disclose that fact publicly, but not reveal exactly what it is (even if it is just a terrestrial source), is pretty freaky.

The military was happy to reveal the providence of the so called spy balloon. Not sure what the reason for the current course of action is, but if they're shooting stuff down, then perhaps it's not that banal.

Even it ends up being a pair of teenagers pulling off an elaborate hoax.

Key point I think the article misses, is that 'bullshit', much like spacetime, is relative.

Considered posting an Ask HN, and this is a bit of a segue, but seems a relevant place to ask... What do people think of DynamoDB? I think it fits my use case, and apparently, there's enough overlap with Cassandra to support a migration, if it turns out to be a bad idea. But I rarely see much writing about teams using it, so wondered about support / popularity / resources?

Can't believe Netlify CMS has been dropped. That was a really smart little project. For sites of a certain size (which seems to be a great number of webapps), it's an almost ideal solution. Hope any fork picks up sufficient traction.

Bugs do appear to still be tracked and tagged though, so it's a confusing state of affairs.

Kanye has burnt a lot of bridges, but he still enjoys a healthy portion of popularity. A very different form of popularity to that of both Trump and Musk too.

Musk and Trump's audiences, I'll admit to guessing about this, are passionate for sure, but:

- In Trump's case, tech literacy is low, the average age is relatively high, and disposable time they have, is probably low

- Musk's audience is undoubtedly tech literate, but I would guess that the age demographic is similar to Trump's, and would further guess their disposable time is similar, if not lower (we nerds barely have time for HN!)

Kanye's audience though... They're young, and they already live online. I can't imagine it overtaking Twitter at any point in the future, but I can definitely imagine the venture gaining more traction than Trump's attempt. And that will encourage other similarly minded business people to support his venture.

If you look at how Python is used in 3D graphics (or similar DSLs in the more esoteric 3D apps), they've been using the scripting system in the likes of Maya and Blender to create inordinately complicated systems for decades. Like 3D graphics, a lot of UI code is visual, ephemeral, complex. The development process for such features, benefits from from the speed of iteration and flexibility that dynamically typed code can provide.

Granted, a checkout, or a clinical case management form (for example) will definitely benefit from the kind of precision a strong type system will encourage.

Beyond that, we should think more about the how and why, because type wrangling can slow down delivery, experimentation, and cannot guarantee the prevention of bugs.

Gmail and Google Maps for example, at least when those projects started out, had no TypeScript in their UI code.

Google Maps, even in it's earliest iteration, far outstrips the complexity of most TypeScript applications in the wild today. And also has a greater requirement for precision than many of the applications that we can call to mind, outside of Finance, Transport, Construction, or Medicine.

People seem to talk as though certain applications were impossible to build without without TypeScript, but that is simply not true.

So TLDR, answering the root of your question, TS is not at all necessary. But it can be helpful. Yet we're in a position now where it's almost intractable, and I don't think that's an ideal situation.

The weight of user expectations, and the tools created to meet them. In between this, the big tech companies have leveraged this situation to put large segments of software developers on a treadmill, by using open source projects and excellent marketing, to impose a 'soft' form of standardisation on common practices (best demonstrated by React / Typescript).

My tongue is in my cheek, but I often wonder.

This is closer to my opinion.

I write a fair amount of Typescript, but it's frustrating to see it used so ubiquitously, when in a lot of cases it's just not necessary.

A strongly typed language definitely has a place in web UI development though. But my hope is to see it replaced by a WASM based language, or better still, a choice of WASM based languages.

Given the number of codebases littered with 'any', and the fact that TS is known to produce app bundles that perform slower than handwritten JS code, I'm in two minds about celebrating those ten years... But it is strange to think it's been ten years.

That's not quite equivalent, but I will indulge you. The truth is, there are many tools and libraries written in CPP, with many years of accumulated knowledge implicitly embedded in their codebases, that will take a very long time to replace, if some of them can be replaced at all.

It's fitting that you mention PHP, because while the ecosystem isn't quite the same, for all it's problems (especially security), WordPress is still viable for a bunch new projects, and things may remain that way for many years to come.

I think this is a silly idea. There are still loads of questions surrounding Rust. Especially about it's practicality... There are articles denigrating the likes of the trait and async systems on HN almost every day. And even ignoring that argument, any language is viable, so long as it can be used to build what you want to build.

Just display the animals side by side, when they sit on the same node.

Yes. 'Rollups' would also help the situation where multiple upgrades in combination will cause an issue. Ideally though, you'll be merging master into each automated pull request regardless. But rollups would save a bit of time.

You routinely write unit tests for dependent packages in your apps?

That would be a shallow reading, however. The last two major runtime issues wer actually one that broke the test runner and ignored a number of tests. And another runtime error was a Python Django specific sub dependency that broke the admin interface, which obviously, we don't explicitly test.

On the other hand, very recently, we had to abort a release, because of an outdated dependency that Dependabot DID actually raise.

Which is why I don't want to throw the baby out with the bathwater, as one or two people have suggested.

But I can say that I think that the reality of working with Dependabot, is not very well reflected in popular online articles.

Yes. This is exactly what I would prefer to do. My current plan is to round up all the PR requests, at the start of each new sprint (every two weeks), and make it the first development task in the sprint.

The problem though, is that so far, I can't point to any literature online, to support this idea.

I would still like to keep Dependabot, because the diagnostic step it performs is useful. But introducing new dependency upgrades daily, even minor upgrades, seems like a recipe for trouble. Minor upgrades are just as likely to introduce a vulnerability, as they are to patch them, after all.

I'm new to blogging (shameless plug https://raskie.com), so keenly feel the pain of writing content. But it's a satisfying experience, even if it can be a bit frustrating. If it's a tech blog, sometimes, the feeling of completion is at least as satisfying as solving a particularly difficult programming problem, or writing a small program. All the more satisfyingly when people read the content, and appreciate it in some small way.

So yeah. I find it valuable, even if I do sometimes feel like 'I could be writing some code / designing something right now'.

A problem I think I have is knowing when to stop writing... I look around at other people's blogs, and see all these succinct, perfectly targeted paragraphs, all the while considering my work to be bloated and overly long. But I do try to reread and rewrite stuff. I think it's a skill worth working on, so that's another reason why I spend the time doing it.

Many people say bad things about the algorithmic feed, but for me, the 'most recent' feed meant that often I missed tweets from people I'm actually interested in.

So I switched back.

I like the fact that it appears to keep the same API as Storybook. But does it have a USP?

Wonder if someone can add a little more info to the title of this story. It's would probably draw more clicks if the title wasn't so cryptic. This is essentially a Java dev infosec post.

Well... As a favour in return (:]), though the code is still early, what do you think of Godot 4 when compared to 3? I'm trying to finish a project with 3, because I know how unstable the master branch can get, but wonder if 4 will be worth the hype?

The link to the contribution guide is a 404? Was intrigued...

This does sound interesting. Regarding the idea of constantly updating dependencies automatically, I've heard of Dependabot, and haven't used it much myself, but isn't there a danger with an automatic update breaking things in production without supervision?

I'd guess I'm missing something in that question?

The biggest difference between our two projects, is the effort you've put into training your own model, which I think is amazing.

One of the technical issues that you pointed out, is that a model trained on still images, shouldn't be expected to work on video. While I did not train a custom model for this this project, I'm current working on another DNN model for a completely different purpose, where I think feeding frame deltas into the model, will improve the outcome.

As a hobbyist, I would reckon for porn and the like, analysing frozen frames is probably just enough. For violence however, I would agree with you and say that some effort to encode motion would be essential.

Focussing on NSFW content generally, I would guess, depending on the scale of your project, that you will forever run into 'edge cases' for NSFW images, even before you run into the soft wall of subjectivity.

I agree that the tech is improving all the time, and I think something like this can be made to be truly useful one day. Possibly soon. But it would need a large, active development team, a great deal more compute, and a LOT of data. In much the same way that no home/garage coder can hope to put together a model like GPT3 right now, I would think that a foolproof NSFW classifier would need more resources than you or I have access to at this moment.

But things change all the time.

Thinking about what you're doing, one thing I might suggest, if you have time to develop it, is to add some kind of 'recording' mechanism to your plugin, so that the users themselves can add to your dataset... But you have to wonder how many users will allow that! XD

I'm also wondering if a Firefox extension is the best place for your model? To that end, I would suggest putting the app on a server (which is what I originally wanted to do with my hack) which will give you the opportunity to crowdsource data collection. People might be more willing to volunteer data in that way (in a similar way to how people use https://builtwith.com/).

You're also very welcome to take the UX work I've done on this opensource project (because this hack was ultimately just a UX experiment), and plug your model in. If your model and trained weights are available, I'd like to try and create a branch myself, if I have time.

Also, as hobbyist building knowledge, I hadn't heard of `EfficientNet Lite` before. I'd been considering Darknet - https://pjreddie.com/darknet/ for embedded stuff until reading your post.

It's in a subfolder for the GUI project. Do you have any advice on the non standard text in the license? This is a concern I've never had before. Tbh, I'm surprised anyone has read it!

It's interesting. I've not tested the model on anything too risque, but again, with the well known Baywatch intro as a frame of reference, wide shots of the whole cast in their swimsuits, are fine. But a close up of any single cast member a swimsuit will invariably trigger the model. Male or female.

In the blog, I suggest this could be the result of an uncultured data set when training the CNN. Or perhaps the dataset was fine, and this is pushing the hard limit of what ResNet50 CNN architecture can do (the off the shelf model I use for this is an extension of ResNet50).

Some of the anomalous results are amusing. One day, I uploaded a video of a female violinist in concert, and the model flagged every close up of her as NSFW! Just those closeups. Wide shots, and closeups of other musicians were absolutely fine.

Again some of that might be down to me (clunky code / very low NSFW threshold). And I suspect the model I used was itself a PoC (https://github.com/emiliantolo/pytorch_nsfw_model). But it does make you wonder how the bigger labs with critical products, like Palantir, handle doubts like this.

Actually, there's a GNU license in both the CLI and GUI project. And the source code for the two 'random exe' can be found here - https://github.com/dynamite-ready/movie-parser-cli

Yep. It's classic hack.

If this was for a product, the first thing I would have done, was drop half the tools in the stack for their inefficiency! For example, the GUI shell is using Node Webkit (which I prefer to Electron, but is essentially the same thing). That in itself is quite bad, but it's not the worst approach to building a desktop app, as Microsoft and Slack have already proven.

But the .exe's you mentioned are also quite large.

The code is very transparent though. I doubt you'd have been the only one to note how clunky this all is!