https://www.europesays.com/hu/284927/ Index – Sport – A székely hős, akinek volt bátorsága szembeszállni Adolf Hitlerrel #berlin #birkózás #HU #Hungarian #Hungary #korond #LőrinczMárton #mac #Magyar #Magyarország #olimpia #Sport #Sports #székelyudvarhely #tölgyfacsemete #ünnepség
Search
11 results for “akin”
-
We’re really living in the most stupid check-boxy times. My bank just messaged me that they made a change that has no impact on me, nothing has changed for me and I don’t need to take any action.
This is akin to them sending me a memo that Jack from accounting changed their hair colour.
Yet, somehow I bet there is some checkbox being checked by this…
-
【 #BuzzFeed #RSSfeed 】
「マジか！！」中森明菜の近影に「誰なんだよ？このお嬢さんは？」「女神すぎ」と反響
https://www.buzzfeed.com/jp/takamiyoshida/nakamori-akina-1016 -
Is there a Faircamp player/app? It would cool to be able to shuffle/favorite/playlist/share/(possible pay for, depending on the artists' setup??) available (opted-in) Faircamp songs. No stream counts or metrics or whatever, just discovery/exposure. I know @radiofreefedi was something akin to this. #faircamp
-
🚨 LIVE COVERAGE CLOSED. THE CRISIS IS NOT.
🔥 Tankers attacked. Hormuz traffic down 70%. Washington and Tehran both claim control. Yemen threatens to widen the war.
The alleged supertanker mine strikes remain unverified.
Our final assessment: Neither side has secured Hormuz. Both can still escalate. Diplomacy remains the only sustainable exit.
Read our closing report:
https://www.thelevantfiles.org/2026/10/breaking-live-supertanker-fire-raises.html -
🚨 HORMUZ ON FIRE. IRAN ON EDGE.
🔥 Tehran claims TWO supertankers struck naval mines. Explosions reported near Sirik. More vessels under attack as Washington and Tehran battle for control of the world's most critical oil chokepoint.
⚠️ The supertanker claims remain unverified. The danger to global shipping is real.
The Gulf crisis is spreading. Follow our LIVE coverage:
https://www.thelevantfiles.org/2026/10/breaking-live-supertanker-fire-raises.html
-
Migrating a legacy application is rarely a walk in the park. It's often a complex dance between maintaining existing functionality, introducing new features, and, if you're lucky, improving performance. When we decided to tackle our aging AngularJS codebase, the promise of a snappier user experience with React was a huge motivator. And let me tell you, the 30% performance improvement we saw wasn't just marketing hype; it was a game-changer.
Why Migrate? Beyond the Hype
Before diving into the 'how,' let's quickly touch on the 'why.' For us, it wasn't just about chasing the latest shiny framework. AngularJS, while revolutionary in its time, had several pain points that were becoming increasingly difficult to manage:- Performance Bottlenecks: Digest cycles, especially with complex two-way data binding and watchers, often led to sluggish UIs. Our app was feeling the weight.
- Developer Experience (DX): The learning curve for new team members was steep, and debugging often felt like navigating a maze. Modern React patterns offer a more intuitive, component-based approach.
- Ecosystem & Support: The community around AngularJS has naturally dwindled, making it harder to find up-to-date libraries, solutions, and talent.
- Maintainability: Large AngularJS applications can become difficult to refactor and scale. Components were tightly coupled, and testing was a chore.
React offered a compelling alternative with its virtual DOM, unidirectional data flow, and thriving ecosystem. The potential for a significant performance boost was the cherry on top.
The Gradual Approach: Strangler Fig Pattern to the Rescue
Rip and replace? Not for a mission-critical application. We adopted a strategy akin to the Strangler Fig pattern. The idea is to incrementally replace parts of the old system with new ones, letting the new system 'strangle' the old one until it's completely gone. This minimizes risk and allows for continuous delivery.Our strategy involved:
- Identifying Isolated Modules: We started with less critical, self-contained features or pages that could be rewritten in React without heavily impacting the core AngularJS app.
- Building a Bridge: The crucial part was making AngularJS and React components coexist and communicate. We used a simple wrapper pattern.
- Shared State Management: For larger applications, a shared state management solution (like Redux or Zustand) was key to avoid prop-drilling across the Angular/React boundary.
Bridging the Gap: A Simple Example
Let's say you have an AngularJS component that needs to render a new React component. You can create an AngularJS directive that acts as a wrapper.// angular-react-wrapper.js
import React from 'react';
import ReactDOM from 'react-dom';
import MyReactComponent from './MyReactComponent';angular.module('myAngularApp')
.directive('reactComponentWrapper', function() {
return {
restrict: 'E',
scope: {
props: '='
},
link: function(scope, element) {
const root = ReactDOM.createRoot(element[0]);scope.$watch('props', function(newProps) {
root.render(
<React.StrictMode>
<MyReactComponent {...newProps} />
</React.StrictMode>
);
}, true);scope.$on('$destroy', function() {
root.unmount();
});
}
};
});Then, in your AngularJS template:
<!-- angular-template.html -->
<react-component-wrapper props="angularData" />This simple setup allows your AngularJS app to pass data (
angularData) to your new React component (MyReactComponent).Measuring Success: The 30% Performance Boost
How did we quantify that 30%? It wasn't just a gut feeling. We focused on key metrics:- First Contentful Paint (FCP): How long until the first piece of content appears on the screen.
- Largest Contentful Paint (LCP): How long until the main content of the page is loaded.
- Time to Interactive (TTI): How long until the page is fully interactive and responsive to user input.
- Bundle Size: Smaller bundles mean faster downloads.
We used tools like Lighthouse, WebPageTest, and even simple
console.time()measurements for specific component render cycles. The results were consistent: pages rewritten in React consistently loaded faster and felt significantly more responsive.Where the Gains Came From:
- Virtual DOM: React's ability to minimize direct DOM manipulations dramatically reduced render times.
- Unidirectional Data Flow: Easier to reason about, leading to fewer unexpected re-renders and simpler performance optimizations.
- Component-Based Architecture: Encouraged smaller, more focused components, leading to better code splitting and lazy loading opportunities.
- Modern Tooling: Leveraging Webpack for optimized bundling, tree-shaking, and minification was far more effective than our older Gulp/Grunt setups.
Challenges Along the Way
No migration is without its bumps. We encountered:- State Management Complexity: Deciding how to manage global state across both frameworks initially required careful planning.
- Styling Consistency: Ensuring a consistent look and feel across AngularJS and React components required a robust design system or careful CSS management.
- Team Skill Gaps: Training the team on React best practices and modern JavaScript was an investment, but one that paid off handsomely.
- Testing: Rewriting tests for React components from scratch, while necessary, added to the workload.
Final Thoughts: Was it Worth It?
Absolutely. The performance boost was tangible, delighting both users and developers. The improved developer experience, the vibrant React ecosystem, and the future-proofing of our codebase made the effort worthwhile. If you're grappling with an aging AngularJS application, don't shy away from a gradual migration. It's a journey, but one that can lead to significant gains and a much healthier application.#angular #react #frontend #migration #software #coding #development #engineering #inclusive #community
Migrating from AngularJS to React: A 30% Performance Improvement Journey -
YSGOL HEOL GOFFA: Four pupils have died in six months, says councillor, and still no nurse
Four pupils at a Llanelli special school have died in the last six months, according to the town councillor campaigning for a full-time nurse on site.
Cllr Shaun Greaney says three of the children were pupils in the school’s Medical Services Unit, and another pupil died of a notifiable disease. He has not named the children or described their circumstances, out of respect for their families.
Campaigners have been calling for a registered nurse at Ysgol Heol Goffa for more than five years. Their pleas have gone to Hywel Dda University Health Board and the county council.
Cllr Greaney, the Labour town councillor who has led the town council’s push for a nurse, said: “The time taken to hold any kind of meaningful talks with frightened and worried parents, campaigners, and the school itself borders on criminal in my opinion.”
He went further: “The kindest comment I’ve heard about it is that it’s disheartening. But in fact it’s horrifying, disgusting, shameful.”
Hywel Dda gave no guarantee and no deadline at MP’s meeting, campaigners say
The action group recently met health board chiefs online, at a meeting convened by Llanelli MP Dame Nia Griffith. Cllr Greaney said the chiefs “could not give a guarantee a nurse would be employed, nor could they give a deadline for a decision”.
According to Cllr Greaney, Dame Nia told the meeting the case for a nurse at the school was all the stronger because Prince Philip Hospital has no paediatric department.
He said it was “encouraging that they finally listened to the overwhelming evidence presented to them”, with chiefs pledging “something would be done”. Apart from the health board seeking information about the children with epilepsy, though, he understands “not a lot has happened”.
Health chiefs also insisted no solution could be reached without the involvement of Carmarthenshire County Council, he said.
Ysgol Heol Goffa mum says the health board is “failing in its duty of care”
Llanelli mum Lana Dakin’s son Jac, eight, has Schinzel-Giedion syndrome, a rare genetic condition, and complex medical needs. She said the staff at Ysgol Heol Goffa “are great but they should not have to carry this alone”.
She said: “The children here have some of the most complex medical needs in our community. I am shocked, appalled, disgusted that the health board is not doing enough. The health board is failing in its duty of care.”
Lana Dakin with her son Jac, eight, a pupil at Ysgol Heol Goffa. (Image: Lana Dakin)Speaking about her son, she said: “Jac is not just a diagnosis. He is my son. He is loved.”
She said he deserved “the very best chance to learn, grow, thrive” and to “have the best quality of life”. “And so does every child at Ysgol Heol Goffa,” she added.
Her message to the health board was blunt: “Children like Jac should not have to wait. They deserve support now.”
Promised Welsh Government guidance still has no timescale
As far back as February, parents warned they had “been lucky to date that a child has not died”, as calls grew for a watchdog investigation.
Hywel Dda has previously pointed to its visiting community children’s nursing service. In August, Cabinet Minister for Health and Care Mabon ap Gwynfor said staff at the school were “assessed as competent”, and that a nurse was “a matter for the relevant local authority and health board“.
New guidance from the Welsh Government has been promised for some time in 2027. Last month, Cabinet Minister for Education and the Welsh Language Anna Brychan said the work was “at an early stage” and gave no timescale.
Cllr Greaney said: “As we’ve stressed all along, time is of the essence. If they wait until the Welsh Government produces new guidance in 2027, it could come too late to save a child’s life.”
Carmarthenshire Council and Hywel Dda could share the cost, councillor says
He saved his sharpest words for the county council: “It’s as if the Plaid Cymru-led county council has a death wish. We are not talking a huge sum of money.”
Split between the health board and the county council, he said, the bill would be “roughly about a figure akin to a council cabinet member’s salary with the potential of keeping children safe and alive”. He asked: “Who could begrudge the parents that peace of mind and have a clear conscience?”
Council rejects ‘modest cost’ claim and says school nursing is Hywel Dda’s job
Carmarthenshire County Council said it “does not accept the suggestion that it has refused to engage in finding a solution” for the school.
Cllr Glynog Davies, the council’s cabinet member for education, said it had “repeatedly raised concerns about nursing provision” with the health board, the Welsh Government, the school and the Children’s Commissioner for Wales. He pointed to Welsh Government guidance that every special school should have access to at least one dedicated registered nurse employed by the health board.
Responsibility for commissioning and delivering school nursing in Carmarthenshire “rests with Hywel Dda University Health Board”, he said, adding that it was “misleading to characterise the issue simply as the Council refusing to share a ‘modest cost'”.
Any future model had to settle “clinical responsibility, governance, staffing and funding” between the organisations responsible, he said, and the council wanted those talks “brought to a clear and sustainable conclusion”.
He said the council would not comment on individual pupils, and that no “causal connection” should be drawn between any deaths and nursing provision “without clear clinical evidence”. There is “not currently a confirmed timescale for a final decision by the Health Board”, he added.
Hywel Dda says its community nursing team and staff training already cover the school
Hywel Dda said it supports the children at Ysgol Heol Goffa “with a specialist/community children nursing service to meet their universal health needs”, and by training the school’s staff.
Sharon Daniel, the health board’s director of nursing, quality and patient experience, said the health and wellbeing of children “is a priority for us” and that specialist support ensured each child with healthcare needs “can be cared for competently and confidently within the school environment”.
She said: “Through continued partnership working and a shared commitment to improvement, we will support ongoing actions to strengthen provision and ensure the best possible outcomes for the pupils and staff at Ysgol Heol Goffa.”
Related stories from Swansea Bay News
YSGOL HEOL GOFFA: Health minister said 2027. Education minister says no timescale. Still no nurse
Neither minister would say when a nurse comes.YSGOL HEOL GOFFA: No permanent nurse for seriously ill children at Llanelli special school as parents told to wait until 2027
The health minister’s letter that Lana Dakin called a “kick in the teeth”.LLANELLI: Minister urged to step in over ‘lifesaving’ school nurse battle as mum warns of preventable tragedy
The town council’s unanimous letter to the health minister.CHILDREN’S COMMISSIONER STEPS IN: Watchdog demands meeting with health board over special school nurse crisis
Rocio Cifuentes asked to meet Hywel Dda in February.‘Lives may be at risk’: Watchdog probe demanded over Llanelli special school nurse crisis
#AnnaBrychanMS #CarmarthenshireCouncil #CllrShaunGreaney #HywelDdaUniversityHealthBoard #Llanelli #MabonApGwynfor #NiaGriffithMP #PrincePhilipHospital #schoolNurse #specialSchool #WelshGovernment #YsgolHeolGoffa
Where the campaign stood in February. -
Introduction: The Persistent Threat of Exposed RDP
Exposing Remote Desktop Protocol (RDP) on Port 3389 directly to the internet constitutes a critical and persistent security vulnerability. This practice bypasses fundamental security controls, creating a direct pathway for unauthorized access. The mechanism is clear: an exposed RDP port enables attackers to initiate connection requests, exploiting the absence of robust pre-authentication safeguards. This exposure facilitates a range of attacks, including pre-authentication enumeration, credential stuffing, and the exploitation of known vulnerabilities such as BlueKeep (CVE-2019-0708). These are not theoretical risks; they are empirically observable. A Shodan search reveals thousands of systems with RDP exposed, many presenting pre-login interfaces that allow attackers to manipulate critical system controls—such as shutdown or restart functions—without authentication. This immediate access can lead to mechanical system failures through process termination or memory corruption, causing operational disruptions with tangible, physical consequences.The risk materializes through two primary vectors: misconfiguration and operational complacency. Misconfigurations, such as weak firewall rules or disabled Network Level Authentication (NLA), create exploitable gaps in the security posture. Simultaneously, organizations often underestimate the sophistication and efficiency of attackers, who leverage automated tools to scan for and target exposed RDP ports. The result is predictable: exposed systems become prime targets for ransomware attacks, data breaches, and unauthorized shutdowns. For example, a ransomware operator can exploit an exposed RDP port to deploy malware, encrypt critical files, and render systems inoperable by overwriting file headers or corrupting master boot records. Despite widespread awareness, the persistence of this issue underscores its criticality as cyber threats evolve to exploit such vulnerabilities.
The causal chain is unambiguous: Exposure → Exploitation → Impact. An attacker identifies an exposed RDP port (exposure), exploits weaknesses through brute-force attacks or vulnerability exploitation (exploitation), and gains control to execute malicious actions such as data exfiltration or system shutdown (impact). This sequence is not hypothetical; it is a recurring pattern in real-world incidents. Effective mitigation requires actionable measures: securing RDP behind a Virtual Private Network (VPN), enforcing granular firewall rules, or deploying an RD Gateway. Failure to implement these measures leaves organizations vulnerable to threats that can compromise operational integrity, overwhelm incident response teams, and cause systemic failures—both literally and metaphorically.
Case Studies: Real-World Consequences of Exposed RDP
Directly exposing Remote Desktop Protocol (RDP) on Port 3389 to the internet is not merely a theoretical vulnerability—it is a critical and persistent security risk. The following case studies, grounded in empirical observations from Shodan scans and technical analyses, demonstrate the cascading consequences of this oversight. Each scenario highlights the direct causal mechanisms through which exposed RDP leads to tangible, often catastrophic, outcomes.- Case 1: Unauthenticated Shutdown of Production Systems
A Shodan scan revealed a manufacturing plant’s Windows server with RDP exposed without authentication. The pre-login interface displayed active shutdown and restart options. Causal Mechanism: An attacker could exploit this exposure to terminate critical system processes, directly halting industrial machinery. For instance, abrupt shutdown of a CNC machine’s spindle mid-operation would induce thermal shock and mechanical stress, deforming the workpiece and potentially damaging the tool.
- Case 2: Ransomware Deployment via Exposed RDP
A healthcare provider’s server, accessible via RDP without Network Level Authentication (NLA), was compromised by ransomware operators. Causal Chain: Attackers exploited weak credentials through brute-force attacks, gained administrative access, and deployed ransomware that encrypted patient records and corrupted the master boot record. Physical Consequence: Medical devices dependent on the server’s database failed to retrieve critical calibration data, resulting in inaccurate diagnostic outputs and direct patient harm.
- Case 3: Data Exfiltration from a Financial Firm
Misconfigured firewall rules exposed a financial firm’s RDP port, enabling attackers to exfiltrate sensitive transaction logs. Technical Process: Attackers employed credential-dumping tools such as Mimikatz to extract plaintext credentials from memory, bypassing encryption protocols. Observable Impact: The exfiltration process triggered sustained I/O spikes, causing disk thrashing and irreversible corruption of active transaction files.
- Case 4: BlueKeep Exploitation in a Utility Company
A utility company’s Windows 7 server, exposed via RDP, was vulnerable to the BlueKeep exploit (CVE-2019-0708). Exploitation Mechanism: Attackers remotely executed arbitrary code to overwrite kernel memory, triggering a system crash. Physical Consequence: The compromised server controlled a SCADA system, leading to a grid-wide power outage as control mechanisms failed to respond to load fluctuations.
- Case 5: Credential Stuffing Attack on a Retailer
An exposed RDP port at a retailer enabled attackers to deploy a credential-stuffing tool using stolen credentials. Causal Sequence: Successful authentication allowed attackers to install a kernel-level keylogger, capturing employee credentials. System Impact: The keylogger’s persistent CPU utilization caused thermal throttling, leading to degraded performance of connected POS systems and transaction failures during peak operational hours.
- Case 6: Unauthorized System Restart in a Data Center
A data center’s RDP interface, accessible without authentication, displayed a restart option. Mechanical Impact: An unauthorized restart initiated a filesystem integrity check (chkdsk) on a RAID array, causing rapid repositioning of read/write heads. Physical Consequence: The mechanical stress induced a head crash, physically damaging the disk platter and rendering the array permanently inaccessible.
These cases are not isolated incidents but recurring patterns that underscore the mechanical, observable, and devastating consequences of exposed RDP. The risk is not theoretical—it is a direct pathway to compromising both digital and physical infrastructure. Exposing RDP to the internet does not merely invite attackers; it provides them with unfettered access to the core mechanisms of your operational integrity.
Best Practices and Mitigation Strategies
Directly exposing Remote Desktop Protocol (RDP) on Port 3389 to the internet constitutes a critical security vulnerability, analogous to leaving a high-value asset unsecured in a hostile environment. The inherent risks stem from RDP’s widespread deployment, weak default configurations, and its status as a prime target for automated exploitation. Mitigating these risks requires a layered defense strategy that disrupts the causal chain of exposure → exploitation → impact. Below, we outline evidence-based strategies grounded in real-world attack mechanics and physical system consequences.1. Secure RDP Behind a VPN: Cryptographic Isolation
Deploying a Virtual Private Network (VPN) as an intermediary layer introduces cryptographic isolation between the internet and the RDP endpoint. Solutions such as WireGuard or OpenVPN enforce mutual authentication and encrypt all traffic, forcing attackers to compromise both the VPN and RDP layers. Mechanistically, this disrupts brute-force and credential-stuffing attacks by requiring valid VPN credentials before RDP access is attempted. Without VPN access, attackers cannot reach Port 3389, effectively neutralizing pre-authentication vulnerabilities. Physical analogy: This is comparable to requiring a multi-factor access card to enter a secure facility, deterring unauthorized entry at the perimeter.2. Enforce Granular Firewall Rules: Attack Surface Minimization
Misconfigured firewalls that permit unrestricted access to Port 3389 create a critical attack surface, enabling tools like Mimikatz to flood the system with connection requests, leading to resource exhaustion and potential denial-of-service. To mitigate this, implement firewall rules that restrict RDP access to specific, trusted IP ranges or employ dynamic whitelisting based on behavioral heuristics. Mechanistically, this reduces the attack surface by preventing unauthenticated traffic from reaching the RDP service, thereby blocking exploitation vectors such as BlueKeep (CVE-2019-0708), which relies on unfiltered access to execute kernel-level memory corruption.3. Deploy an RD Gateway: Hardened Intermediation
A Remote Desktop Gateway (RD Gateway) acts as a hardened intermediary, encapsulating RDP traffic within an encrypted tunnel and enforcing authentication at the gateway layer. This breaks the direct exposure of Port 3389 to the internet, requiring attackers to first compromise the gateway’s authentication mechanisms. Mechanistically, this prevents pre-authentication attacks by ensuring that only authenticated users can reach the RDP endpoint. Physical analogy: This is akin to routing all access requests through a guarded checkpoint before granting entry to a secure zone.4. Enable Network Level Authentication (NLA): Pre-Session Validation
Network Level Authentication (NLA) mandates user authentication before establishing an RDP session, preventing attackers from exploiting pre-authentication vulnerabilities such as user enumeration or credential dumping. Mechanistically, NLA shifts the authentication process to the client side, reducing the server’s exposure to unauthenticated requests. This disrupts the exposure → exploitation chain by blocking access to the RDP stack until valid credentials are verified, effectively neutralizing attacks like BlueKeep that target unauthenticated sessions.5. Monitor and Patch: Proactive Vulnerability Management
Unpatched systems remain vulnerable to known exploits such as BlueKeep, which enables arbitrary code execution by overwriting kernel memory. This can lead to catastrophic physical consequences, including uncontrolled thermal expansion in critical components (e.g., CPU delidding or spindle motor failure in industrial systems). Proactive patching and continuous monitoring using tools like Shodan detect exposed RDP instances before attackers do, enabling timely remediation. Physical analogy: This is equivalent to replacing a compromised structural component before it fails under operational stress.Edge-Case Analysis: Failure Modes and Consequences
Despite robust mitigations, edge cases such as misconfigured VPNs or zero-day vulnerabilities in RD Gateways can lead to mitigation bypass → exposure → exploitation. For example, a zero-day exploit in an RD Gateway could grant kernel-level access, enabling memory corruption and system compromise. Physical consequences include thermal runaway in server CPUs, leading to permanent hardware damage or operational failure in interconnected systems. Such scenarios underscore the necessity of continuous monitoring and multi-layered defenses.Key Takeaway
Securing RDP requires a multi-layered approach that systematically disrupts the causal pathways of exposure and exploitation. VPNs, granular firewalls, RD Gateways, and NLA collectively act as mechanical barriers, each addressing specific failure modes. Neglecting these measures not only risks data breaches but also poses tangible threats to physical infrastructure. In cybersecurity, the weakest link is not merely metaphorical—it is a deterministic failure point with predictable consequences. Vigilance and proactive defense are non-negotiable.#rdp #security #misconfiguration #ransomware #software #coding #development #engineering #inclusive #community
Securing Remote Desktop Protocol: Mitigating Risks of Exposing RDP on Port 3389 to the Internet -
Turkish court orders access block of 13 news reports on minister’s assets, investment fund scandal
A Turkish court ordered access blocked to 13 news reports concerning the property holdings of Justice Minister Akın…
#EuropeSays #Turkiye #Türkiye #accessbans #AKParty #akıngürlek #AKP #Article8/A #democracy #Erdogan #freedomofexpression #humanrights #Internetcensorship #Justice #law #mediacensorship #MLSA #oppression #özgürözel #pressfreedom #ruleoflaw #Turkey #Turkish
https://www.europesays.com/turkiye/62747/ -
秋華賞
◎3マスターソアラ
○8モンローウォーク
▲14サムシングスイート
☆13ドリームコア