If you can trivially avoid even the risk of offending someone — especially in a professional context — then why wouldn’t you?
2,180 karma · joined November 2, 2011
Socials: - josephredfern.at.hn - joseph@redfern.me - github.com/josephredfern - linkedin.com/in/josephredfern - reddit.com/user/j03
---
If you can trivially avoid even the risk of offending someone — especially in a professional context — then why wouldn’t you?
Then, after GCSEs, during A-levels, we were told (by the same teachers, in the same classrooms) to forget this model, and that the situation was actually more complicated, with s, p, d, f orbitals etc.
I realise that this is was a simplification and not necessarily an outright lie, and can understand why they did it this way. But it was the first time I realised I’d been deliberately taught something that was incomplete or inaccurate.
I think calling it a drop in replacement highlights that the aim of Zluda is to not require recompilation of the software being run. Maybe “Proof of concept drop in replacement” would be a better description?
If the tweet was claiming that it was ready to go for general use and that everyone should install it and use it as their daily driver, then I could see that the external boot disk caveat would be more significant... but it seems kind of irrelevant in the context of what they've achieved so far.
Is the CPU/SoC not the thing on which then operating system is running?
That said, I (like others) am a bit concerned about the lack of updates to Signal-Server (https://github.com/signalapp/Signal-Server/commits/master). Commits seemed to suddenly stop April last year, and I'd be very surprised if the actual Signal Server that's running in production hasn't been updated over such a long period. Would be very happy to be proven wrong here, or to be pointed in the direction of anything that might explain the lack of activity.
Parler was pretty much the antithesis of end to end encrypted and secure, and Signal serves a very different purpose to Parler. From what I've seen on Parler, their average user would dismiss Signal as being produced by commies and therefore evil, due to its Open Source license.
Termination Reason: Namespace CODESIGNING, Code 0x1
I can (re)sign the application with: codesign --force --deep --sign - /path/to/The.app
which often resolves the issue.but what's the difference between the error that causes the friendly warning, and the error that cases the stack trace/exception? Is this the difference between a lack of code signature and a failed check?
What's the point of using Ecosia if not to help them fund-raise for their environmental projects? Why not use Google or Bing directly (with an ad-blocker) and save the Ecosia the bandwidth costs?