Video yükleniyor...

Video Yüklenemedi

Ana Sayfaya Dön

Malaysia’s new SaveME 999 app: Reporting an emergency shouldn’t be this complicated. #saveme999 #ng999 #mers999 #saveme #999 #bomba #pdrm #hospital

63,789 görüntüleme • 9 ay önce •via X (Twitter)

0 Yorum

Yorum bulunmuyor

Orijinal gönderinin yorumları burada görünecek

Benzer Videolar

A Young Teen Girl Collapses Inside Easons, Blanchardstown Centre - One of Ireland’s Largest Shopping Centres - Convulsing and Foaming at the Mouth. Connolly Hospital, with One of Dublin’s Major Emergency Departments and Ambulance Fleets, Is Minutes Away. 999 Was Called Immediately. No Emergency Response Yet. No Visible First Aid Administered. Now 105 Minutes and Counting. This evening, at approximately 6.10pm, a young Irish girl collapsed in what staff described to me as a serious medical emergency on the upper floor of Eason’s two-level unit in Blanchardstown Centre. A 999 call was made. 98 minutes later, there was still no visible emergency medical response at the scene. Let that sink in. A child collapsed on the floor of a major shopping centre in Dublin 15. She was unconscious. Her parents were sitting beside her on the floor. Staff had closed the upper level of the store where the incident occurred. And people still tried to get in. Not to buy medicine. Not to get food. Not to deal with an emergency of their own. The upper level of this store sells stationery, envelopes, picture frames and similar retail items. The ground-floor bookshop remained open. This was not a question of essentials. This was not necessity. This was consumer selfishness stripped naked. The girl was only feet from the entrance. She was plainly visible. Yet people argued with staff that they should still be allowed in, as though a collapsed child on the floor was merely an obstruction between them and stationery. According to the manager, people did not ask how the girl was. They did not ask whether she was alive, conscious, breathing, safe, or being helped. They wanted what they had come to buy. That is not merely disappointing. It is obscene. I am deliberately not showing the girl, her face, her parents, or any identifying image of her in the attached video. This post is not about exploiting a child’s distress. It is about recording the disgrace of what happened around her. Connolly Hospital is only minutes away from this location. It is a large hospital with a major Emergency Department. In a normal vehicle, it is close. With blue lights, in an emergency, it should feel almost next door. And yet, 98 minutes after the emergency call, no visible emergency medical response had arrived. I do not know where exactly the failure occurred. I do not know whether the issue lies with dispatch, capacity, triage, staffing, ambulance availability, or some other breakdown in the system. But I know what I saw. A 13-year-old girl collapsed on a shop floor. Her parents sat beside her. Staff tried to protect the scene. Members of the public argued to get past her. And nearly an hour and forty minutes after a 999 call, the emergency response still had not visibly arrived. This is Ireland in 2026. A child can collapse in one of Dublin’s largest shopping centres, minutes from a major hospital, and the system can leave her on the floor long enough for strangers to become irritated that they cannot buy envelopes. It is now approaching two hours and still no emergency medical response. This is not normal. This is not acceptable. And someone needs to answer for it.

GP

54,027 görüntüleme • 2 ay önce

Watch the moment Michael Ormandy was arrested for the murder of Rebekah Campbell. 32-year-old Rebekah was fatally stabbed by Ormandy during an incident on Tuesday 15 April at around 10.30pm where she was attacked inside a flat at Knowsley Heights. Officers attended and gave first aid to Rebekah until paramedics arrived. She was taken to hospital but sadly died from her injuries. Today, Ormandy, 34, of Linacre Road, in Litherland, has been sentenced to life imprisonment with a minimum term of 24 years for the murder of Rebekah. Our thoughts continue to remain with Rebekah’s family and friends as they continue to grieve their tragic loss. We would urge anyone who may be a victim of domestic abuse, or know someone who might be, to please reach out for help to the police or a local support service. Domestic abuse comes in many forms. If you are suffering from physical, sexual, psychological or financial abuse, or are being threatened, intimidated or stalked by a current or previous partner or close family member, it’s likely you’re a victim of domestic abuse. If you are a victim or believe someone you know is a victim - you can contact us Merseyside Police Contact Centre, or call 999 if you are in immediate danger. If you ring 999 and are not in a safe position to speak to us then cough, or tap, the phone and press 55, when prompted. This will alert the operator that you need assistance and we will provide support. We have an ongoing Violence against Women and Girls (VAWG) campaign to put the voices of women and girls at the heart of our work to tackle VAWG. You can find out more about the campaign via our website. Video credit: NPAS Footage © West Yorkshire Combined Authority NPAS North West Region

