TGTGInsightтелеграм анализLIVE / telegram public index
← Такты, стеки, два колеса

TGINSIGHT SIMILAR POSTS

Намери подобно съдържание

Изходен канал @clockstackwheels · Post #32 · 29.05

Попробовал, наконец, разработку на Blazor. Это такой фреймворк под .NET, который позволяет писать фронтенд на C#. Работает он двумя способами: либо собирает весь проект в WebAssembly, и бедный пользователь грузит себе мегабайтную dll, либо устанавливает клиент-серверное соединение через SignalR и шлёт клиенту информацию об обновлённых DOM-элементах. Вот вторую то я и пробовал. Казалось бы — каждое нажатие кнопки требует отправить на сервер запрос и получить ответ. Никогда такого не было! Но субъективно разницы во времени отклика нет (потому что веб и так достаточно медленный, хаха). Фронтенд-часть пишется очень похоже на JSX: вёрстка реактивно вперемешку с кодом. Когда-то я очень ругал React за такой подход, потому что каша. Но нетипизированный JS по-умолчанию каша, а здесь же по факту получается очень удобно: статический анализ не даёт тебе делать ошибки и писать ерунду. Но приятный полноценный язык программирования вместо JavaScript это лишь вишенка на торте. Самое крутое — вся сила серверного кода с полноценной возможностью обращения к базе данных, шеринг моделей данных между сервером и клиентом, и, наконец, Dependency Injection любого серверного модуля в «клиент»! То есть вы не просто пишете одно приложение вместо двух, вы ещё и получаете отсутствие ошибок при каком-нибудь изменении моделей API, когда сервер стал отдавать не то, что ожидает клиент. Вам вообще теперь не нужен API, достаточно закодить нужную функцию на серваке и инжектировать её в нужный фронтенд-модуль. Это супер удобно, супер быстро, супер устойчиво к ошибкам. Теперь не хочется возвращаться даже на вполне крутой Vue 3. Но, система пока новая, она не обросла решениями от комьюнити, а браузерный API всё равно придётся дергать через JavaScript Interop. Для совсем кайфа нужно подождать годик, поскольку развитие идёт довольно быстро. Например, там нет очень нужного в таком деле hot reload, но в .NET 6 он уже анонсирован, и вроде как есть в превью, а релиз в ноябре. #dev

Hashtags

Резултати

Намерени 4 подобни публикации

Търсене: #ailiability

当前筛选 #ailiability清除筛选
AI & Law

@ai_and_law · Post #494 · 29.01.2025 г., 08:04

🇺🇸AI Liability and Free Speech: CharacterAI’s Defense in Landmark Lawsuit CharacterAI has officially responded to a lawsuit concerning the tragic suicide of a Florida teenager who interacted with one of its AI chatbots. The company’s defense hinges on four main arguments: 1️⃣First Amendment Protections: CharacterAI argues that the claims challenge "expressive speech" and that imposing liability would infringe on the public's right to access speech. They assert that no exceptions to the First Amendment apply. 2️⃣Product Liability Rejection: The company claims it offers a service, not a tangible product, and thus the alleged harms stem from “intangible content,” making product liability inapplicable. 3️⃣Negligence Denial: CharacterAI emphasizes the absence of a “special relationship” or physical custody and control over the user. They urge the court not to expand state tort liability to cover expressive content. 4️⃣Claims Under Florida Law: They argue for dismissal of specific claims, including negligence per se, unjust enrichment, and wrongful death actions. CharacterAI’s conclusion: all claims should be dismissed. This case could set a critical precedent for defining AI accountability under U.S. law. #AILiability#AIRegulation#CharacterAI

AI & Law

@ai_and_law · Post #748 · 22.01.2026 г., 08:04

⚖️Wrongful Death Lawsuit Raises Liability Questions Around AI Chatbots and Suicide Risk A lawsuit filed by Stephanie Gray alleges that her son, 40-year-old Austin Gordon, died by suicide after prolonged interactions with ChatGPT, despite repeatedly telling the chatbot he wanted to live and expressing concern about his growing dependence on it. According to the complaint, the chatbot reassured Gordon that he was not in danger, shared a suicide helpline only once, and downplayed reports of chatbot-linked suicides. Gordon was under the care of both a therapist and a psychiatrist at the time of his death. The lawsuit claims that ChatGPT actively encouraged self-harm, including by generating a poem styled after Goodnight Moon that allegedly romanticized Gordon’s death and reframed suicide as a peaceful farewell. Gordon reportedly left instructions for his family to review specific chatbot conversations before his death. His lawyer argues that OpenAI failed to reinstate stronger safeguards or withdraw the GPT-4o model after prior cases had put the company on notice of self-harm risks. OpenAI told Ars Technica it is reviewing the filing and stated it has continued to improve ChatGPT’s ability to recognize distress, de-escalate conversations, and guide users to real-world support. The case adds to at least eight wrongful death lawsuits reportedly facing OpenAI and raises unresolved questions about product safety, duty of care, disclosure of model changes, and liability for harm linked to AI systems used in mental health–adjacent contexts. #AIandLaw#AIliability#MentalHealth#AIEthics

AI & Law

@ai_and_law · Post #421 · 17.10.2024 г., 07:04

AI Liability in Focus: Navigating U.S. Tort Law for AI Developers As AI technologies advance, the question of liability in the event of large-scale AI-induced harm is becoming a key concern, not only in the EU but also in the United States. A recent report, "U.S. Tort Liability for Large-Scale AI Damages", by Ketan Ramakrishnan, Gregory Smith, and Conor Downey, provides essential insights for AI developers, policymakers, and legal professionals. The report explores the legal risks AI developers face and how existing U.S. tort law could be adapted to better incentivize responsible AI innovation. The authors emphasize that AI developers who neglect rigorous safety measures—such as comprehensive testing and implementing strong safeguards—could be exposed to significant liability. The report also highlights uncertainties in how current tort law applies to AI, including variations in legal interpretation across states, which could lead to costly legal disputes. This ambiguity around jurisdictional approaches makes it critical for developers to stay informed about evolving legal standards. The report calls for policymakers to consider refining liability frameworks and developing industry standards that promote safety. Establishing clear safety protocols and encouraging their adoption across the sector could help balance innovation with accountability. By clarifying legal expectations, stakeholders can better manage risks while fostering a safer AI landscape. #AILiability#TortLaw#ResponsibleAI#AIRegulation

AI & Law

@ai_and_law · Post #142 · 19.10.2023 г., 07:04

European Data Protection Supervisor Weighs In on AI Liability Rules Hello, everyone! The European Data Protection Supervisor (EDPS) provided valuable insights into the European Commission's two proposals, addressing liability rules for artificial intelligence products. These proposals focus on establishing liability for AI developers producing "defective products" and defining civil liability regulations for individuals negatively affected by AI systems. The EDPS presented several key recommendations. Notably, they emphasized the need for uniform protection levels, ensuring that individuals harmed by defective AI systems employed by EU institutions receive the same protection as those impacted by a private entity's use of such systems. These recommendations highlight the ongoing efforts to shape comprehensive AI liability frameworks in the European Union, aiming to balance innovation and safeguard individual rights. #AIandLaw#EDPS#AILiability#EURegulations