10 interesting stories served every morning and every evening.
Draw an iceberg and see how it will ﬂoat.
Icebergs are less dense than water, so they always ﬂoat with about 10% of their mass above the water. But which way up? An iceberg wouldn’t ﬂoat exactly like on this page in reality. Its three-dimensional distribution of mass and its relative density compared to the water are both significant factors that are only approximated here.
Today I channeled my energy into this very unofﬁcial but passionate petition for scientists to start drawing icebergs in their stable orientations. I went to the trouble of painting a stable iceberg with my watercolors, so plz hear me out.
— Megan Thompson-Munson (@GlacialMeg) February 19, 2021
Today we are pleased to announce Total Cookie Protection, a major privacy advance in Firefox built into ETP Strict Mode. Total Cookie Protection conﬁnes cookies to the site where they were created, which prevents tracking companies from using these cookies to track your browsing from site to site.
Cookies, those well-known morsels of data that web browsers store on a website’s behalf, are a useful technology, but also a serious privacy vulnerability. That’s because the prevailing behavior of web browsers allows cookies to be shared between websites, thereby enabling those who would spy on you to “tag” your browser and track you as you browse. This type of cookie-based tracking has long been the most prevalent method for gathering intelligence on users. It’s a key component of the mass commercial tracking that allows advertising companies to quietly build a detailed personal proﬁle of you.
In 2019, Firefox introduced Enhanced Tracking Protection by default, blocking cookies from companies that have been identiﬁed as trackers by our partners at Disconnect. But we wanted to take protections to the next level and create even more comprehensive protections against cookie-based tracking to ensure that no cookies can be used to track you from site to site as you browse the web.
Our new feature, Total Cookie Protection, works by maintaining a separate “cookie jar” for each website you visit. Any time a website, or third-party content embedded in a website, deposits a cookie in your browser, that cookie is conﬁned to the cookie jar assigned to that website, such that it is not allowed to be shared with any other website.
In addition, Total Cookie Protection makes a limited exception for cross-site cookies when they are needed for non-tracking purposes, such as those used by popular third-party login providers. Only when Total Cookie Protection detects that you intend to use a provider, will it give that provider permission to use a cross-site cookie specifically for the site you’re currently visiting. Such momentary exceptions allow for strong privacy protection without affecting your browsing experience.
In combination with the Supercookie Protections we announced last month, Total Cookie Protection provides comprehensive partitioning of cookies and other site data between websites in Firefox. Together these features prevent websites from being able to “tag” your browser, thereby eliminating the most pervasive cross-site tracking technique.
To learn more technical details about how Total Cookie Protection works under the hood, you can read the MDN page on State Partitioning and our blog post on Mozilla Hacks.
Total Cookie Protection touches many parts of Firefox, and was the work of many members of our engineering team: Andrea Marchesini, Gary Chen, Nihanth Subramanya, Paul Zühlcke, Steven Englehardt, Tanvi Vyas, Anne van Kesteren, Ethan Tseng, Prangya Basu, Wennie Leung, Ehsan Akhgari, and Dimi Lee.
We wish to express our gratitude to the many Mozillians who contributed to and supported this work, including: Selena Deckelmann, Mikal Lewis, Tom Ritter, Eric Rescorla, Olli Pettay, Kim Moir, Gregory Mierzwinski, Doug Thayer, and Vicky Chin.
Total Cookie Protection is an evolution of the First-Party-Isolation feature, a privacy protection that is shipped in Tor Browser. We are thankful to the Tor Project for that close collaboration.
We also want to acknowledge past and ongoing work by colleagues in the Brave, Chrome, and Safari teams to develop state partitioning in their own browsers.
I’m a 19-year-old girl in Gaza, Palestine studying Computer Engineering who just was selected for a summer internship at Google and Repl.it. I never imagined this is possible. I am sharing my story hoping it will help people in any way!
I became passionate about programming in high school. My teacher selected me for a robotics competition. We built a line follower robot using Arduino. I totally loved the logic behind programming.
I started taking online courses to learn how to program: an Edx class called “Introduction to Computer Science” and I also joined Technovation, a coding competition for high school girls. We built an app using App Inventor which is similar to Scratch. Gaza Sky Geeks connected us to mentors to help us with building the app. It helped physically abused women reach specialists for help. I loved building something so useful.
I was really excited to study Computer Engineering in university but I was nervous about ﬁnding a job after university. In Gaza, there is such high unemployment. Even Computer Engineering graduates face unemployment.
The university program was mostly focused on theoretical fundamentals about technology and computers. I thought I needed something more practical. Lucky me I saw a Facebook post for a fullstack software development bootcamp called RBK in Jordan. It used a Silicon Valley based Hack Reactor curriculum and was focused on hands-on experience and it had a scholarship from Anera.
I applied and was thrilled to be one of 30 who were accepted with the scholarship out of an applicant pool of ~800. I don’t know if you know how unusual it is for an 18-year female to leave Gaza. Thankfully my family was supportive and we were able to get the permits.
At RBK I built 3 fullstack apps using the MERN stack using agile development. I loved working with my scrum team and I think we learned a lot about soft skills, how to work with a team and meet deadlines.
I came back to Gaza and lucky me, I saw another Facebook post in one of the tech facebook groups for Gazans. The post was about Manara which connects people in Palestine and the Middle East to jobs or internships at global tech companies. I thought “Is that even possible?”!
I got excited and applied and got in. We started the ﬁrst two months with technical prep. Doing Leetcode, Pramp, and weekly lectures and homework on Data Structure and Algorithm assignments. I used to think that solving coding problems was torture. But I started enjoying this kind of challenge. I competed with my classmates to see who could solve more, and discussing our solutions. It was really interesting to see how different people solved the same problem.
We also got access to Educative.io course “Grokking the Coding Interview: Patterns for Coding Questions” which really helped me organize all the learning.
Here it comes the interesting part, we had the chance to e-meet with Silicon Valley engineers and practice interviews with them. That really made a difference. I practiced their advice every day. They were all so nice and supportive. Some of them even told me how difﬁcult interviews used to be when they started practicing.
The studying was very intense but I felt motivated because of my classmates, mentors, mock interviewers, and the Manara staff. Most of my classmates got a “hire” recommendation on a mock interview before I did. That motivated me to work even harder!
In October 2020 Manara provided referrals to Repl.it and Google. It was amazing. I knew I would apply to Google but I didn’t know about Repl.it. Repl.it is my best friend as a developer. I use it every day. I didn’t realize I could work there!
In November 2020, my applications for Google and Repl.it were both accepted and the interviews were scheduled soon after. I had my midterm exams with university during that time so I asked if it is possible to reschedule Google interviews for two more weeks so I have the time to prepare. The recruiters are so understanding and my interviews were rescheduled.
I still didn’t feel I was ready. I studied 10 hours a day. And that’s when I got my ﬁrst “hire” recommendation on a mock interview, just a few days before my Google interview. I started feeling more conﬁdent and that motivated me to work even harder.
In December 2020, I had my interviews at both companies.
At Google there were interviews exactly like what Manara prepared us for: data structures & algorithms problem-solving. Each interview was an hour long and they were on the same day with an hour break between. The interviewers were super nice and that helped me through the interview. I was able to discuss the thinking process out loud while coding. I can say that I had a really fun time making the interviews.
Repl.it’s interviews were really different. First they gave me an operational transformation homework assignment. This was completely new for me. The interviewer talked to me about the assignment and again it felt more like we were having a discussion, sharing ideas we had. I felt well-prepared for the questions I received during the interview, they were just like the homework assignment.
For my second interview, about two weeks later, I had to prepare a presentation with ideas to improve the product. Manara connected me to a mentor to practice my presentation and that gave me the conﬁdence that I was ready.
At Repl.it the interviewer was the same person each time, and he was really smart & funny!
On January 1, 2021, I received an email from Repl.it letting me know that I had been selected. That was the BEST new year’s day I’ve ever had!
Later in January I received an email from my Google recruiter to inform me that I got positive feedback on the interviews and had passed the Google hiring committee. That was a feeling that I will never forget!
At Google I still had to ﬁnd a team. A few days later, my recruiter emailed me because there was a potential team interested in me. I had a 30-minute “intern placement interview call.” The call was nothing technical, it was to get to know the team’s mission and ﬁnd out if the intern is interested in joining, and to let the team know about my skills.
A few days later, my recruiter informed me that I got matched with the team and that I had reached the ﬁnal step of the process which is obtaining approval for my offer! HOW AMAZING — I almost couldn’t believe it!!
Now, here I am, with offers from two of the most famous tech companies in the world! I got a little stressed actually… I wanted to do both but they said I can’t because they’re both during the summer.
What I loved about Repl.it was the feeling that I could explore different areas: frontend, backend, infrastructure. I’m still young and I’m not really sure yet what I’ll want to do so a company that lets me explore like this would be ideal! I also really liked the recruiter and the engineer who interviewed me and felt like I ﬁt into the team.
I chose Google because they will send me to Europe for the internship. Having the chance to spend the summer in Europe will be life-changing for me. I’ve never been on an airplane before. My only time out of Gaza was when I went to RBK in Jordan! And I think I will learn a lot at Google.
I’m also really excited about earning money. I want to help my parents pay for my younger brother’s education and maybe I can help others too.
I am so proud to say that 4 out of 6 people who applied to Google from my Manara cohort got offers there. We will meet for the ﬁrst time in Europe this summer! The other 3 classmates (Muath, Mohammed, and Hamza) live in the West Bank. I live in Gaza. It’s not far away but I can’t go to the West Bank and they can’t come here. I can’t wait to take a selﬁe in front of the Google ofﬁce together and share it with everyone at Manara. :-)
I traveled close to the West Bank once when I was going to Jordan for RBK but the permit I had only let me go straight to the border, I wasn’t allowed to stop on the way.
I am so thankful for everything and everyone that helped through this journey and especially everyone at Manara!! Thank you to all the mentors, mock interviewers, and staff!
Sign up or login to join the discussions!
Sign up to comment and more
Citibank just got a $500 million lesson in the importance of UI design
Citibank was trying to make $7.8M in interest payments. It sent $900M instead.
A federal judge has ruled that Citibank isn’t entitled to the return of $500 million it sent to various creditors last August. Kludgey software and a poorly designed user interface contributed to the massive screwup.
Citibank was acting as an agent for Revlon, which owed hundreds of millions of dollars to various creditors. On August 11, Citibank was supposed to send out interest payments totaling $7.8 million to these creditors.
However, Revlon was in the process of reﬁnancing its debt—paying off a few creditors while rolling the rest of its debt into a new loan. And this, combined with the confusing interface of ﬁnancial software called Flexcube, led the bank to accidentally pay back the principal on the entire loan—most of which wasn’t due until 2023.
On Flexcube, the easiest (or perhaps only) way to execute the transaction—to pay the Angelo Gordon Lenders their share of the principal and interim interest owed as of August 11, 2020, and then to reconstitute the 2016 Term Loan with the remaining Lenders—was to enter it in the system as if paying off the loan in its entirety, thereby triggering accrued interest payments to all Lenders, but to direct the principal portion of the payment to a “wash account”—“an internal Citibank account… to help ensure that money does not leave the bank.”
The actual work of entering this transaction into Flexcube fell to a subcontractor in India. He was presented with a Flexcube screen that looked like this:
The subcontractor thought that checking the “principal” checkbox and entering the number of a Citibank wash account would ensure that the principal payment would stay at Citibank. He was wrong. To prevent payment of the principal, the subcontractor actually needed to set the “front” and “fund” ﬁelds to the wash account as well as “principal.” The subcontractor didn’t do that.
Citibank’s procedures require that three people sign off on a transaction of this size. In this case, that was the subcontractor, a colleague of his in India, and a senior Citibank ofﬁcial in Delaware. All three believed that setting the “principal” ﬁeld to an internal wash account number would prevent payment of the principal. As he approved the transaction, the Delaware supervisor wrote: “looks good, please proceed. Principal is going to wash.”
But the principal wasn’t going to wash. When the subcontractor conducted a routine review the next morning, he noticed there was something drastically off about the previous day’s ﬁgures. Citibank had actually sent out almost $900 million, not the $7.8 million it was trying to send.
Citibank then scrambled to get the funds back, notifying each creditor that the principal payments had been made by mistake. Some of the creditors sent the money back. But others refused, leaving Citibank out $500 million.
Ordinarily, paying back a loan early wouldn’t be a big deal, since the parties could simply negotiate a new loan on similar terms. But in this case, some of the lenders were not on good terms with Revlon and Citibank.
Earlier in the year, as the pandemic was accelerating, Revlon experienced ﬁnancial difﬁculties and sought to borrow more money. To do that, Revlon convinced a majority of its previous creditors to allow it to transfer collateral from its old loan to a new one.
The strong-arm tactic angered the other creditors, who felt that the reduced collateral could leave them holding the bag if Revlon ran out of money. That’s more than a theoretical concern: Bloomberg’s Matt Levine reports that Revlon’s debt is “trading at around 42 cents on the dollar.” But under the terms of the loan, the minority lenders didn’t have a way to force early repayment.
So Citibank’s screwup allowed Revlon’s creditors to claw back cash that it might otherwise have never gotten back. And it could leave Revlon in a precarious ﬁnancial situation if the company can’t get the money back from the old lenders and can’t ﬁnd new lenders willing to replace the funds. Though given its screwup, Citibank could possibly end up as Revlon’s new creditor.
Citibank sued, arguing that it was entitled to get the money back since the cash was sent out by mistake. Ordinarily, the law would be on Citibank’s side here. Under New York law, someone who sends out an erroneous wire transfer—for example, sending a payment to the wrong account—is entitled to get the money back.
But the law makes an exception when a debtor accidentally wires money to a creditor. In that case, if the creditor doesn’t have prior knowledge the payment was a mistake, it’s free to treat it as a repayment of the loan. Judge Furman ruled that that principle applies here, even though Citibank notiﬁed its creditors of the mistake the very next day. The defendants noted that the amounts they received matched the amounts Revlon owed down to the penny, making it reasonable for them to assume it was an early repayment of the loan.
Furman also argued that it was reasonable for the creditors to assume that a bank as sophisticated as Citibank wouldn’t send out such a large amount of money by accident.
“To believe that Citibank, one of the most sophisticated ﬁnancial institutions in the world, had made a mistake that had never happened before, to the tune of nearly $1 billion—would have been borderline irrational,” he wrote.
The case isn’t over, however. Furman has ordered the creditors to keep the funds in escrow to give Citibank time to appeal his ruling.
“We strongly disagree with this decision and intend to appeal,” Citibank said in a statement. “We believe we are entitled to the funds and will continue to pursue a complete recovery of them.
Timothy B. Lee
Timothy is a senior reporter covering tech policy, blockchain technologies and the future of transportation. He lives in Washington DC.
Daft Punk, the Parisian duo responsible for some of the most popular dance and pop songs ever made, have split. They broke the news with an 8-minute video titled “Epilogue,” excerpted from their 2006 ﬁlm Electroma. Asked if Daft Punk were no more, their longtime publicist Kathryn Frazier conﬁrmed the news to Pitchfork but gave no reason for the breakup.
Thomas Bangalter and Guy-Manuel de Homem-Christo formed Daft Punk in Paris in 1993, helping to deﬁne the French touch style of house music. Their debut album, 1997’s Homework, was a dance music landmark, featuring classic singles “Around the World” and “Da Funk.” By the release of its follow-up, Discovery, in 2001, the duo had taken to making public appearances in the robot outﬁts that became their trademark. The singles “One More Time” and “Harder, Better, Faster, Stronger” cemented them as global superstars. Their imprint in the popular imagination continued to deepen in subsequent years, with records including third album Human After All, live LP Alive 2007, and the Tron: Legacy soundtrack album.
Twenty years into their career, Daft Punk blew up once more with “Get Lucky,” the lead single of their 2013 album Random Access Memories. The ubiquitous track sold millions of copies around the world and won two Grammys for the duo and guests Nile Rodgers and Pharrell Williams, both of whom also featured on follow-up single “Lose Yourself to Dance.” Random Access Memories earned Daft Punk a further three Grammys, including Album of the Year, and the ceremony hosted one of the last stagings of their spectacular live show. “When you know how a magic trick is done, it’s so depressing,” Bangalter told Pitchfork in a 2013 Cover Story. “We focus on the illusion because giving away how it’s done instantly shuts down the sense of excitement and innocence.”
The year of Random Access Memories’ release, Daft Punk were also credited with co-production on several tracks from Kanye West’s Yeezus, including the formidable opening trio of “On Sight,” “Black Skinhead,” and “I Am a God.” They would go on to collaborate with the Weeknd on the 2016 single “Starboy”—Daft Punk’s ﬁrst Billboard singles chart topper—as well as a second hit, “I Feel It Coming.”
Beyond the singles, their visual identity, interstellar mystique, and party-music ethos inspired generations of artists across genres. LCD Soundsystem’s breakout song, “Daft Punk Is Playing at My House,” captured the duo’s paradoxical embodiment of hipster cool even as their singles dominated airwaves. They released several batches of incredible holiday merch. They were sampled by R&B greats Janet Jackson and Jazmine Sullivan, parodied in Family Guy and Powerpuff Girls, and celebrated in art galleries around the world. Watch their farewell video below.
This article was originally published on Monday, February 22 at 9:40 a.m. Eastern. It was last updated on February 22 at 11:37 a.m. Eastern.
Build smaller, faster, and more secure
desktop applications with a web frontendcompatibility with any front-end framework means you don’t have to change your stackrelicensing is possible with Taurisize of a Tauri App can be less than 600KBis the Tauri-Team’s biggest priority and drives our innovationare here to help you choose important features with simple conﬁgurationcompilation allows to bundle binaries for major desktop platforms (mobile & WASM coming soon)Notice: This roadmap is subject to change. Generate, develop and build Tauri apps from the command line.Finalize, audit, write documentation and create examples for the smoke-tests.Bundle for all major desktops from native systems.Use a splashscreen while the main content is loading.Build your Web application as a Tauri binary for MacOS, Linux and WindowsOpt-in feature enabling for iframe dialog with Tauri and the native API.Run a command that is no longer available after ﬁrst run.Manufacture WASM bundler for use in websites.Stable on On all Platforms.Go, Nim, Python, C++ and other bindings are possible with the stable API.A decompiler and threat analyzer for Tauri Apps, using Frida.Something missing? Got a great idea? We want you to help us make it happen.
Program ScheduleKJZZ’s Here and NowPodcastsStories You Don’t Want to MissAbout
Latest News On COVID-19 | Map: Cases And Deaths In Arizona | FAQ About Vaccines In Arizona
Whistleblowers: Software Bug Keeping Hundreds Of Inmates In Arizona Prisons Beyond Release Dates
According to Arizona Department of Corrections whistleblowers, hundreds of incarcerated people who should be eligible for release are being held in prison because the inmate management software cannot interpret current sentencing laws. KJZZ is not naming the whistleblowers because they fear retaliation. The employees said they have been raising the issue internally for more than a year, but prison administrators have not acted to ﬁx the software bug. The sources said Chief Information Ofﬁcer Holly Greene and Deputy Director Joe Proﬁri have been aware of the problem since 2019.The Arizona Department of Corrections conﬁrmed there is a problem with the software.As of 2019, the department had spent more than $24 million contracting with IT company Business & Decision, North America to build and maintain the software program, known as ACIS, that is used to manage the inmate population in state prisons.One of the software modules within ACIS, designed to calculate release dates for inmates, is presently unable to account for an amendment to state law that was passed in 2019.Hear Jimmy Jenkins’ Interview With Host Steve Goldstein On The Show
Your browser does not support the audio element.
Senate Bill 1310, authored by former Sen. Eddie Farnsworth, amended the Arizona Revised Statutes so that certain inmates convicted of nonviolent offenses could earn additional release credits upon the completion of programming in state prisons. Gov. Ducey signed the bill in June of 2019.But department sources say the ACIS software is not still able to identify inmates who qualify for SB 1310 programming, nor can it calculate their new release dates upon completion of the programming.“We knew from day one this wasn’t going to work” a department source said. “When they approved that bill, we looked at it and said ‘Oh, s–-.’”After repeated internal warnings, employees sent a report to department leadership in October, 2020, specifically detailing the software bug.Bug reports detailing the Department of Corrections’ inability to calculate SB 1310 releases.Bug reports detailing the Department of Corrections’ inability to calculate SB 1310 releases.“Currently this calculation is not in ACIS at all,” the report states. “ACIS can calculate 1 earned credit for every 6 days served, but this is a new calculation.”Instead of ﬁxing the bug, department sources said employees are attempting to identify qualifying inmates manually. Arizona Department of Corrections spokesperson Bill Lamoreaux said the department has been able to identify 733 inmates that are potentially eligible to take part in the early release programming, who are not currently enrolled in a program.“ADCRR is prioritizing those eligible for this type of release,” Lamoreaux said, “and will put them in program spaces as soon as an opening becomes available based on release timeline.”But sources say the department isn’t even scratching the surface of the entire number of eligible inmates.“The only prisoners that are getting into programming are the squeaky wheels,” a source said, “the ones who already know they qualify or people who have family members on the outside advocating for them.”Even if inmates are identiﬁed and they are able to complete the required programming for SB 1310 releases, department sources say the software is preventing the prisoners from getting the time they deserve taken off their sentences.“We can’t ﬁnd people to get them into the programs, and after they complete the programs, we still can’t get them out the door,” a source said. “These people are literally trapped.”→ Bill Would Allow Prison Releases During Public Health EmergenciesLamoreaux said “ADCRR is working with the vendor to update the software with the methodology and logic programmed for this new release criteria.”In the meantime, Lamoreaux conﬁrmed the “data is being calculated manually and then entered into the system.”Department sources said this means “someone is sitting there crunching numbers with a calculator and interpreting how each of the new laws that have been passed would impact an inmate.”“It makes me sick,” one source said, noting that even the most diligent employees are capable of making math errors that could result in additional months or years in prison for an inmate. “What the hell are we doing here? People’s lives are at stake.”
’Just The Tip Of The Iceberg’While the problems with sentence calculations are concerning, department sources say those programming issues are “just the tip of the iceberg.”According to the sources, the entire inmate management software program, known as ACIS, has experienced more than 14,000 bugs since it was implemented in November of 2019.“It was Thanksgiving weekend,” one source recalled. “We were killing ourselves working on it, but every person associated with the software rollout begged (Deputy Director) Proﬁri not to go live.”But multiple sources involved in the rollout said they were instructed by department leadership to “not say a word” about their concerns. “We were told ‘We’re too deep into it — too much money had been spent — we can’t go back now.’”Since the rollout, department sources say several other programs have failed to perform correctly, including modules that track inmate health care, head counts, inmate property, commissary and ﬁnancial accounts, religious afﬁliation, security classiﬁcation, and gang afﬁliations.“We have put people in cells together who are in conﬂicting gangs without realizing it,” a source said. “We can’t keep the right medication with seriously ill inmates when they are transferred to a new unit. We’re putting people in danger. It’s only a matter of time before someone gets killed or dies.”The sources said the ACIS software also makes it difﬁcult for employees to correct errors once they have been identiﬁed.“In one instance there was a disciplinary action erroneously entered on an inmate’s record,” a source said. “But there’s no way to back it out. So that guy was punished and he wasn’t able to make a phone call for 30 days. Those are the kinds of things that eat at you every day.”
“We have a couple modules they spent millions of dollars on that we can’t use at all,” a department source said. “The program that tracks inmate property is not working. So they went back to the old fashioned way of tracking it by hand with paper because the software wasn’t doing what it was supposed to.”The ACIS software system replaced an older program called AIMS that had been in operation for more than three decades. According to a 2019 presentation to the Joint Legislative Budget Committee, the Department of Corrections has spent more than $24 million replacing the inmate management system. A department spokesperson testiﬁed that requirements for the project were poorly scoped from the beginning, resulting in a contract that went millions of dollars over budget.A Department of Corrections contract amendment with the IT company Business & Decision for millions of dollars of additional servicesA 2020 audit of the Department of Corrections by the Arizona Department of Auditor General found nearly $1 million in unreconciled inmate trust accounts. According to the audit, the department blamed the unresolved accounts on the transition to the new software system.“During the data migration from AIMS, a lot of records that should have not been transferred to the new system did, causing complications and a lot of manual work to resolve the conversion issues,” the audit states. “As with any new system, the lack of enough knowledge and experience of the staff, led to posting errors that additionally delays and complicates the reconciliation process.”One department whistleblower said the number of problems with the ACIS system was unprecedented in their professional experience. “I have never in my life run across an application like this,” they said. “It’s just been one big cluster.”All of the sources that spoke to KJZZ emphasized the need for more programming hours from the vendor that could be used on maintenance and support.“When they legislate these things, they need to be appropriating enough money to make sure they work,” a source said. They estimated ﬁxing the SB1310 bug would take roughly 2,000 additional programming hours.There are currently several bills in the Arizona Legislature that would expand eligibility for earned release credits to even more inmates than the standard set by SB 1310.Department of Corrections sources claim poor leadership is ultimately to blame for the continued IT problems. “There are choices being made like business decisions,” a source said, “when they need to be thinking about what’s in the best interest of the staff, and ultimately, what’s in the best interest of the inmates.”Another source said they were “disgusted” with the way the department has dealt with the software problems. “I’m embarrassed to be associated with people that don’t care enough to make these things a priority,” the source said. “It’s absolutely inhumane to keep people in prison longer than they are supposed to be.”In response to this report, a Department of Corrections spokesperson said claims of inmates being held beyond release dates were false, but admitted the ACIS system “does not currently calculate release dates in accordance with the parameters established by Senate Bill (S.B.) 1310.” The department maintains this has not delayed the release of any inmates.
An opera singer who traded the stage for the kitchen during the pandemic.
What questions do you have about the Valley and the state we call home?
For questions about programming, membership or anything else about KJZZ, please visit kjzz.org/contact.
Sign me up for KJZZ’s Stories You Don’t Want To Miss newsletter.
Please don’t publish my name.
This question is for testing whether or not you are a human visitor and to prevent automated spam submissions.
Solve this simple math problem and enter the result. E.g. for 1+3, enter 4.