Merseyside Police

28,265 görüntüleme • 10 ay önce

🔥 85,075,311,824 $SHIB Burned 80,022,668,294 $SHIB burned in a single transaction, followed by a 5,000,000,000 $SHIB burn and a couple smaller burns. Nearly $1M that went under the radar at the time. This wasn’t a community burn. This comes from an event that happened on June 18th, 2025. You may have heard this story. ZachXBT first flagged suspicious outflows tied to an address 0xf22cc3c5b24e3b40ba7a27b82ea0d4b6d3088bbd. Further reporting from Reuters and CoinDesk later confirmed the scale of the exploit. An Iranian crypto exchange, Nobitex, was reportedly hacked for $90M+. 0xffFFfFFffFFffFfFffFFfFfFfFFFFfFfFFFFDead was mentioned (a burn address on Ethereum) on those reports, but didn't see anyone going further to confirm that multiple tokens like $SHIB were actually burned. Somehow, it was missed. One of the burns being the 2nd biggest burn we had so far for $SHIB. Other assets were wiped as well: -255.6 billion $PEPE -12 thousand $CHAIN -262 ETH ...just to name some. As you may know, tracking $SHIB was mostly focused on known SHIB-related burn addresses. That’s why this was missed. We should’ve been tracking more addresses. So what changed? We built a new tracking platform that monitors 100+ addresses, including 29 official burn addresses in Ethereum, with 0xffFFfFFffFFffFfFffFFfFfFfFFFFfFfFFFFDead being one of them. The new application will be revealed within 3 weeks. A platform built to track burns at a much deeper level, across chains, tokens/nfts/coins. We already have over 1M tokens tracked. The new uses the platform's API and will be accessible to others. That’s how this was discovered, and is now accounted for. This one went under the radar. It shouldn’t have. It won’t happen again. ClayBro Matthew G Perry LuckSide Crypto

Shibburn

36,720 görüntüleme • 5 ay önce

