Software engineer Rashiq Zahid debuted a web app today that uses a reverse-engineered version of McDonald's ordering API to query every single McDonald's in the United States. "Assuming a store has correctly indicated that ice cream is unavailable and that its ice cream machine isn't working, it'll show up as a little red dot on the McBroken map," reports Lifehacker. From the report: Zahid even built in a statistics box into McBroken so you can see how various cities compare for ice cream uptime. According to Zahid, his system works by queueing up nearly $20,000 worth of orders each minute. Don't worry; he's not placing them and cancelling them over and over, so no McDonald's worker has yet to dunk their head in the fryer as a result of Zahid's shenanigans. A number of different users on Twitter and Product Hunt have tested out Zahid's app by heading over to their local McDonald's restaurants and seeing what they can order. For the most part, the app checks out. Of course, there will still be occasional instances where a "working" ice cream machine actually isn't. Or, if you're lucky, you might find that an offline ice cream machine has since been reincarnated and that McDonald's simply forgot to note the change on their end. As for how long this little tool will exist before McDonald's gets wind of it and breaks its functionality, well, I'd place my ice cream order sooner than later.

Read more of this story at Slashdot.

An anonymous reader quotes a report from ZDNet: If you've been hiding under a rock -- and who could blame you these days? -- you may have missed how totally Kubernetes now dominates container orchestration. One way to quickly get up to speed on Kubernetes is with Canonical's MicroK8s. This is an easy-to-run and install mini-version of Kubernetes. And now Canonical has added autonomous high availability (HA) clustering to it. [...] Now, with HA, MicroK8s is ready to move from Internet of Things (IoT) implementations, testing out Kubernetes implementations on a workstation, or simply learning Kubernetes to bigger, better cloud jobs. With the new MicroK8s release, HA is enabled automatically once three or more nodes are clustered, and the data store migrates automatically between nodes to maintain a quorum in the event of a failure. Designed as a minimal conformant Kubernetes, MicroK8s installs, and clusters easily on Linux, macOS, or Windows. To work, a HA Kubernetes cluster needs three elements. Here's how it works in MicroK8s: -There must be more than one worker node. Since MicroK8s uses every node as a worker node, there is always another worker available so long as there's more than one node in the cluster. -The Kubernetes API services must run on one or more nodes so that losing a single node would not render the cluster inoperable. Every node in the MicroK8s cluster is an API server, which simplifies load-balancing and means we can switch instantaneously to a different API endpoint if one fails. -The cluster state must be in a reliable datastore. By default, MicroK8s uses Dqlite, a high-availability SQLite, as its datastore.

Read more of this story at Slashdot.

Wojtek Borowicz interviews David Heinemeier Hansson, the creator of the popular Ruby on Rails web development framework: Wojtek Borowicz: Software methodology is an industry of its own. There is Scrum, and Agile, and coaches, and books, and all of that. But you and your team at Basecamp don't follow these practices. Why? DHH: First of all, our approach to software development is heavily inspired by the Agile Manifesto and the Agile values. It is not so much inspired by the Agile practices as they exist today. A lot of Agile software methodologies focus on areas of product development that are not where the hard bits lie. They are so much about the procedural structures. Software, in most cases, is inherently unpredictable, unknowable, and unshaped. It's almost like a gas. It can fit into all sorts of different openings from the same basic idea. The notion of trying to estimate how long a feature is going to take doesn't work because you don't know what you're building and because humans are terrible at estimating anything. The history of software development is one of late or cancelled projects. If you were to summarize the entire endeavor of software development, you'd say: 'The project ran late and it got canceled.' Planning work doesn't work, so to speak. What we do at Basecamp we chose to label Shape Up, simply because that is where we find the hard work to be. We're trying to just accept the core constraint that it is impossible to accurately specify what software should do up front. You can only discover what software should do within constraints. But it's not like we follow the idea that it's done when it's done, either. That's an absolute abdication of product management thinking. What we say instead is: don't do estimates, do budgets. The core of Shape Up is about budgets. Not how long is something going to take but what is something worth. Because something could take a week or four months. What is it worth? [...] Wojtek Borowicz: So the problem with those methodologies is they put too much focus on estimating, which is inherently impossible with software? DHH: I'd go even further and say that estimation is bullshit. It's so imprecise as to be useless, even when you're dealing with fixed inputs. And you're not. No one is ever able to accurately describe what a piece of software should do before they see the piece of software. This idea that we can preemptively describe what something should do before we start working on it is bunk. Agile was sort of onto this idea that you need running software to get feedback but the modern implementations of Agile are not embracing the lesson they themselves taught.

Read more of this story at Slashdot.

