I see your point but I still wouldn’t call OBPs any more dangerous among kinky activities and the risks you mention can and should mitigated with standard BDSM safety measures. Also, it’s not clear from this picture, but usually the top part which actually gets inserted into the sub is a dildo or something else with a fair bit of flex to it, of course it’s not just solid metal pike.

Hmm, how come? I guess falling down with the dildo inserted could cause damage but as long as there’s always someone close by to help if needed, I would consider OBPs pretty safe.

One bar prison

That’s reassuring to know. What I don’t understand is why you have the /api/v3/post/like/list route. You say you don’t want votes to be snooped on, but then you add an endpoint that makes it very easy for instance admins to do exactly that if they choose to? Also worth pointing out that the tool linked here wouldn’t work in its current form if this route didn’t exist.

Compare your actions to releasing a 0-day exploit for a security vulnerability instead of responsibly disclosing. It doesn’t help, it just causes chaos until the people who do the actual work can figure out a solution.

This comparison is not fair at all. It’s not like the devs are unaware of this. They could start by removing the API endpoint that lists a post’s votes, but they haven’t, which means they seem to think it’s okay for the instance admins to snoop on votes if they so wish.

For me, this post seems to have the NSFW tag. In a recent update to Lemmy, the devs removed the NSFW checkbox from the interface when posting to a community that is marked as an NSFW community. I guess the idea is that posts to such communities should automatically be marked as NSFW, but this doesn’t seem to always work correctly. The confusion is worsened by the fact that in many Lemmy apps (such as Voyager, which I use) the checkbox is still there even when posting to an NSFW community.

But AFAIK, even non-NSFW posts from NSFW communities have always been treated as NSFW by Lemmy.

https://killedbymicrosoft.info/

Seems to be gradual rollout as usual. I don’t see that option in the latest app version

I’m just guessing but lemmynsfw.com uses some custom patches to change the behavior of how NSFW tagging works. Maybe the issue is related to that?

https://lemmynsfw.com/post/23232239
Seems their modifications have caused issues before.

Oh, I agree. This change will affect all CAs however. And their post seemed to contain the most amount of information.

I like that metaphor, I’m gonna save it. And agreed, there’s going to be issues with legacy systems.

Luckily, at my current job, all of our outside-facing legacy services already go through an SSL terminating reverse proxy. And we then use self-signed certs with much longer validity for internal traffic where needed.

Their official English party name used to be ‘True Finns’ but at some point someone probably figured out that sounds a bit elitist; Like everyone not supporting them is not a true Finn?

Luckily, the far-right here in Finland is less extreme than some of their counterparts in Europe. Finns Party members aren’t literal Nazis (or at least most of them aren’t), and some media outlets, including Yle, usually refuse to label them as far-right at all. Personally, I’m of the opinion that in the context of the Nordics, being far-right doesn’t necessarily mean you’re full-blown Nazi and that’s why I editorialized the title a bit.

I’ve been using Webbear and have been happy with them. I think they’re based in The Netherlands.

I think most guesses in this thread are a bit on the low side. I say $48.50.

Seems to be a CORS issue. A GET request to https://discuss.tchncs.de/pictrs/image/2254acd7-9ce1-4b07-b334-15631f2847e2.png is correctly responded to with a single Allow-Origin header:

Access-Control-Allow-Origin: *

However, the problem occurs when a browser makes that request. It adds an Origin header (For example, Origin: https://aeharding.github.io/ in this case), and then the server responds with two Allow-Origin headers, which is invalid:

access-control-allow-origin: https://aeharding.github.io/
Access-Control-Allow-Origin: *

(Note the different capitalization.)

Ignoring that, it also seems that the server does not support the Range header. Requesting the same image with the header:

Range: bytes=0-1

returns the full image instead of the requested partial content. This effectively means that while video/audio files hosted on this instance will play, features like fast forwarding won’t work properly. This is something @[email protected] will probably want to take a look at some point.

For me accessing that site in Firefox on Windows (even with uBO) does trigger the scam popup, but in any other browser I tried (Edge, Chrome, FF dev edition), it doesn’t. Kinda interesting.

The popup does not manage to add anything to the clipboard. There are tons of JS errors in the console, so luckily the thing seems to be pretty broken right now.

I think Microsoft should add a warning before allowing pasting into the Run dialog for the first time. Similarly like they already have in Edge’s console

If not, I volunteer to try them one by one. It’s only 1000 possible combinations… Let’s hope she doesn’t mind if I have to give the lock a good tug after every try just to be sure it’s not the right combination 😈

Drawing. And maybe some calligraphy. I take shifts at the local cafeteria during summers and we have a markerboard thingy outside to display our opening hours, daily special discounts and whatnot. I’ve seen others write on it with beautiful lettering and then decorating it with cool doodles. I tried it once and let’s just say it didn’t turn out well…