Pylon's 𝗺𝗼𝘀𝘁 𝗵𝗮𝘁𝗲𝗱 𝗳𝗲𝗮𝘁𝘂𝗿𝗲 is our Analytics. That ends today. We've completely rebuilt our Analytics from scratch. Here's what we tried, what we screwed up, and what's coming. 𝗩𝗲𝗿𝘀𝗶𝗼𝗻 𝟭, The Basics (Nov 2023) Our first attempt at analytics was quite loved by customers. At the time our customers were mostly small startups with simple needs. We built an out-of-the-box set of dashboards that covered the common use cases of support analytics (SLA-tracking, CSAT, TTFR, TTR, basic filtering...). As we moved upmarket... 1/ Everyone was requesting custom metrics 2/ Queries were becoming inefficient and slow We needed an upgrade. 𝗩𝗲𝗿𝘀𝗶𝗼𝗻 𝟮, Advanced Reporting (June 2024) We knew custom reporting was going to be blackhole of work that long-term led to fully customer-customizable dashboards. We had four choices: 1/ Do nothing for now 2/ Do custom work per customer 3/ Build full custom reporting in-house 4/ Use an embeddable analytics vendor At the time Pylon was under 10 people total and we had no capacity to do the frontend work so we chose Option 4 (use a vendor). This was the first time we chose to not build a core feature like this in-house as we ultimately want full control of the end-user experience. We built out the new reporting with the chosen vendor over ~3 weeks. On the surface the new reporting looked really good (not visually, but in terms of functionality). You could add custom charts of any type, create custom formulas, label the Y and X axis, and effectively build most of what you would want. It was really great for demos. But in practice it was incredibly hard to use, lacked core capabilities (like the ability to filter off of dynamic custom fields), and visually looked not stylized to the rest of the product. We started to discover some of these issues during the implementation, but it still felt like there was more upside than downside so we released it. Feedback was not great but we hoped our vendor would fix changes quickly. Unfortunately they weren't fast enough and we lost confidence that they would be a good long-term solution. As a stop-gap we also built out a data warehouse integration so customers could export their data back to Snowflake or BigQuery to use with their own BI tools. Finally, a few months ago the vendor told us they were being acquired. That was the final straw. We needed to move off ASAP. 𝗩𝗲𝗿𝘀𝗶𝗼𝗻 𝟯, New Reporting (Today) Today's release is back to being built entirely in-house. It's been rolled out in beta to all customers with an option to flip back to old analytics until we plug some custom reporting gaps. This time we have the capacity to do it right between Wendy (prev product design at Amplitude), Matt, and Tom. We've managed to greatly improve: 1/ Desired filter options (custom field support) 2/ Performance 3/ Setup UX 4/ Style (looks native) Early feedback has been really positive so far and as we bring it out of beta we're thinking about how to make the best natively-offered reporting of any support platform. 𝗩𝗲𝗿𝘀𝗶𝗼𝗻 𝟰 (What's coming soon) To get to first-class reporting, we need to study not only our learnings, but also what the incumbents have screwed up as well. Funny enough, Zendesk's analytics have similar complaints to our v2, and for the exact same reason as we did: they integrated an external tool. In 2015 they bought a company called BIME Analytics which they became Zendesk Explore. The complaints they have to this day are similar to our v2: 1/ Steep learning curve 2/ Advanced, yet still not enough flexibility 3/ Random feature gaps 4/ Data accuracy and reliability concerns 5/ Performance issues 6/ Complicated UX v4 will follow three core principals: Offer a simple default setup. We want to continue being startup friendly and we'll feature gate custom reporting and data exports by tier in the product. Offer maximal configuration, with AI-assisted setup. As we go upmarket, customers will want to Explore (pun intended) data in every single direction. We need to allow them to do that. For those more complicated use cases we think AI will be the Ultimate (also pun intended) way to reduce setup friction. Build it all in-house. Although using a 3rd party embedded analytics provider didn't work for us, we don't think that is the case for everyone. It's just in customer support, reporting is REALLY important. They are probably some of the highest-complexity reporting of most SaaS vendors (maybe second to marketing products). So... we have to do it right. And since this is end-user facing, we have to own every detail of it. If you got this far, thank you for reading. See our new Analytics at

Marty Kausas

115,123 görüntüleme • 1 yıl önce

Manhattan, New York — An unidentified man deployed an incendiary device outside 26 Federal Plaza in Lower Manhattan on the morning of July 20, 2026, prompting a large emergency response and a federal investigation. The incident occurred at approximately 8:30 a.m. outside the Jacob K. Javits Federal Office Building, which houses the FBI's New York Field Office, the local U.S. Immigration and Customs Enforcement (ICE) office, an immigration court, and several other federal agencies. In a statement, the FBI said: “This morning an individual deployed an incendiary device outside of 26 Federal Plaza. The individual has been taken into custody and the FBI New York Joint Terrorism Task Force is investigating the incident.” According to law enforcement sources, the suspect pushed a cart displaying a sign that read “ICE off our streets.” Authorities said the cart contained fireworks and two long firearms that appeared to be airsoft or pellet guns. Investigators believe the suspect ignited the fireworks, possibly using a flammable liquid, creating flames and smoke near the building's entrance. Officials also reported that the suspect allegedly threatened pedestrians with the apparent firearms before being taken into custody by federal officers near Worth Street and Centre Street. The NYPD Bomb Squad responded to assist at the scene. FBI Director Kash Patel said the incident resulted in two minor injuries. The New York City Fire Department (FDNY) reported that one person was transported to a hospital with non-life-threatening injuries. Authorities said there were no serious injuries and no significant damage to the federal building. The FBI New York Joint Terrorism Task Force is leading the investigation. #police #cops #crime #policia #polizei #CrimeNews #FBI #DHS #ICE #NYC

Police Incidents

14,747 görüntüleme • 1 ay önce