

Regarding Google, looks like it’s in the pipe yes, Fushia is non-GPL (permissive licenses, so no redistribution clause in case of a sudden licensing switch).
Also on Mastodon: @pedroapero@mastodon.top
Want to send me a tip? XMR:89oiUKyACFZ655sTikh42RF8wpd46EQDmbTQUQiHHRWFEatjp5xxj4tZBhMMfjC4X45qvq4EdEGXkBsdxT1kP9xyVia8mPD


Regarding Google, looks like it’s in the pipe yes, Fushia is non-GPL (permissive licenses, so no redistribution clause in case of a sudden licensing switch).


Code signing for EXE is already a thing. And @DFX4509B@lemmy.wtf is right, the same thing is happening there. Restrictions are getting more inconvenient, with Microsoft now talking about a maximum code signing certificates validity of 72 hours, with identity verification getting more strict too. Valid code signing certificates are not mandatory yet but I guess it’s a matter of time before we need to type powershell commands to disable restrictions.
I use Signal, but I’m unable to force everybody to do the same.
Any chance to use Whatsapp on /e/ ?
Yes, so now when there’s a success, it gets attributed to AI. When there’s an outage, that’s the fault of humans not reviewing correctly. These senior engineers will get fucked in all scenarios.