Saw a Tekever AR5 [1] fixed wing UAV on flightradar [2], and that led me to a Serious Incident report where both engines switched off as it was preparing to land. Fortunately an external pilot had line of sight and was able to land the UAV.
It seems that commands are sent as 11 bit values, 50 per second, and the command to send the "Ignition Off" value is any value over a set threshold.
From the doc: "A such, a single bit error would be sufficient to modify the 'Ignition ON' signal value so that it exceeded the 'Ignition OFF' threshold."
(This has now been fixed by the manufacturer so that there must be 10 consecutive Ignition OFF commands)
Ha - did the same phishing thing with our RM Nimbuses in the school computer lab. Wrote a turbo pascal program that showed the same login UI as the Nimbus. Logged into my own account on all machines and ran the program. When someone "logged in", it wrote their username and pw to a text file, and rebooted the machine (which got the user to the real login screen). Never got caught for that either, but also don't remember doing anything malicious with the info - I think it was more about the fun of the challenge :)
A forager friend of mine has just completed participating in a gut biome study (in conjunction with the UK Zoe project), where he and other foragers have been only eating wild foraged food for 3 months. A pretty good achievement for him (although he lost about 20kg over the 3 months). He blogged daily photos of what he ate on insta: https://www.instagram.com/rural_courses/
I semi-regularly refer colleagues to this article I read some years back "The Interruptible Programmer" - it argues that it's hard to stay in the zone, so instead accept that you're going to be interrupted and embrace it.
I remember using dogpile [1] (which was a search engine aggregator) - the results from google were consistently better than altavista, so over time I gravitated directly to google for results. These days I'm on Kagi...
> If anyone did have a credit card attached to their account, they're looking at it from the fraud angle. Everyone else is wondering if they're going to try to force some kind of debt collection because we are not going to pay, that's likely where the knives-out reactions are coming from.
"The general position under English law is that IP rights created by an employee within the course of employment automatically belong to the employer; where there is any doubt as to whether an employee or their employer owns IP rights, the relevant legislation largely favours employers."
"If material which includes IP rights is created outside office hours and/or using the employee’s private resources this may give rise to arguments that the rights belong to the employee rather than their employer, but that is not decisive. The fact that work is done outside normal working hours does not necessarily mean that the work is not done in the course of employment as, for many employees, there is often no clear demarcation of the hours of work."
"The key question to be asked is whether the work was the kind of work which the employee was employed to do i.e. whether it was within the scope of their employment. Could the employee have been ordered to do the work and would it have been a breach of contract for the employee to not do it? The terms of any contract of employment and job description will be relevant, however, these (and duties more generally) often evolve in the course of time and it may therefore not be appropriate to rely on them exclusively."
IANAL, but my reading of that is that if I wrote a novel about unicorns and rainbows, that wouldn't be owned by the company, but if I wrote software, it would.
Urgh - I got one of these - completely forgot that I'd set up a fogbugz account years ago. Don't know if these invoices are as a result of a hack, or whether it's because it's now owned by another company and they're pre-emptively "upgrading" previously free accounts to "paid" accounts in the hope that they're going to get some subscriptions...
The email had some vlaid account fogbugz account details, so it's at least coming from their database...
I've managed to get specific exclusions for IP I've worked on as a side project, and more recently got my employer to include the majority of the github "balanced employee ip agreement" [1] in our employment contracts, which states quite clearly "If you create IP outside the scope of your employment or contract or before or after your employment or contract ("Your IP"), the Company doesn't own it" [2]
(UK based company)
I once went for an interview, setup by a recruitment agency, in a town nearby. The job looked great, and it was a step up for my career. It was for a mature company that made software for the oil drilling industry amongst other things.
The interview went well, the coding test was good. Finally, I were just chatting with the CEO, and he asked "So you're ok with spending 2 years on site in Kazakhstan?"
Needless to say we both agreed that it was a wasted interview and that the recruitment agency should have mentioned the Kazakstan bit...