884 karma · joined June 4, 2019
erik@100toolkit.com
https://www.linkedin.com/in/erikmarkuskannike/
loads a real goldsrc .bsp map file (the same format half-life and cs 1.6 used), parses it in javascript, rebuilds the geometry for webgl with three.js, and runs a from-scratch reimplementation of valve's player movement so the surf feels right. multiplayer is peer to peer over webrtc with no game server.
it uses trystero, which does webrtc peer to peer and uses public relays only to introduce peers to each other, no game server in the middle. everyone in the same room name shares a session, broadcasts their position about 20 times a second, and you see each other surf.
On January 11th, Google and Shopify announced the Universal Commerce Protocol (ucp.dev). It's an open standard that lets any application query products across e-commerce platforms without needing APIs, integrations, or middlemen. AskUCP is one of the first applications built on it.
Right now, if you want to buy something online, you have to know which store sells it. You go to Amazon, or you go to a Shopify store, or you go to Etsy. Each one has its own search, its own interface, its own checkout. The experience is fragmented because the infrastructure is siloed.
UCP changes this at the protocol level. If products are described in a standard format, any application can discover them. You don't need permission from each platform. You don't need to build integrations. Anybody or any AI agent just querys the protocol.
AskUCP is designed to be a single pane of glass into online commerce. You search once, and you see products from across the ecosystem. Currently, that means the entire Shopify catalog. As more platforms adopt UCP, their products become explorable too. Eventually, it should be everything.
This is a proof of concept. It's early, and there are rough edges. Let me know what you think, refinements, ideas etc etc.
If you've ever tried to accept M-Pesa payments in East Africa, you know the pain: XML callbacks, rotating OAuth tokens, undocumented error codes, etc.
M-Pesa processes over $300B annually. It's how 50+ million people in Kenya pay for everything from groceries to rent. But integrating it into your app? That's a different story. Most developers spend weeks on what should take hours.
Micropay is essentially what Stripe did for credit cards, but for mobile money.
I'm currently Chief Strategy Officer at a defence-tech startup. Doing some small angel tickets as well :)
I also wrote a longer technical post on the maths behind it: https://medium.com/p/292c755a6ceb.
Happy to answer any questions about the tech stack or the simulation logic. The campaign mode has some interesting scenarios if you want to give it a try.
Issue ID: MO941162 Affected services: Exchange Online, Microsoft 365 suite, Microsoft Teams Status: Service degradation Issue type: Incident Start time: Nov 25, 2024, 4:54 AM GMT+2
User impact Users may be unable to access their Exchange Online mailboxes or their calendar functionality in Microsoft Teams.
More info The affected scenarios are as follows:
Users may be unable to access Exchange Online using the following impacted connection methods: - Outlook on the web - Outlook desktop client - Representational State Transfer (REST) - Exchange ActiveSync (EAS)
Users may also be unable to access or modify their calendar in Microsoft Teams. This would include loading calendar, viewing meetings, creating/updating meetings and joining meetings.
Scope of impact Some users may intermittently be affected by this issue when attempting to access their mailboxes using any connection method in Exchange Online or attempting to use their calendar in Microsoft Teams.
Preliminary root cause A portion of infrastructure which supports mailbox and calendar functionality isn't operating as expected, resulting in impact.
Current status Nov 25, 2024, 10:54 AM GMT+2 While we’re continuing the restarts to improve service availability, we’re thoroughly analyzing recent changes and the specific failure path to determine the next steps required to resolve the issue. Next update by: Monday, November 25, 2024 at 1:00 PM GMT+2
History of updates Nov 25, 2024, 10:18 AM GMT+2 Nov 25, 2024, 9:21 AM GMT+2 Our ongoing service monitoring has determined that the issue is not limited to users in Asia Pacific, and instead that all users worldwide could be intermittently impacted. As such, we're expanding our restart efforts to ensure the issue is resolved for all users. Nov 25, 2024, 7:46 AM GMT+2 We're continuing to work to restart the small subset of machines which have previously failed to restart. We're also continuing to add additional capacity to the affected environment to mitigate impact as quickly as possible. At this time, we expect the majority of users will experience relief from impact as we work to address the remaining issues. Nov 25, 2024, 6:56 AM GMT+2 We've identified a small subset of machines which are failing to restart, resulting in persisting impact. We're further investigating what is causing the restarts to fail to determine our next steps. Nov 25, 2024, 6:18 AM GMT+2 Nov 25, 2024, 5:50 AM GMT+2 We've determined via our internal telemetry that the impact to Microsoft Teams calendars has self-recovered. To fully resolve the issue, we initiated restarts on affected infrastructure and are monitoring further to determine whether additional steps are required. We're also continuing our investigation into the root cause of this issue. Nov 25, 2024, 5:29 AM GMT+2 Nov 25, 2024, 5:00 AM GMT+2 Our automated systems alerted us to an issue in which some users may be intermittently unable to access their mailboxes in Exchange Online using any connection method or their calendar functionality in Microsoft Teams. We're analyzing a portion of Exchange Online infrastructure responsible for accessing mailboxes to understand the root cause of the issue and determine our next troubleshooting steps.
On another note it is easy to shame the CIA for making such a basic mistake as using subsequent IP numbers/same file layouts on sites. Of course they should be, but funnily enough mistakes such as these happen in every intelligence service. As example would be the Russian military intelligence (GRU/GU) who have for years sent agents abroad with fake/cleaned Russian passports. Only problem being of course that the passport numbers were sequential and as in the case of the CIA websites, if you identified one agent and his passport, you could look up the next ones in line on databases and identify all the other active agents as well.
Reference for GRU passports: https://www.voanews.com/a/russia-gru-operatives-unmasked/460...
n world of technology, where the problem is no longer the lack of information, but rather the abundance of it, such work is more important than ever.