Ügyek

My granddaughter Lily is eleven years old. She wants a smartphone. Her mother, when she is sober, says yes because all the other kids have one. The school says it is useful for group projects. I say no. I am raising Lily because her mother got into trouble with pills, and I have been at this long enough to know that a phone at eleven is not a tool. It is a leash. A window into a world that has no business being in a childs hands yet. I have raised three kids of my own and now I am raising a fourth. I have seen what happens when kids get screens before they have the spine to handle them. I have seen aunts, cousins, neighbours hand their kid a phone at ten and then wonder why that kid cant hold a conversation, look an adult in the eye, or sit through a dinner without twitching. Boredom is good for a child. Boredom makes them think, makes them create, makes them figure out who they are. A smartphone kills boredom on sight and replaces it with endless distraction. But I am old enough to know I might be wrong. Maybe the world has changed and I am clinging to a rule that made sense in 1995 but not in 2026. Maybe a phone at eleven teaches responsibility. Maybe the kids who get one early learn digital literacy while the kids who dont fall behind. I want the community to weigh in with a binding decision because this is not about what Lily wants. It is about what is best for her, and I need facts, not opinions.

I have run a fantasy Premier League group for the past three seasons with a mix of colleagues from my clinic and old university friends. We wrote down every rule before the first draft — no verbal agreements, no handshake trades unless logged in the chat. We thought we had covered everything. Last week a manager discovered a loophole: the platform allows lineup substitutions after the Friday deadline if the game is postponed, even though our league rule says no changes after the first kick-off of the gameweek. The manager used it to swap out a player who got a red card on Saturday for a clean replacement on Sunday, winning their matchup by three points. Now the league is split. Half the managers say the loophole was in the platform code, not our written rules, so it is fair game. The other half say it violates the clear intent of our rule about deadline integrity, and that allowing it destroys the competitive foundation of the league. I have been through this before. A few years ago a similar dispute in a different league ended with half the members quitting, not because of the points but because nobody could agree on what the rules actually meant. The question is not about this one substitution. It is about whether a group of friends playing a game for fun can change the rules mid-stream by majority vote, or whether rule stability matters more than popular opinion. I want the community to weigh in with a binding decision so I can present it to my league and we can move forward with a clear framework.

For thirty years I have watched music critics and casual listeners alike argue that the mark of a great album is how it makes you feel. Emotional resonance. The gut punch. The tears. The nostalgia. And I think that is a lazy standard that lets mediocre production hide behind sentiment. Here is the problem with emotional resonance as the primary metric: it is entirely subjective and untestable. You cannot point to a specific moment in a song and say that is where the emotional depth is measured because you are describing your own reaction, not anything in the recording itself. One person hears a lo-fi bedroom recording and hears vulnerability. Another person hears it and hears a microphone that was placed in the wrong room. Both are describing the same recording. The difference is entirely in the listener, not in the work. Technical production quality is measurable. Mic placement, frequency spectrum balance, dynamic range, stereo imaging, mastering consistency, session musician execution. You can show someone where a compressor is pumping badly. You can A/B two recordings of the same song and a trained ear will tell you which one has better technical execution. These are facts, not feelings. I am not arguing that emotional response should be ignored. I am arguing that when we evaluate an album as a work of craft, the craft must come first. A song that makes you cry but was recorded through a potato is a lucky accident, not a good recording. If the production is sloppy, the arrangement is lazy, and the mix is muddy, then whatever feeling you had was despite the work, not because of it. The question before the court is this: when ranking or reviewing an album, should technical production quality be the primary criterion, with emotional resonance as a secondary consideration? Or should we continue the current practice of treating personal emotional response as the gold standard? This is a case. I want a binding decision because the music press has been getting this wrong for decades and someone needs to say it plainly.

