𝙣𝙪𝙠𝙚

deleted by creator

I tend to agree. I think there’s little need as a developer to go that extra mile for accurate browser detection without UA unless it’s for fingerprinting. Most feature sets are supported and where it isn’t you have a polyfil or whatever shim to make it work. So in the case of fingerprinting you try not to rely fully on anything the user can alter easily.

.

deleted by creator

Browser detection is rarely done through User Agent lookup anymore. Nowadays we determine browser through feature detection.

https://developer.mozilla.org/en-US/docs/Web/HTTP/Browser_detection_using_the_user_agent#avoiding_user_agent_detection

I don’t think the average person understands how advanced bots have become at bypassing captchas now. Users will see this and be upset, and understandably so, but I’m telling you there is a big problem right now and devs are having trouble keeping up.

deleted by creator

Just hit Ctrl+Z to Undo

Say no more, I’m sold

Here you go. This might answer some questions you have https://www.healthcare.gov/what-if-im-pregnant-or-plan-to-get-pregnant

I had an idea about this today but I don’t know enough about Lemmy to confirm it. Thought I’d run it by you just in case.

Could you create a post and lock it normally, then directly edit the postgres row to unlock the post? I’m wondering if this would federate the lock but not federate your unlock causing all outside users to see a lock and all internal users see an unlocked post.

Possible edge case: users who subscribe to the community after the unlock will receive the initial data dump of posts and this will include the post in its current unlocked state.

However, this would be an easy way to block the majority commenting on a post while maintaining a seemless experience for your internal users.

Wouldn’t it make a difference in cases where the nameserver and host are not the same entity?

Oh no, the genocide supporters were defederated. Oh no, the horror!

Lol, cope

Thanks Satan

If the intention is to have an internal, instance-only post, I believe such a thing could be enforced with an automoderator bot. I had a lot of success throwing the Lemmy API into an AI and generating my own moderator bot from that. Could work for you.

Fair point, I agree there should be such a check. It seems for now that the only ones affected were people who tried to intentionally mess with it. It will be a hard goal to reach completely because what’s ok and healthy for some could also be a deathly allergic reaction for others. There’s always going to have to be some personal accountability for the person preparing a meal to understand what they’re making is safe.

That’s a bit dramatic of a take. The AI makes recipe suggestions based on ingredients the user inputs. These users inputted things like bleach and glue, and other non-food items, to intentionally generate non-food recipes.

Let’s not turn every community into memes. There’s plenty of meme communities on lemmy for you to choose from.

“Though his statements were intemperate at times, he has never, and would never, commit any act of violence against another human being over a political or philosophical disagreement,” the statement read.

Cognitive dissonance. He literally committed an act of violence against another human by shooting at FBI agents. Their whole damn family is fucking stupid and I’m glad the piece of shit is dead.

Instance admins should also make sure they’re not blocking /nodeinfo/2.0.json to avoid their instance being marked dead.