What about both? User supplies bad input? HTTP 400 with response body json describing the error in a standard format?

Looks like the link was to the form builder, not the data intake side of a built form. I didn’t make one to verify that side is different though.

Hiding a camera in person would be actively malicious if the other party doesn’t know. Having a zoom recording leaked is less actively.

It’s a balance, but too many people don’t even flag it to management because they’re lazy and they write shit and ship it to get it off their own plate.

Now, if management says ship it anyway it’s a balance of you as a developer making sure they understand they’re throwing this technical debt on the credit card and it may (probably) need to be paid off later. If you fail to articulate the interest that’ll be due later then you didn’t do enough or management is bad.

You shouldt work unpaid to fix it, but sometimes you should just do it right even if it takes longer because it’s how it should be done.

I have done it as my main job and I echo your sentiment. It’s inevitable that sometimes you have to meet a deadline or get something more important working first, but if you write bad code because you are lazy or unwilling to read the docs to do it right, shame shame shame.

I’m sure there are projects covering those areas written in JavaScript.

That sounds awful. And a major loss to accessibility. Here’s hoping one of the standards gains traction as the one path everyone can agree on.

I’m not up to speed on this issue, but it seems like the solution is to push forward with making the readers work in Wayland? Is there a technical issue with Wayland’s design that prevents readers from working properly?

That’s perfectly fine for some things, but for most people letting their browser choice dictate what sites they use is backwards

Did you forget the ./s or something? Lemmy itself is developed on GitHub, as are plenty of other “valuable” open source projects. To pretend nothing of value is built there is putting your head in the sand.

If you’re developing software on GitHub you have a chance at getting some useful feedback, bug reports and maybe even PRs. Like it or not, the network effect is real.

That’s no worse than you started. The fact remains nobody is going to get 100% coverage of their contact list on the fediverse without Meta, so trading a Facebook account for a threads account is no different, and it ignores the benefits of that time when you maybe able to live without either.

I felt like I had a good understanding of both htmx and csp, but after this discussion I’m going to have to read up on both because both of you are making a logically sound argument to my mind.

I’m struggling to see how htmx is more vulnerable than say react or vue or angular, because with csp as far as I can tell I can explicitly lock down what htmx can do, despite any maliciously injected html that might try to do otherwise.

Thanks for this discussion 🙂

Can you elaborate on that? I haven’t used it, but just assume if you host it on your own domain you can have it play nicely with csp, there are docs in their site about it. Where did it fall short for your use case?

That sounds awful. Imaging going back and forth requesting changes until it gets it right. It’d be like chatting with openai only it’s trying to merge that crap into your repo.

Is there a way to sign in with Microsoft account and not upload your key to the cloud?

This also makes me wonder if Android does the same thing with its device encryption, since you must login with a Google account.

I think the issue is that on mobile especially, switching contexts between apps is incredibly difficult compared to desktop and as such it’s easier for one app maker to include everything so it can contest switch more easily. The “share” mechanisms on Android and iOS are great for the common use cases but harder for more nuanced things.

That and keeping you within their ecosystem drives engagement which increases profit.

Which are all useless if nobody you want to talk to is there.

That’s interesting, I’d be curious to read more about that. Do you have any links to get started with? Searching this type of stuff on Google yields less than ideal results.

I’ve been using it with Firefox and haven’t had any issues with lag or speed on a regular pixel 6. I’m curious what issues you’ve had or if you’ve used the most recent versions?

I’m typing this from the new sync, because it’s more familiar to me and I prefer it’s ui.

Is there a specific Bluetooth dongle/adapter you use?