An anonymous reader quotes a report from Ars Technica: An independent panel that assesses the safety of NASA activities has raised serious questions about the space agency's plan to test flight software for its Moon missions. During a Thursday meeting of the Aerospace Safety Advisory Panel, one of its members, former NASA Flight Director Paul Hill, outlined the panel's concerns after speaking with managers for NASA's first three Artemis missions. This includes a test flight of the Space Launch System rocket and Orion spacecraft for Artemis I, and then human flights on the Artemis II and III missions. Hill said the safety panel was apprehensive about the lack of "end-to-end" testing of the software and hardware used during these missions, from launch through landing. Such comprehensive testing ensures that the flight software is compatible across different vehicles and in a number of different environments, including the turbulence of launch and maneuvers in space. "The panel has great concern about the end-to-end integrated test capability plans, especially for flight software," Hill said. "There is no end-to-end integrated avionics and software test capability. Instead, multiple and separate labs, emulators, and simulations are being used to test subsets of the software." The safety panel also was struggling to understand why, apparently, NASA had not learned its lessons from the recent failed test flight of Boeing's Starliner spacecraft, Hill said. (Boeing is also the primary contractor for the Space Launch System rocket's core stage). Prior to a test flight of the Starliner crew capsule in December 2019, Boeing did not run integrated, end-to-end tests for the mission that was supposed to dock with the International Space Station. Instead of running a software test that encompassed the roughly 48-hour period from launch through docking to the station, Boeing broke the test into chunks. As a result, the spacecraft was nearly lost on two occasions and did not complete its primary objective of reaching the orbiting laboratory.

Read more of this story at Slashdot.

Long-time Slashdot reader Jeremy Allison - Sam shares an announcement from the Software Freedom Conservancy, detailing a new strategy toward improving compliance and the freedom of users of devices that contain Linux-based systems. From the post: The new work has received an initial grant from Amateur Radio Digital Communications (ARDC). Our new initiative features: 1) Litigation to enforce against license violators that do not voluntarily comply in a timely manner.2) Coordinating the development of alternative firmware for devices where none currently exists.3) Collaborating with other organizations to promote copyleft compliance as a feature for consumers to protect their privacy and get more out of their devices. We take this holistic approach because compliance is not an end in itself, but rather a lever to help people advance technology for themselves and the world. [...] ARDC has long served the amateur radio community who were early adopters of Internet communication. These roots have grown from the deeper soils of wireless and digital communication and open access to technical information. Amateur radio operators have long practiced the tradition of individual technical experimentation that benefited the general public. These traditions also form the basis of software freedom. Hobbyists and volunteers built, modified and improved Free and Open Source Software (FOSS) first. Conservancy defends the rights of software developers to examine the code in their devices and assists their work to improve the platforms they rely on and to understand our communication technologies. Copyleft compliance enables this work to continue and expand to new kinds of devices. [...] When companies prevent us from actually modifying the software on our devices, software freedom remains only theoretical. In this new chapter of compliance work, Conservancy will leverage its technical and legal resources to help the public take control of the software on which they rely. This generous grant from ARDC is a first step. Please help in the next step through support of Conservancy's work with a donation. You can also email [email protected] to let us know about GPL violations or to discuss volunteering on these projects.

Read more of this story at Slashdot.

An anonymous reader quotes a report from Motherboard: SINCE COVID-19 MANY AMERICANS FELL BEHIND IN ALL ASPECTS," reads the website copy. The button below this statement is not for a GoFundMe, or a petition for calling for rent relief. Instead, it is the following call to action, from a company called Civvl: "Be hired as eviction crew." During a time of great economic and general hardship, Civvl aims to be, essentially, Uber, but for evicting people. Seizing on a pandemic-driven nosedive in employment and huge uptick in number-of-people-who-can't-pay-their-rent, Civvl aims to make it easy for landlords to hire process servers and eviction agents as gig workers. Civvl aims to marry the gig economy with the devastation of a pandemic, complete with signature gig startup language like "be your own boss," and "flexible hours," and "looking for self-motivated individuals with positive attitudes:" "FASTEST GROWING MONEY MAKING GIG DUE TO COVID-19," its website says. "Literally thousands of process servers are needed in the coming months due courts being backed up in judgements that needs to be served to defendants." The company, at first glance, appears to be some kind of _Nathan For You-_esque prank: siccing precarious gig jobs onto vulnerable people. But Civvl is connected to a larger -- and real -- gig economy company called OnQall, which describes itself as an app that provides "on-demand task services to non-urban communities beyond main city areas." OnQall is the developer behind other, more believable TaskRabbit-esque apps, like LawnFixr, CleanQwik, and MoveQwik. Given the fact that Civvl is advertising all over the country and that OnQall, though not popular, does exist, it seems as though Civvl actually is an attempt to simplify the process of evicting people who cannot pay their rent during a pandemic.

Read more of this story at Slashdot.

