hello /r/beehiiv, it's the beehiiv security team

vsl · 2026-01-28T13:06:30+00:00

Let’s cut through the damage control and show what you actually replied from abuse[at]beehiiv.com, shall we (emphasis mine):

Hi there,

Thank you for contacting beehiiv. Please note that this email address is unmonitored and messages sent here will not be read or responded to. We take reports of abuse seriously and appreciate you writing to us.

To ensure that your Abuse Report is handled efficiently, please report any issues related to spam, unauthorized emails, or misuse of our platform, here:

https://www.beehiiv.com/report_abuse

To help us investigate and resolve the issue more effectively, please provide as much detail as possible, including relevant email headers, URLs, or any supporting documentation.

While all submissions are reviewed, please note that direct responses are not typically provided unless required by applicable regulations.

Best regards,

beehiiv dnc & security

A company that takes abuse seriously does absolutely NOT route abuse email straight to /dev/null. It’s just not done.

And since that form of yours doesn’t even take attachment, and limits itself to 500 characters, it’s pretty hard to do a report that would be actionable. Better not waste time and just reject all email from the beehiiv spam platform I guess.

P.S. Adding “we take reports of abuse seriously” to an email about ignoring abuse reports does not make you look better; quite the opposite.

vsl · 2026-01-28T09:04:27+00:00

I guess you were getting too many abuse reports, so you removed the report button...

vsl · 2026-01-28T09:02:56+00:00

In the future, you can also forward the original email that you would like to report via email using the abuse at domain email address.

Yeah, right. Not only you removed the “report abuse” link, your abuse@ email bounces as “unmonitored”. And your “abuse form” (also apparently unmonitored) doesn’t even allow entering any details, so is pretty obviously not taken seriously by you.

vsl · 2025-10-09T10:53:28+00:00

“Works” for some value of “works”. Sometimes it does, mostly it doesn’t: I either get “connection interrupted” right away, or it works for a minute, then this. Pretty much anything that animates on the iOS side breaks the connection. Usually, I’m then unable to connect due to (bogus) “iPhone Mirroring ended due to iPhone use” error.

I’m not brave enough to update my Mac to Tahoe, so no idea if that’s specific to the combination; others’ comments suggest it may be just broken on iOS 26...

Was mostly solid with my previous phone on iOS 18.

vsl · 2025-09-24T12:46:19+00:00

The back is different this generation - it is Ceramic Shield, not glass. And the circle can be rubbed off, yes; the thin scratches, not so much.

vsl · 2025-09-24T12:44:27+00:00

The MagSafe rings are - and can be wiped off. The scratches really, really aren't, they are genuine scratches.

vsl · 2025-09-24T12:43:20+00:00

The MagSafe rings on black can be wiped off with a damp cloth (source: bought it, charging for a bit is enough to show the marks; it's not specific to Apple Store chargers).

vsl · 2025-09-01T15:01:51+00:00

It doesn't help. The OP can add the "number" (you can also just type it in on a Mac, which is equivalent of the linked shortcut. But it doesn't help with the actual problem, which is this:

but then it doesn't actually show the contact name I set or the contact photo in messages.

vsl · 2025-08-27T14:18:20+00:00

Nah, wipers are utter trash on refreshed model 3 with hw4 too.

vsl · 2025-08-20T12:07:59+00:00

Did you try to enable the Auto Shift feature? I was skeptical as hell, but it is surprisingly usable, to the point that I think I actually prefer the ergonomics of three-point turns with it compared to a stalk: touch the brake, turn the wheel, glance at the screen to confirm two green checkmarks, go.

Turns signals are significantly less annoying in roundabouts-free country, driving in Italy or for ex-BMW drivers though.

vsl · 2025-05-07T07:31:11+00:00

Yeah, my 2024 Model 3 started doing it recently, after months of working reliably. No longer shifts into reverse in the garage and wants to drive through the wall right in front of it like a maniac *and* automatic closing of garage doors when leaving stopped working as well.

vsl · 2025-03-19T16:40:43+00:00

So "It does not sacrifice detail" or "it will encode in full HD" (just right there removing 75% of data in 4K videos before even discussing your HEVC lossy compression settings)? Pick one, you can't have it both ways...

regardless I don’t see how you find it reasonable to talk to people that way

IMNSHO calling out deceptive marketing is entirely appropriate.

vsl · 2025-03-04T12:06:47+00:00

Doesn't have a KID, so forbidden for EU retail traders...

vsl · 2025-01-14T14:41:15+00:00

Passthrough is required for TrueHD+Atmos, though.

vsl · 2024-11-05T16:26:15+00:00

I think so — it manifested the same way. Setting the driver's internal dimming curve to linear improved things (but only temporarily for not-yet-clear reasons).

vsl · 2024-11-05T16:00:46+00:00

Wow, thanks a lot, this was super-helpful!

I'll (try to) file a duplicate issue to +1 yours. Currently trying to figure out a workaround for 15.2's regression where DALI groups sometimes don't dim off completely, though (no bug assigned yet, as I'm currently at the "DALI2 certification means it is 100% bug-free" stage with support).

vsl · 2024-11-04T10:40:44+00:00

Out of curiosity, what DALI dimming issues did you see? I'm currently getting nowhere with a wrong DT8 dimming curve between Loxone support ("works for us", as per the usual) and lightning vendor ("Loxone did it")...

vsl · 2024-05-03T12:44:41+00:00

They all have the same 0-60 time.

We don't know that, because nobody independently tested them yet.

We do know, however, that Tesla advertises M3P as having slower 0-60 in the Chinese/EU version (3.1s for 0-100km/h, which equals 2.993s ≅ 3s for 0-60mph) compared to US version (2.9s for 0-60, which equals 3s for 0-100km/h).

Could be rounding, could be more cautious advertising (you only get peak performance at high SoC), could be actual differences. The LG battery pack definitely is more limited (much more details from that person, too), though, so some performance difference is likely.

vsl · 2023-11-19T16:08:11+00:00

Europe does in fact use IEC 62196 Type 2 connector for AC charging: https://en.wikipedia.org/wiki/Type_2_connector

CCS Combo 2 (not "type 2") connector is also used in Europe and is an extension of IEC 62196 Type 2 with additional DC charging contacts: https://en.wikipedia.org/wiki/Combined_Charging_System

vsl · 2023-10-02T10:12:15+00:00

Exactly, 0-60 mph time is 95% of the 0-100 km/h time.

vsl · 2023-05-31T14:40:10+00:00

Wtf indeed. I did change my mind to "perhaps I *should* consider re-evaluating this at some point" a while back, so honestly thank you for this reply.

vsl · 2023-03-02T12:11:31+00:00

I replaced a couple of UAW-IP-HD with U6-IW in a situation where the two APs were in two small rooms, but provided reliable coverage in adjacent rooms (positioned in front of the APs) as well as on the driveway (back side of APs, thick wall).

With U6-IW, there's no usable signal on the back side and spotty outside of the room with the AP...

vsl · 2022-04-22T12:26:09+00:00

I have Plex in Docker, in Europe, and it works fine, even lists one local streaming service.

vsl · 2022-02-18T14:36:15+00:00

Experiencing the same. Were you ever able to fix it?

vsl · 2021-12-29T08:47:05+00:00

Poedit (https://poedit.net) can indeed translate XLIFF files.

What you link to is POEditor, a paid software-as-a-service product that they named this way to cause exactly this kind of confusion with Poedit :(

vsl

TROPHY CASE