I tried to be an attendee-only at a conference and failed. I am taking over Tomas Votruba's talk about Rector on short notice (with his slides and permission), as he's unable to make the trip to Montreal.
I really would like an opportunity to get in on a Product Owner role at some point. Unfortunately all the requests for PO roles specify the ideal candidate has 5+ years of previous experience as a PO
Following the steps documented using https://rpms.remirepo.net/wizard/ for getting PHP 8.3 as default on Fedora 39 (after removing the default 8.2) I only get PHP 8.3.0-RC.1...?
@Skoop Oh I don't doubt it is possible ;-) I just have a rather long "track record" of failing to make the cut. Which, for whatever reason, bothers me more than it probably should..
I finally gave in. After 5 years on Linux I will go back to MacOS in 2024 (which I have been using in various degrees of professionalism since... 1991?).
Linux is all nice and dandy. But there are so many rough edges that hinder my productivity.
So I'll bite the bullet and compromise on openness and IMO questionable company decisions in favour of my own productivity and sanity.
@derickr@ocramius@grmpyprogrammer Interestingly, I only have a hard time calling people I don't know personally - unless it's a call center I have to call. No issues receiving calls here.
$country->getIso() is string|null, but I'm sure it is string - or at least I'm fine ignoring the unexpected case ๐
Or do I neet to put it in a var to add a /**@var to it?
@Schrank@muhdiekuh What's the point of using a 3rd party library when PHP can do this natively?
assert($iso !== null);
Works just as good. You can also configure PHP how to react on assertions failing: Exception, Warning or ignore, where the later turns it into a no-op at compile time, afaik
As may become obvious in my replies to the thread linked above, I disagree to some extend.
I use assert all the time, mostly to cover unlikely (or almost impossible) edge cases that infection finds and I do not feel like writing explicit code for. Or to avoid writing psalm annotations for my implicit asserts ($obj->isFoo())
Is it just me doing something wrong or is @plausible (self hosted) having issues all of a sudden with the google search console integration? I cannot re-link anymore - it used to work before like charm, but now always fails: "Your Search Console account hasn't been connected successfully. Please unlink your Google account and try linking it again."
@movetodevnull@heiglandreas We should meet again sometime soon and discuss how we can keep this stuff alive - and how to re-implement the things that need changing ๐
Suggested Mitigation: Do not expose Exim to the internet.
How not helpful. It's an MTA!
But not doing anything feels wrong. So I put exim behind NGINX using its mail proxy. Took about 20 minutes of RTFM and ~10 lines of nginx / exim config changes.
Does it help? No idea, we don't have details of the exploit. But it feels better. Does that count? ;-)
When you explain the bug bounty hunter that the existence of the RESTish users endpoint in a WordPress installation does not automatically mean that it's vulnerable according to CVE-2017-5487 and that according to your Security Policy issues in the Blog do not qualify for a bug bounty.
And then they answer back and ask whether that kind of hard effort deserves some reward.....
@heiglandreas I received security vulnerability reports from a "security researcher" (also insisting that he get a compensation..) claiming issues with the respective website, but referring to, according to him, invalid DMARC Settings. The fact DMARC is mail and has thus nothing to do with web, was apparently irrelevant. And the claims where wrong as well, the setting is correct and only broken MUA do not adhere to it properly.
The first time I tried to explain things, then I had to RBL him.
