capableweb

In the context we're discussing it right now, it basically is.

Is it really so blurry? Social engineering is about fooling a human. If there is no human involved, why would it be considered social engineering? Just because you use a DSL (English) instead of programming language to interact with the service?

Maybe it's a balance thing? Hyper-focus on commercialization and maximizing shareholder value might make other aspects of society worse, and some countries rather not make those tradeoffs while the US at large is willing to make those tradeoffs.

Even if "innovation commercialization" sucks in Europe, the EU is still the second largest consumer market in the world, so some of the things they're doing works, even if you're only focused on increasing capitalistic metrics.

Pretty shitty of that accounting software to reuse a name that has been used for paper accounting since basically forever.

Or, we can have multiple things being called the same thing, as RTFA actually makes the context clear.

And since you're bragging/plugging it here, I take it you tested it against this repository+version and it detected it?

Seems they've released a bunch already?

Image-to-text models, filtered by "Microsoft": https://huggingface.co/models?pipeline_tag=image-to-text&sor...

It's not weird, is typical Apple playbook.

Year 0 of cool thing - Nothing and silence

Year 1-3 of cool thing - Maybe, if you're lucky, a mention on some hardware thing related to it

Year 3-5 of cool thing - Hardware or software launches that uses thing, no mentions of this besides the earlier one if any.

Year 5-6 of cool thing - Next part of hardware or software launches that uses previous launch, no mentions of this besides the earlier one if any.

Obviously, the time-frames differ, but that's generally how they do things.

Companies of the size of Microsoft usually function more like a country with various companies within, rather than one company with a unified view and unified goals.

So probably, the group wasn't even aware of that technology because it's far away by either professional connection, or by personal/relationship connections, or they knew about it but had another goal than "maximize use of own stuff" and made the call that the tradeoffs wasn't worth it.

Since when does it cost money? I'm fairly sure it used to be free to visit...

When even Microsoft uses their own platform in a non-intended way, you know it's an official Microsoft project.

The link takes me to marketplace.visualstudio.com which makes it seem like a Visual Studio extension, not a VSCode extension? Not sure, it's as confusing as the live/hotmail/outlook/authentication parts of Microsoft tends to be.

Besides, it says the following:

> Windows AI Studio will run only on NVIDIA GPUs for the preview, so please make sure to check your device spec. WSL Ubuntu distro 18.4 or greater should be installed and is set to default prior to using Windows AI Studio.

So seems it'll only run in Linux, as it's a requirement to have Ubuntu WSL running beforehand.

Seems it might be looking at the referrer. Loading https://www.shopify.com/robots.txt from clicking the link shows the weird line while opening it in a private browser window shows the right one.

Not OP but:

"Has the site a /products.json file?" is a good first check :) And if it does, "Does that format match with the format a Shopify store?" is another good followup question.

> IMHO UI tests are just too difficult to be worth bothering with in most situations.

Yes, that's because you're doing them wrong.

Don't mess around with the "golden master" testing (edit: seems the frontend ecosystem call that "Snapshot Testing" actually, but it's the same) you see bunch of projects do, that compare the old DOM vs the new DOM you accept/deny changes based on component render output. That's a waste of time and won't actually prevent bugs.

Instead, extract the logic-heavy parts out from your components, then put those under unit tests, like any other code you write.

Boom, easy to maintain, verifies your implementation and makes your UI easier and faster to refactor and build in the first place.

> It took a while, but the arc of history is starting to bend in favour of that guy who said 'just use rsync' on Drobox's Show HN post in 2007.

It be interesting to see a breakdown on "time spent" between the people who went with Dropbox and started syncing stuff right away VS the people who first setup their own infrastructure to do the same thing.

Yes, this! People tend to forget when reviewing code long after it was written, that there is a lot of context around code that isn't "codified".

I remember looking once at a project me and some others got pulled into, where everything was working but the code was spaghetti (which, to be fair, is usually why I get pulled in), and they were having a hard time adding new features without breaking existing ones.

At first, our reaction was the same as many programmers; "Oh my god what have they done and why have they done it like this?!"

Turns out, the company was on the brink of extinction, had about two months of runway left and made this Hail Mary project to attract some new attention and eventually landed them new funding.

So the project was rushed, a lot, but that's OK, but if they didn't rush and wrote super shitty code, the company wouldn't have existed at all. They were OK with this, because they traded "existing today" for "refactoring in the future", which sometimes is the right call to do.

> The current reality is that Google has taken over the Web for all practical purposes

In the anglosphere and averaged out globally, yes, this is true. But country-per-country, the stats vary wildly. Some countries have ~20% Safari usage, others have ~20% Firefox usage. Other countries like Germany for example has Chrome usage below 50%, which is pretty neat.

But yeah, if you're a Usaian, I could understand if "the world" looks differently.

I can't speak for the Python part (which another commentator also already did comment on), but I don't think the React part is anything to highlight as "code you should try to imitate".

I just did a quick look, but it seems to suffer from common problems lots of UIs suffer from. Zero tests (unless I missed where they are located), even for things that doesn't even touch the DOM (like the "helpers"). Components filled with heavy logic at instead of being cleanly separated out. Just two examples after a quick 5 minute browse.

That said, I've definitely seen worse codebases and this wouldn't be too hard to work on in a professional setting. Clearly it works for them, and they seem to be progressing, which is good enough. But again, wouldn't flag it as "exceptional" either which you seemed to have done here.

> Doing things that way in 2023 struck me as so horrifically out of touch

> Clearly a distinctly minority attitude

So... Not at all out of touch then, as most people seem to be fine with it?

Great argument, how people may or may not use a browser in the future :) What if instead we look at current reality, which is what I outlined in my previous comment?

> You know most of consumer apps everybody uses are closed-source, right?

You know that web browsers is not your typical "consumer app" right? And none of the current popular browser engines are closed-source.

> I wonder if it has to do with so many people also being share holders with a vested interest in their success?

Would also explain why every single "union vs Tesla" story disappears so quickly from the frontpage.

> and their hand’s skin cracked bloodily and got bruised after a session. But they insisted to finish the game.

This arcade machine would be a great hit at BDSM parties I bet.

No, blaming the victim would have been:

> The only reason this happened was because they failed to secure their own systems, it was bound to happen

Instead, parent said:

> IT also failed to put enough checks here

My emphasis on the "also".

A publisher is a company that can help a developer handle things like marketing, support and other things. Basically the same as a book publisher not actually writing books, which is what authors do. Sometimes, the publisher and the developer is the same company, sometimes there is only the developer, and sometimes they are two different companies.

A porting house is a company that specializes in porting games across platforms. Lets say you've built a PC game with Godot, and now you wanna launch it on PlayStation. Instead of doing the porting yourself, you can outsource this to a company who would do the port for you.

Most of dang's comments (that I've came across at least) are moderation actions, like telling people how they're not following the guidelines and so on. But yeah, also the actual backend moderation actions should obviously be included in the training set.

Probably 5 to 10 years. Lets check back with each other around that time, I've put it in my calendar in the meantime :)

Using private keys the way they are supposed to be used is a deal-breaker? You're supposed to have (at least) one keypair per device, so if you lose the device, you can restrict access by revoking the keypair belonging to the lost one.

Are you currently sharing one keypair for all your devices?

Meh, fine-tune a LLM on dang's comments and call it a day. Ship early and ship often, adjustments can be made as we discover it doing the wrong thing.

What the hell is "mumbo jumbo"?

I hate it when people use words I don't understand and why should I have to lookup words I don't understand when people could just stop using those words?! I swear the world is against me.