I have been a high school guidance counselor in Columbus, Ohio for thirty-five years. Over that time I have watched the pendulum swing on student discipline more than once, and I have yet to see a policy that satisfies everyone. But the question I keep coming back to is this: when a student breaks a rule, what are we trying to achieve? Zero-tolerance policies became standard in the 1990s. They are clear, they are consistent, and they treat every infraction the same regardless of who the student is or what led to the behavior. A student brings a pocket knife to school — automatic suspension. A student gets into a fight — automatic suspension. The argument is that this removes bias from discipline, creates a predictable environment, and sends a message that certain behaviors simply will not be tolerated. There is comfort in knowing the rules apply to everyone equally. Restorative justice takes a different approach. Instead of asking what rule was broken and what punishment fits, it asks who was harmed, what needs to be repaired, and how the student can take meaningful accountability. A fight might lead to a mediated conversation between the students, a written reflection, and a commitment to repair the harm rather than three days at home playing video games. The evidence suggests restorative practices reduce repeat offenses and keep students engaged in school. But they take time, training, and a willingness to handle each case on its own terms. I have seen both sides work and both sides fail. Zero-tolerance has suspended students who clearly needed help, not punishment. Restorative justice has been applied inconsistently, with some students getting a conversation while others get a referral to the principal. I am not asking which approach is easier to administer. I am asking which one actually serves the students and the school community better. This is a question I wrestle with every semester, and I would value the community's advice on how to think about it clearly.

I spent forty years as an electrician in Berlin. I have walked into houses where a well-meaning homeowner replaced a socket and ended up with the entire floor on one overloaded circuit because they did not understand how the wires were meant to run. I have also seen work done by licensed colleagues that was just as bad: rushed, sloppy, hidden behind the wall because they knew the inspection was coming. The question is not whether electrical work should be safe. The question is whether the permit and licensed-contractor requirements are the right tool to guarantee that safety. On one side, the rule says any electrical work beyond replacing a bulb must be done by a certified electrician with a permit. This exists because electricity kills people quietly. A bad connection behind a wall can smoulder for weeks before it starts a fire, and by then the homeowner who did the work has no idea what they did wrong. The permit system is not about gatekeeping. It is about accountability. If a licensed electrician wires a house and it burns down, there is a paper trail, insurance, and a license that can be revoked. If a homeowner does it and it burns down, there is just a pile of ash and a question mark. On the other side, a homeowner who owns their property should have the right to work on it, provided the work is ultimately inspected and approved. Many countries allow this with the proper inspection step. The requirement for a licensed contractor adds thousands of euros to a simple job, prices out people who cannot afford a professional, and creates a system where the cost of compliance drives people to do the work anyway, but without telling anyone, so it never gets inspected at all. An inspection-after model would at least catch the dangerous work while letting competent homeowners save money. I have seen both sides play out in real houses. I want the jury to weigh in on which approach actually keeps people safer, and whether the cost of licensing is worth the safety it claims to provide.

Berlin has miles of abandoned railway corridors that have become de facto community green spaces, urban farms, and wildlife corridors. Should the city formalize this by designating them as Community Stewardship Zones managed by local residents?

I was in a refugee camp in Greece in 2017 when a young woman was denied medical care because she could not 'prove' she existed. Her documents had been lost crossing the Mediterranean. She had a phone with a mobile wallet containing a verifiable credential issued by a grassroots aid organization — but the camp clinic's policy required 'government-issued ID or UNHCR registration card.' The credential was real, the attestations were valid, and the issuing organization was recognized by every NGO in the camp. The clinic's protocol simply had no provision for it. That moment changed the direction of my career. I left Mozilla the year before to work on decentralized identifiers, but that field visit crystallized the question: are we building self-sovereign identity for the people who need it most, or for the people who already have documents? This trial asks the community to weigh in on whether humanitarian aid organizations — camp clinics, food distribution points, education programs, legal aid desks — should update their intake protocols to accept cryptographically verifiable credentials (DID-based, VC-standard) as primary proof of identity, alongside or in place of state-issued documents and UNHCR registration cards. The practical stakes are enormous. Verifiable credentials can survive conditions that destroy paper: water, fire, flight, theft. They can be issued by community organizations without state backing. They travel with the person, not the bureaucracy. They can encode educational credentials, vaccination records, professional certifications, and family relationships — none of which fit on a registration card. But the objections are real and must be addressed. Critics argue that accepting decentralized credentials in humanitarian contexts could fragment the identity landscape, creating a two-tier system where the documented have state IDs and the undocumented have 'lesser' digital credentials. They warn about exclusion of people without phones, about digital literacy barriers, about the risk of surveillance if the credential system is not truly self-sovereign. They point out that a corrupt or coerced aid worker can issue false credentials just as easily as a corrupt state official can forge papers — decentralization alone does not solve trust. I believe the answer is not to reject decentralized credentials but to build better threat models around their use: offline-capable verification, privacy-preserving selective disclosure, transparent governance of trusted issuer registries, and parallel paper-based workflows for those who cannot or will not use digital tools. But the first step is a community decision on whether the principle is sound. This trial asks: should humanitarian organizations accept self-sovereign identity credentials as primary proof of identity in displacement and refugee contexts?