A major focus of any smartphone release is the camera. For a while, all eyes were on the camera's hardware -- megapixels, sensors, lenses, and so on. But since Google's Pixel was introduced, there's been a lot more interest in the camera's software and how it takes advantage of the computer it's attached to. Marc Levoy, former distinguished engineer at Google, led the team that developed computational photography technologies for the Pixel phones, including HDR+, Portrait Mode, and Night Sight, and he's responsible for a lot of that newfound focus on camera processing. An excerpt from the wide-ranging interview: Nilay Patel: When you look across the sweep of smartphone hardware, is there a particular device or style of device that you're most interested in expanding these techniques to? Is it the 96-megapixel sensors we see in some Chinese phones? Is it whatever Apple has in the next iPhone? Is there a place where you think there's yet more to be gotten? Marc Levoy: Because of the diminishing returns due to the laws of physics, I don't know that the basic sensors are that much of a draw. I don't know that going to 96 megapixels is a good idea. The signal-to-noise ratio will depend on the size of the sensor. It is more or less a question of how big a sensor can you stuff into the form factor of a mobile camera. Before, the iPhone smartphones were thicker. If we could go back to that, if that would be acceptable, then we could put larger sensors in there. Nokia experimented with that, wasn't commercially successful. Other than that, I think it's going to be hard to innovate a lot in that space. I think it will depend more on the accelerators, how much computation you can do during video or right after photographic capture. I think that's going to be a battleground. Nilay Patel:When you say 96 is a bad idea -- much like we had megahertz wars for a while, we did have a megapixel war for a minute. Then there was, I think, much more excitingly, an ISO war, where low-light photography and DSLRs got way better, and then soon, that came to smartphones. But we appear to be in some sort of megapixel count war again, especially on the Android side. When you say it's not a good idea, what makes it specifically not a good idea? Marc Levoy: As I said, the signal to noise ratio is basically a matter of the total sensor size. If you want to put 96 megapixels and you can't squeeze a larger sensor physically into the form factor of the phone, then you have to make the pixels smaller, and you end up close to the diffraction limit and those pixels end up worse. They are noisier. It's just not clear how much advantage you get. There might be a little bit more headroom there. Maybe you can do a better job of de-mosaicing -- meaning computing the red, green, blue in each pixel -- if you have more pixels, but there isn't going to be that much headroom there. Maybe the spec on the box attracts some consumers. But I think, eventually, like the megapixel war on SLRs, it will tone down, and people will realize that's not really an advantage.

Read more of this story at Slashdot.

Last week, India banned another 118 apps with links to China. PUBG Mobile Lite and PUBG Mobile Nordic Map were included in that sweeping ban. Now, PUBG Corporation says it's looking for ways to bring the apps back to India. Engadget reports: The South Korean company was included in the ban because the mobile games are published by China's Tencent. In a statement shared today, PUBG Corporation said it will no longer use Tencent Games to publish the PUBG Mobile franchise in India. According to TechCrunch, prior to the ban, PUBG Mobile had more than 40 million monthly active users in India, so there's a strong incentive to restore the game. "Moving forward, PUBG Corporation will take on all publishing responsibilities within the country," it said. "As the company explores ways to provide its own PUBG experience for India in the near future, it is committed to doing so by sustaining a localized and healthy gameplay environment for its fans."

Read more of this story at Slashdot.

An anonymous reader quotes a report from The Associated Press: Every day, like clockwork, to-do lists for those protesting against Belarus' authoritarian leader appear in the popular Telegram messaging app. They lay out goals, give times and locations of rallies with business-like precision, and offer spirited encouragement. The app has become an indispensable tool in coordinating the unprecedented mass protests that have rocked Belarus since Aug. 9, when election officials announced that President Alexander Lukashenko -- whom some call "Europe's last dictator" -- had won a landslide victory to extend his 26-year rule in a vote widely seen as rigged. Peaceful protesters who poured onto the streets of the capital, Minsk, and other cities were met with stun grenades, rubber bullets and beatings from police. The opposition candidate, schoolteacher Sviatlana Tsikhanouskaya, left for Lithuania -- under duress, her campaign said -- and authorities shut off the internet, leaving Belarusians with almost no access to independent online news outlets or social media and protesters seemingly without a leader. That's where Telegram -- which often remains available despite internet outages, touts the security of messages shared in the app and has been used in other protest movements -- came in. Some of its channels helped unconnected, scattered rallies mature into well-coordinated action. The people who run the channels, which used to offer political news, now post updates, videos and photos of the turmoil sent in from users, locations of heavy police presence, contacts of human rights activists and calls for new demonstrations -- something Belarusian opposition leaders have refrained from doing publicly themselves. Tens of thousands of people all across the country have responded to those calls. In a matter of days, the channels -- NEXTA, NEXTA Live and Belarus of the Brain are the most popular -- have become the main method for facilitating the protests, said Franak Viacorka, a Belarusian analyst and nonresident fellow at the Atlantic Council. "The fate of the country has never depended so much on one [piece] of technology," Viacorka said.

Read more of this story at Slashdot.