On 8 Nov 2024, at 23:20, Pete Resnick wrote:
On 8 Nov 2024, at 16:13, Murray S. Kucherawy wrote:
If the goal is to favor running code over mere pontification, I think
that's a solid proposal...
That it certainly true. But I think we do want code that is not just
running, but is also usable
On 9 Nov 2024, at 8:38, Jim Fenton wrote:
Email, as a service, has to serve both large providers and small.
It’s important that the charter consider the needs of small
providers as well as the large ones. This is a theoretical concern at
this point, and I hope we don’t end up in a situation wh
On 9 Nov 2024, at 17:25, Pete Resnick wrote:
> On 9 Nov 2024, at 17:07, Jim Fenton wrote:
>
>> On 9 Nov 2024, at 13:16, Pete Resnick wrote:
>>
>>> On 9 Nov 2024, at 8:38, Jim Fenton wrote:
>>>
suggest that the charter acknowledge that scalability is important and
stop there.
>>>
>>> W
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
In message <1810e35c-f268-4040-af09-073cccbae...@bluepopcorn.net>, Jim
Fenton writes
Since I think we have a duty not to heat up the planet any more than
absolutely necessary, and since designs with large numbers of crypto
operations (to achieve limi
On 9 Nov 2024, at 13:16, Pete Resnick wrote:
> On 9 Nov 2024, at 8:38, Jim Fenton wrote:
>
>> Email, as a service, has to serve both large providers and small. It’s
>> important that the charter consider the needs of small providers as well as
>> the large ones. This is a theoretical concern at
On 9 Nov 2024, at 17:07, Jim Fenton wrote:
On 9 Nov 2024, at 13:16, Pete Resnick wrote:
On 9 Nov 2024, at 8:38, Jim Fenton wrote:
suggest that the charter acknowledge that scalability is important
and stop there.
Well, I would also like something that is clear that running code is
favored