When certifying safety-critical automotive software at the highest Automotive Safety Integrity Level (ASIL-D), should ISO 26262 and its national adoptions explicitly recognize memory-safe system programming languages such as Rust, provided the toolchain is qualified? Proponents argue that mandatory recognition would give OEMs and Tier-1 suppliers a compliant, low-risk path to eliminate entire classes of memory-safety defects that still plague C/C++ firmware in brake control, steering, and powertrain ECUs. Opponents warn the standard is deliberately technology-neutral and that explicit endorsement risks regulatory capture and a false sense of safety without rigorous tool qualification and systematic-fault evidence.

In 1995 former NFL star O.J. Simpson was tried in Los Angeles for the June 1994 murders of his ex-wife Nicole Brown Simpson and her friend Ron Goldman. The eight-month televised trial was watched by an estimated 150 million people when the verdict came on October 3, 1995: not guilty on both counts, after under four hours of deliberation. In 1997 a civil jury, applying the lower "preponderance of evidence" standard, found him liable for both deaths and awarded $33.5 million. Simpson died in April 2024. The question is whether the criminal jury reached the right verdict on the standard it had to apply — proof beyond a reasonable doubt — not simply whether you think he did it. The prosecution case: DNA evidence linking Simpson to the scene and the victims' blood in his Bronco and at his home, a history of domestic violence against Nicole, a matching shoe-print size, the bloody gloves, and his flight in the Bronco chase. The defence case: lead detective Mark Fuhrman was shown to have used racial slurs and later invoked the Fifth Amendment when asked if he planted evidence; the LAPD crime lab's handling of samples was sloppy; a criminalist carried a vial of Simpson's blood around for hours; and the bloody glove appeared not to fit ("If it doesn't fit, you must acquit"). Against the background of the 1992 Rodney King riots, many saw the verdict as a referendum on the LAPD as much as on Simpson.

In Roe v. Wade (1973) the US Supreme Court ruled 7–2 that the Constitution's guarantee of liberty under the Due Process Clause of the Fourteenth Amendment includes a right to privacy broad enough to cover a woman's decision to have an abortion. It set a trimester framework, later replaced in Planned Parenthood v. Casey (1992) by a viability line and an "undue burden" test. For nearly 50 years it was among the most debated rulings in American law. On June 24, 2022, in Dobbs v. Jackson Women's Health Organization, the Court overruled Roe and Casey 6–3, holding that the Constitution confers no right to abortion and returning the question to the states. This case asks a legal question, not a policy one: was Roe sound constitutional law? You can think abortion should be legal and still believe Roe was poorly reasoned (as some liberal scholars, including Justice Ruth Bader Ginsburg, argued about its breadth), or oppose abortion and still accept a privacy-based right as doctrine. Arguments that Roe was right: it built on a line of privacy and bodily-autonomy precedents (Griswold v. Connecticut, Eisenstadt v. Baird); the Fourteenth Amendment protects liberties not explicitly listed; and 50 years of reliance mattered. Arguments that it was wrong: abortion is not mentioned in the Constitution and was not a recognised right when the Fourteenth Amendment was ratified; the trimester scheme read like legislation; and on a contested moral question the Court should leave decisions to elected legislatures.