Re: [PHP-DEV] [RFC] PHP.net analytics

2024-11-05 Thread Jonathan Vollebregt
On 11/5/24 6:29 PM, Larry Garfield wrote: Overall I feel like the signal we can get from using a JS tracker specifically is comparatively low to the point it's not actually worth it. Some more things a client-side tracker could do that logs cannot: * How many people are accessing the site from

Re: [PHP-DEV] [VOTE] Add persistent curl share handles

2024-11-05 Thread Eric Norris
> > That said, as I mentioned above I would be fine with removing cookie > > jar persistence if that was necessary to secure a passing vote, since > > it's not our primary focus. > > Given the information regarding the TLS re-use, the cookie sharing is my > only remaining concern. In fact with cook

Re: [PHP-DEV] RFC: Support Closures in constant expressions

2024-11-05 Thread Larry Garfield
On Mon, Nov 4, 2024, at 6:57 PM, Gina P. Banyard wrote: > On Monday, 4 November 2024 at 20:32, Larry Garfield > wrote: > >> On Mon, Nov 4, 2024, at 6:06 AM, Tim Düsterhus wrote: >> > >> > Here's another brainteaser: >> > >> > function foo( >> > string $bar, >> > Closure $baz = static fn () => $

Re: [PHP-DEV] [RFC] PHP.net analytics

2024-11-05 Thread Larry Garfield
On Fri, Nov 1, 2024, at 6:10 PM, Bob Weinand wrote: > On 1.11.2024 22:41:29, Larry Garfield wrote: >> In a similar vein to approving the use of software, Roman Pronskiy asked for >> my help putting together an RFC on collecting analytics for PHP.net. >> >> https://wiki.php.net/rfc/phpnet-analytics

Re: [PHP-DEV] [RFC] [Discussion] Persistent CurlShareHandle objects

2024-11-05 Thread Eric Norris
On Mon, Nov 4, 2024 at 2:13 PM Jakub Zelenka wrote: > > On Mon, Nov 4, 2024 at 2:21 PM Jakub Zelenka wrote: >> >> Hi, >> >> On Wed, Oct 9, 2024 at 10:18 PM Eric Norris wrote: >>> >>> Hello all, >>> >>> After receiving some feedback about >>> https://github.com/php/php-src/pull/15603, I'm formall

Re: [PHP-DEV] [VOTE] Add persistent curl share handles

2024-11-05 Thread Eric Norris
> > Here's a pull request indicating that the curl team considers TLS > > reuse safe: https://github.com/curl/curl/pull/1917. I believe they > > consider it a vulnerability if you are able to make curl incorrectly > > reuse a TLS session with differing TLS settings. > > Thank you. That would be use