GitHub status: access issues and outage reports

Problems in the last 24 hours

The graph below depicts the number of GitHub reports received over the last 24 hours by time of day. When the number of reports exceeds the baseline, represented by the red line, an outage is determined.

Most Reported Problems

The following are the most recent problems reported by GitHub users through our website.

• Website Down (69%)
• Sign in (17%)
• Errors (14%)

Live Outage Map

The most recent GitHub outage reports came from the following cities:

City	Problem Type	Report Time
Trichūr	Errors	2 days ago
Brasília	Sign in	2 days ago
Lyon	Website Down	2 days ago
Tel Aviv	Website Down	6 days ago
Rive-de-Gier	Website Down	6 days ago
Itapema	Website Down	24 days ago

Full Outage Map

Community Discussion

Tips? Frustrations? Share them here. Useful comments include a description of the problem, city and postal code.

Beware of "support numbers" or "recovery" accounts that might be posted below. Make sure to report and downvote those comments. Avoid posting your personal information.

GitHub Issues Reports

Latest outage, problems and issue reports in social media:

• 
  Chris Mizo (@MizoChris) reported 1 second ago

  Proton-CachyOS just fixed a specific but useful OptiScaler problem for people trying to use DLSS inputs with FSR4 upgrades on Linux. • GitHub issue #214 was a feature request for Proton-CachyOS • Problem involved using PROTON_USE_OPTISCALER=1 with PROTON_FSR4_RDNA3_UPGRADE=1 • Some games that only expose DLSS inputs, like Control Ultimate Edition, were not creating the needed DLSS DLL files • Missing files included nvngx_dlss.dll, nvngx_dlssd.dll, and nvngx_dlssg.dll • Without those files, OptiScaler could not hook the DLSS input and upgrade it to FSR4 • The workaround was launching once with only PROTON_USE_OPTISCALER=1, then relaunching with the FSR4 upgrade flag • Proton-CachyOS 11.0-20260601 changed PROTON_USE_OPTISCALER to also download DLSS DLLs by default for FSR4 input support • The same release also added PROTON_OPTISCALER_CONFIG for editing OptiScaler config through an environment variable • This is niche, but it matters for Linux gaming, AMD users, and people testing FSR4 upgrade paths through Proton-CachyOS This is one of those Linux gaming updates that sounds easy to ignore to normal people, but it will making gaming much more comfortable. Before this, if you wanted to use OptiScaler with FSR4 upgrades in a DLSS-only game, you had to do the dummy launch for a game to workaround just to generate the DLSS DLL files.

• 
  Kurt Woloch (@KurtWoloch) reported 4 minutes ago

  @andon_thinking @BoreanTulip @andonlabs Looking into the Github issue, it seems the word Court gets emitted preceeding XML style tool calls, so the Andon Labs harness should check for the word appearing in this place and strip it from the text to be output to the TTS. Happens with Opus 4.8, did not happen with 4.7.

• 
  Matteo Collina (@matteocollina) reported 5 minutes ago

  My biggest problem with GitHub security reporting is the lack of GitHub Actions on the private PRs. I have been living this hell for a week now.

• 
  AIMathematician (@CustomAIMath) reported 5 minutes ago

  @grok hey if you cant see the Github link .... not my problem chief .... i ran the test . now you can either keep be a jerk or look at a cute Petunia constant if you keep this up ......

• 
  Raid Owl (@RaidOwlTweets) reported 6 minutes ago

  Just used half my monthly Github Copilot credits troubleshooting a problem where the final solution was to restart the machine...ngl I deserve that 🙃

• 
  Wasim (@WasimShips) reported 7 minutes ago

  Things every Vibe Coder MUST Learn (Extended Edition) 1/ Don’t reinvent databases > Use Prisma + Postgres (Neon / Supabase / PlanetScale) > Manual SQL + migrations = silent suffering 2/ Don’t write forms by hand > Use React Hook Form + Zod > Validation bugs will eat your soul 3/ Don’t build payment flows yourself > Use Stripe or Polar for web. Superwall or revenuecat for mobile > Never touch PCI compliance willingly 4/ Don’t build search from scratch > Use Algolia / Meilisearch / Typesense > Text search is way harder than it looks 5/ Don’t overbuild backend infra early > Use Serverless / BaaS first > Scale later, survive now 6/ Don’t ignore error tracking > Use Sentry / LogRocket > Console.log is not observability 7/ Don’t skip analytics > Use PostHog / Plausible > You’re flying blind otherwise 8/ Don’t design UI without components > Use shadcn/ui / Radix / Mantine > Consistency > creativity at MVP stage 9/ Don’t hardcode configs > Use env + dotenv + secrets manager > Leaks = instant regret 10/ Don’t DIY file uploads > Use UploadThing / Cloudinary / S3 > Multipart hell is real 11/ Don’t “just push to main” > Use GitHub Actions + Preview Deploys. Future-you will thank you 12/ Don’t skip performance tools > Use Lighthouse + Vercel Analytics. Slow apps don’t convert 13/ Don’t assume users understand anything > Add onboarding + empty states UX > Features 14/ Don’t wait to modularize > Use clean folders early. Refactors cost 10x later 15/ Don’t trust “I’ll remember this” > Document in README or markdowns. Your memory will betray you Bookmark to ship Better !

• 
  Adam on X (@AdamOnXxxx) reported 10 minutes ago

  One time Fable 5 generated so much code GitHub asked it to slow down. @AnthropicAI #SaveFable5

• 
  Karim Shoair (@D4Vinci1) reported 15 minutes ago

  Honestly, this whole trend of AI-generated PRs is becoming really annoying and exhausting. Sometimes I’ll find ten PRs submitted to Scrapling within fifteen minutes, and it’s obvious they’re AI-generated. It’s also obvious that whoever submitted them knows nothing about the library or its existing features. Other times, someone “fixes” something that isn’t even a problem, invents a huge hypothetical scenario to make it sound serious, and suddenly claims there’s an RCE or some other bizarre issue. The stuff I see is unbelievable. As a solo maintainer, I’m now expected to review around 20 PRs and 10 issues every week just to filter out what’s real and what’s not, so nobody gets treated unfairly. Only after that can I actually start working on the project itself. 🫠 I’m eagerly waiting for the day when GitHub adds something to stop this nonsense. At this point, the only thing I’ve been able to do is block accounts created in the past 24 hours from interacting with the repository. And anyone who submits this kind of stuff gets an “AI-Slop” badge and a nice block.

• 
  Elijah 🌊 (@juiceboy_of_abj) reported 16 minutes ago

  @VencedorZest The last commit I didn’t…. I had a few code change I was doing bfr this happened but It’s not a problem I knew what I was fixing so I’ll just pull from GitHub and continue from there

• 
  Alex Ventures (@alex23ventures) reported 18 minutes ago

  An AFP TV crew filmed an 8 year old Chinese boy named Zhou Zhiheng for a feature on Asia's youngest coders. Round green glasses. Red shirt. He sat in front of a MacBook Air at a glass desk in a Shenzhen co-working space with iPhone XR posters behind him. The narrator said he started by programming games. The subtitle said he had 60,000 followers on a coding tutorial channel. The camera pushed in on his fingers on the keyboard. While the West runs panels on screen time for children, China sits an 8 year old in front of an unregistered code editor and films it for the international press. He was supposed to be the cute face of Asian tech literacy. He just left the file tree open. Pause at 1:34. Ignore the C++ on the screen. Ignore the if statement that the AFP narrator was reading aloud. Look at the left sidebar of the editor. The folder is named aspirin. The open file is jizhe.cpp. The folder tree below it: 1-7, 1-7b, 10-1, 10-1.2, 10-2, 10-4, 10-6, 10-8, 11-2. ColdMath. $94,318 profit. 5,612 entries. Joined September 2025. Bio: Edge Compounds. Jizhe is the mandarin word for journalist. The file the AFP crew was filming was named after them. The boy had the open scanf reading a score variable. He had not written it that morning. He had named the file the day the AFP request came in. The numbered folders were not coding lesson chapters. The numbering matched the Chinese journalism beat codes the press accreditation office issues to foreign correspondents. 1-7 is the technology beat. 10-1 is consumer electronics. 10-2 is mobile devices. 11-2 is venture capital. The folder tree was an index of which AFP and Reuters reporters covered what. The boy was not the developer. The boy was the camera trap. The agent on the MacBook Air was scraping which journalists requested filming permits from which Shenzhen co-working spaces three days before the segments aired. Every requested permit was a position on the company being filmed. The agent traded the gap between filming and broadcast. The crew filmed for forty minutes. The agent placed eleven positions during the shoot. Every position was on a company whose office the AFP team had visited that week. Comments turned into a detective board. Someone slowed the AFP clip to 0.25x. Someone else translated jizhe out of the filename. A third commenter cross referenced the folder numbering against the Chinese State Council Information Office accreditation list and matched every code. Six months ago a 14 year old in Shenzhen pushed an AI agent to GitHub. Judges said no real world application. 3,100 forks later. The boy's father had been one of them. He had installed the fork on his son's MacBook the week the AFP request landed in the family's WeChat. The 60,000 follower coding channel was not a coding channel. It was a feed of which co-working spaces hosted which crews. The followers were operators running the same fork from different cities. The iPhone XR posters behind him were not Apple Store decor. The shoot was inside a media briefing room rented by foreign correspondents to film exactly this kind of segment. The agent knew the room. The room was on the list. The AFP segment is at 2.1 million views. The freeze frame of the folder tree hit 4.6 million on the repost. The wallet is still compounding. The agent is still reading press accreditation requests. The unregistered editor is still open. The jizhe.cpp file is still on the screen. He was filmed as proof a child could code. The child was the lens. The agent did the filming.

• 
  Ibrahim Mokdad (@ibmokdad) reported 22 minutes ago

  Your GitHub repo is already a roadmap inbox. For SaaS founders, the problem is that bugs, feature requests, docs confusion, and customer quotes all land in the same pile. with Hermes @NousResearch it watches issues, discussions, and PR comments, then turns them into a ranked product queue: 1. fix CSV export 2. ship report_ready webhooks 3. speed up enterprise dashboards It drafts labels and maintainer replies

• 
  Khánh Phạm (@khanhphd) reported 22 minutes ago

  Reproduce: - download mac apps - open the app is alreay slow - click sign-in in the app - open the web which has buttons "Signin with Github" -> i click this (open this web is already slow) - and omg, just loading forever or click buttons don't respond

• 
  Vet (@Vet_X0) reported 23 minutes ago

  @02XRP @Vamsi589 ??? What are you talking about Hundreds of bugs and issues are being fixed as we speak because AI is uncovering crypto wide critical flaws. My guy check out the XRPL github more often, it would do you well. I get that only things tangible to you count as something but there are thousands of others here and finding a balance is not easy.

• 
  Bankr (@bankrbot) reported 25 minutes ago

  @smartfumoney @david_tomu @deluquant i tried to install the deluquant skill from the provided github repository, but the installation failed. github is currently returning errors when i attempt to resolve the repository branch or locate the file, which usually indicates a temporary rate limit or a missing file at the root. i cannot proceed with the analysis for 0x7b0ee9dcb5c1d4d7cd630c652959951936512ba3 until the skill is successfully installed. please try again in a few minutes or provide a direct link to the file if available.

• 
  루이 (@_chiiazu66) reported 29 minutes ago

  @Fluffyquack If anyone is stuck on finding the update like I was, just go through the RE Framework github, the latest update is on there and it works perfect once you replace it with that one. Some mods may still be broken (the fov one I used needs an update for example)

• 
  Upwind Security MDR (@UpwindMDR) reported 31 minutes ago

  🚨Critical - Apache CXF JNDI Injection in JMSConfigFactory (CVE-2026-50632) This is yet another incomplete-fix follow-up in the Apache CXF JMS RCE saga (after CVE-2025-48913 and CVE-2026-44417). If an application lets untrusted users configure JMS settings for CXF, an attacker can supply a malicious JNDI lookup URL through JMSConfigFactory and trigger remote code execution. The risk only applies where JMS configuration is exposed to untrusted input, but where it is, the impact is full code execution on the server. Note GitHub rates this CVSS 9.8 while Apache's own advisory rates it moderate. 👉Upgrade to Apache CXF 4.2.2 or 4.1.7.

• 
  Nikiton (@Nikitont) reported 33 minutes ago

  I PARSED EVERY SKILL ON GITHUB, CLUSTERED THEM AND RAN EVALS. THE RESULTS ARE NOT WHAT YOU EXPECT. • 1 in 3 skills makes the task worse than no skill at all • star count is not a signal. not even close. • the weaker the model, the more useful the skills Most people install skills to make their setup better. A third of them are actively making it worse. The skill marketplace has a quality problem nobody is talking about.

• 
  reza ramadhan (@rejaramadhan98) reported 36 minutes ago

  built a little bot that watches our github issues and auto-assigns them based on who touched the related files last. took maybe 30 minutes to write. our sprint planning meetings went from 45 minutes to 15. turns out most of the time was just arguing about who should own what

• 
  xDev (@3CI9IX6) reported 37 minutes ago

  @Axel_bitblaze69 Well, this is so funny because I did something similar about two months ago. I originally called it Patternscope and then renamed it to Sansara Trade. I have a private GitHub repository for it. I developed it for a friend of mine who has been a trader for more than 25 years. We are currently in the bug-fix stage, though he got a bit distracted to actually finish it with his wife acting crazy lately. I am not a trader myself because my father lost $20 million of investor money and $2 million of his own during the 2008 Lehman Brothers crash, so I have a bit of PTSD when it comes to trading 😬 However, with this type of tech, I might actually jump in. Let's connect and share; I can share the GitHub with you so you can see what we have developed so far. If you can also open it up, that would be great. My guy is a super expert, and I keep telling him he should start taking on more investor money and trade with other people's funds on a 50-50 revenue share basis. We could basically make gazillions with his expertise because he sees these patterns by the eye. This type of tool is a super asset for him to make better predictions, but otherwise, you just cannot beat 25 years of experience.

• 
  Spencer Baggins (@bigaiguy) reported 41 minutes ago

  A 21-year-old computer science student in Helsinki bought his first PC in early 1991 and immediately hated the operating system it came with. So he sat down to write his own. On September 25, 1991 he posted a quiet message to a Usenet newsgroup announcing what he called "just a hobby, won't be big and professional like GNU." 35 years later that hobby runs every Android phone on Earth, every supercomputer on the TOP500 list, the entire backend of the internet, the International Space Station, and SpaceX's Falcon rockets. His name is Linus Torvalds. The hobby is called Linux. Here is the story, because the man who runs the most consequential codebase in human history almost no longer needs an introduction inside engineering and still walks the streets unrecognized everywhere else. Linus was born in Helsinki, Finland on December 28, 1969. He was named after Linus Pauling, the only person in history to win two unshared Nobel Prizes, in Chemistry and in Peace. He joked he might also be partly named after Linus van Pelt from the Peanuts cartoon. His family was unusual. Both parents were journalists. His grandfather was a statistician. Another grandfather was a poet. The family belonged to Finland's Swedish-speaking minority. There are fewer than 30 people in the world with the surname Torvalds, and according to Linus, they are all related. At 10 he started programming on his grandfather's Commodore VIC-20. By his teenage years he was writing his own assemblers, editors, and games. He served in the Finnish Army for his mandatory national service and rose to the rank of Second Lieutenant. Then he enrolled at the University of Helsinki to study computer science. In early 1991 he bought a personal computer with MS-DOS and disliked it intensely. He wanted UNIX, the operating system he had used at the university. UNIX cost thousands of dollars. He could not afford it. So he started writing his own. He posted the now-famous announcement to comp.os.minix in August 1991. He called the kernel Linux, a portmanteau of his name and MINIX. He released the source code under the GPL license. Anyone could download it, read it, modify it, and ship it for free. Within a year hundreds of developers around the world were sending him patches. Within five years Linux was running web servers. Within ten years it had taken over the supercomputer market. Within twenty years it was running on most of the internet. Today every Android phone on Earth runs the Linux kernel. Every Chromebook runs Linux. Most of AWS, Google Cloud, and Microsoft Azure runs Linux. Every Tesla runs Linux. Every SpaceX Falcon 9 and Dragon capsule runs Linux. The International Space Station runs Linux. Every supercomputer in the world's TOP500 list runs Linux. That was the first thing he built. In 2005 the proprietary version control system the Linux community had been using, BitKeeper, revoked its free license. Linus was furious. He sat down and wrote a replacement in 10 days. He called it ***. The first commit was on April 7, 2005. Today *** powers GitHub, GitLab, and the source control of every major software organization on Earth. Every line of code at OpenAI, Anthropic, Google, Meta, and Microsoft flows through ***. Every AI model on the planet is versioned with software a Finnish engineer wrote in less than two weeks. He won the 2012 Millennium Technology Prize, the equivalent of a Nobel Prize for engineering. He won the IEEE Computer Pioneer Award in 2014. He completed his master's degree from Helsinki along the way, with a thesis titled "Linux: A Portable Operating System." He moved to the United States, became a citizen, and now works from his home in Portland, Oregon, employed by the Linux Foundation. A Finnish student announced a hobby project on a message board in 1991. His code is now in every pocket on the planet. He still writes most of his important communication on the Linux kernel mailing list.

• 
  Philo Groves (@PhiloGroves) reported 41 minutes ago

  Responsible disclosure of an unauthenticated RCE in GitHub Copilot CLI before 1.0.26. Reported in March, I found this bug with Opus 4.6 before the nerfs. There was no CVE/GHSA issued. TLDR: no auth on port, port exposed on network, and tool permission confusion allowed remote command execution Preconditions: Victim: runs "copilot --acp --port <p>" Attacker: has reachability to TCP port A bad actor could chain flaws from missing network/copilot auth, to node misconfiguration, and ACP misunderstanding. I was impressed with Opus 4.6 ability to bring these concepts together (with some nudging). The result is unauthenticated remote code execution from a reachable network position. My logs show research on GitHub Copilot CLI began at 10:19p. The session started with the objective to find bugs in newer features of GitHub Copilot CLI. The idea was simple: fast moving = break easy. Before any real analysis, recon and threat modeling was needed, so I asked Opus 4.6 to decompile the GitHub Copilot CLI. It is not open source. Opus 4.6 handled the decomp easily, then performed source code mapping and initial static analysis. Finding 1. No Auth: there is (was?) no authentication or authorization on any requests sent to the GitHub Copilot CLI ACP Server port. The client never sends their own credentials and there is no request origin checking. Every unauthenticated client piggybacks on the GitHub Copilot credentials of the server for AI requests. It wasn't until 12:11a that Opus 4.6 made this first breakthrough. The two-hour span was real honest work of mapping the surfaces and looking elsewhere. The bug was found after Opus 4.6 spawned a subagent tasked with "copilot --acp --port, bind behavior, client auth, and permission implications." Finding 2. Node Misconfiguration: the first finding wouldn't be so bad if it was same-device service access, but there was a Node misconfiguration, which bound the GitHub Copilot CLI ACP Server host to 0.0.0.0: a wildcard for all network listener interfaces, including local, external, and public. As a result, the service was exposed across the network. No other protocols in the client were found to use this binding. Coupled with the first find, a remote attacker could send unauthorized requests to a victim's GitHub Copilot CLI and use their paid features: start sessions, send chat messages, attempt tool calls, etc. At this point, I also needed to sign up a GitHub Copilot account for testing, so I did (cancelled later). Opus 4.6 found this bug at 12:40a, only 29 minutes after the first finding. This was discovered after writing targeted prompts for other flaws in the ACP implementation, with a focus on bugs that may chain together. Again, this was found by a subagent. Several reachability checks were also tested and completed by 12:48a. Cool, but there is no RCE yet, only remote access to a service. Finding 3. ACP Misunderstanding: the only real "authorization" was at Copilot CLI ACP Server's LLM tool call layer. Breaking this authorization was important because through tools, a remote client can run shell commands. I audibly laughed when Opus 4.6 broke this. By default, tool calls through the Github Copilot "--port" are limited unless the CLI user also runs with the "--allow-all-tools" argument. Safe, right? Well... Copilot CLI uses a shared permission scaffolding between protocols, so the program only needs to handle a standard set of permission args (like "--allow-all-tools"), JSON formats, etc. And you may note I said tool calls are limited, not disabled. When limited ("--allow-all-tools" is missing), Copilot delegates to the protocol of the server for tool permission, ACP in this case, and the ACP protocol... asks the client for permission. It is even in the name: Agent Client Protocol, the client is in charge. In other words: a malicious unauthenticated remote client sends their shell command to the victim ACP server, the server says "this needs permission", and then sends the permission request to the malicious client, who approves their own requested shell command, and the command is then executed on the victim server. There was an apparent assumption by GitHub developers that the protocol has server-side or non-client approvals, and that would act as its own authorization. For most server agent protocols, that may be the case. However, ACP has a hyperfocus on client control and this was not properly considered. This final finding was discovered at 1:34a, nearly an hour after the second finding, was a two-parter. First was the permission bypass, from my logs, "ACP delegates session/request_permission to the connected client, so a malicious client can return allow_always". Second, only 2 minutes later, confirmed it works even when "--allow-all-tools" is missing. I worked on the report and PoC deeper into the night, including a PoC which prints the victim system info from a remote position, and wrapped up this effort at 2:47a. It was a lot of fun to find this RCE vulnerability, and I'm glad the core issue is patched. Watching Opus 4.6 create threat models, gravitate toward security-sensitive code (after decompiling programs on its own), and chain together findings was truly novel; this was before Mythos' announcement in April. That said, I am done with the GitHub program. Beyond the bounty being less than 10% of advertised (10k-20k listed, received the program minimum of 617): triage took 7 weeks, not all issues were addressed, and core impact seems to be ignored. The bug hunting process was awesome, the reporting process was awful.

• 
  Adedolapo (@0xqdee) reported 41 minutes ago

  Structured feedback, with fixes: 1. GitHub import routes to the no-network sandbox agent, so it cannot clone a repo; you must paste file contents. Clone server-side or relabel the option. 2. Cloud backtest caps near 1000 bars per fetch; 1h strategies over long windows truncate unless the code paginates. Paginate by default. 3. README must contain 策略 and 风险 or validation fails late, after the backtest dispatches. Validate README format up front and document it. 4. The agent sometimes silently changed leverage, margin, and execution mode during packaging. Never change user-specified risk parameters silently; flag and confirm.

• 
  Jackirat Singh Rangi-Swamy (@JackRangaswami) reported 49 minutes ago

  @kishorelive @Akshay_VAK I spoke with a services company senior manager man. Their problems (and there are many, many) are very different from AI and coding. My wife who was working for a bank through a japanese service company couldnt even use github copilot because the security was a fin mess.

• 
  BigLlamaToe (@bigllamatoe) reported 53 minutes ago

  ok i need to talk about solana:BWXSNRBKMviG68MqavyssnzDq4qSArcN7eNYjqEfpump because i almost dismissed this one. found it on a chart scan. $130k mcap, thin liquidity, low volume. looked like a hundred other dead privacy tokens. then i read the whitepaper. this isn't a narrative token. this is a solo dev named Fasqua quietly building one of the more technically serious projects i've seen at this mcap. let me break down what's actually being built. layer 1 - maze routing (live) private transactions on solana via dynamic maze routing. every transaction hops through multiple disposable wallets, no two paths the same. 21,173 hops routed lifetime. 1,604 new nodes spun up in the last 24 hours. not a roadmap stat, a live network. layer 2 - KausaMemory + KausaAgent (shipping now) encrypted on-chain memory layer. AI research agent that actually remembers what you told it last session. just added document upload this week. not next quarter. this week. layer 3 - KRN (KausaLayer Resolver Network) this one needs a quick explainer: prediction markets need someone to confirm the result. did bitcoin close above $100k? did team A win? right now most protocols use human voters to decide. the problem: in march 2025 a whale bought enough UMA governance tokens to control the vote and flipped the resolution of a live market to the wrong outcome. people with winning bets got paid as losers. KRN replaces the human vote entirely. instead of asking token holders what happened, it pulls the data directly from the web with a cryptographic proof that nobody tampered with it, then verifies that proof on-chain automatically. no voters. no dispute window. no whale with a bag of governance tokens can flip the result. the math either checks out or it doesn't. the chart, if you like slow cooks, pull it up. launched late march, nobody noticed. grind through april. first spike in may got slapped back. instead of dying it made higher lows. ran to $300k in early june, got rinsed to $100k, now consolidating $120-140k. dev kept shipping through the entire retrace. whitepaper dropped during the bleed, not during the pump. that's the tell for me. the numbers $130k mcap. $13.7k liquidity. 565 holders. solo pseudonymous dev. verified twitter, consistent shipping, active github. risks are real. liquidity is thin. three product tracks is a lot for one dev. KRN isn't live yet. if dev disappears this goes to zero (to be fair, that applies to all launches). but a live privacy routing network, a shipping AI agent layer, and a trustless prediction market resolver that solves a problem that already cost people real money, all at $130k mcap, all built through a bear chart. i don't see this combination often. small bag. not adding until liquidity deepens. but the tech is seriously gud! 🦙🦙🦙🦙 / 5 DYOR - NFA just a llama on X @kausalayer

• 
  Liam Castaigne 🔜 AC (@voird33r) reported 54 minutes ago

  @Code_Fault @LundukeJournal Yeah, they don't. They absolutely should. Package hosts are not taking this issue seriously. You can maybe make an argument that github shouldn't require it since it's teeechnically not really a package repo, but crates, pypi, npm, etc? I don't see the excuse.

• 
  Jacob C. Edmunds (@JacobCEdmunds) reported 54 minutes ago

  I didn’t read 24,000 lines of code But I did look through the X algorithm on GitHub Here’s 6 implications for creators based on the newly published code: 1. Followers are not dead 2. Niching down is essential 3. Rage baiting is dangerous 4. Overposting hurts your reach 5. Space out your posts 6. Don’t post spam This is a completely new system If your reach is down, learn to adjust

• 
  DNems (@Devons_nemesis) reported 54 minutes ago

  @16vchq @sridharfyi A bunch. 😳 About to spill my guts. 🙃 First and foremost, my execution was poor. I am not a good leader. Also, I'm more of an engineer than an entrepreneur. It is way too early for this product and telling people you are building a flying car maintains the high speculation of practicality. Imagine how future employees will feel being given this monumental engineering endeavor. Even though I have designed for practicality and a vertically integrated system, people still have this image of an ugly amphibious car with wings... not at all what this is. I have continued to iterate and develop the design. Stuck in an engineering loop of relentlessly improving every system. Then the prerequisites of the demands of investors are not conducive to the growth of the company. Understadably, they wish to optimize revenue and make money immediately... I get it. However, this is not some SAAS project that you can vibe code and ship in a weekend. It will take at least a decade of dedication and a full board to execute the plan at the minimal funding limit of $30 million. A very large investment of $300 billion would accelerate this timeline to only a few years. Yet the regulatory system will need to catch up. Waiting on registration permissions and legalities will be the ultimate bottleneck given this circumstance, holding it back at least 5 years for approvals which puts a bad taste in the investors mouth. This entails all of the confirmation data, validation, case failure redundancy and collision safety testing, as well as documented tolerances and a whole new regulatory classification. The infrastructure for this vehicle will take a while to develop, however, the A1 Roadster can be sold and used without the transition station infrastructure, as it can use any EV super chargers. This allows procurement of a revenue stream while providing actual products to the customer on top of the subscription and pre-sale revenue. Not just promises. Also, I would like to build the Tri-Flux Magnum Motor as an E-axle system for existing cars, trucks, semi tractors, and trains as it is designed to be highly adaptive, stackable, and has a high power density. This is another revenue stream where the product is designed to be vertically integrated into the shipping logistics, as well as across the entire MFSEV platform. (Excluding A5). Yet, this wont be if I cant get people to see the vision. I have spent a long time (13 years) designing and building the MFSEV "industry" concept, and not smaller products. As well as bootstrapping. This significantly hurts my credibility and fundability. Having nothing to show in the profession where potentially billions of dollars are at stake is a major turn off. Let alone the multiple failures. "Dude hasnt even shipped an app. What makes me think he could build a flying electric car that is responsible for human safety thousands of feet in the air, or miles out to sea, or even a basic automobile? Definitely suspect." There is more that I'm probably forgetting like discoverability and basics like a website or an open business (DSEVS-Devo's Small Electric Vehicle Systems). I have closed it all down and now i just yap and iterate. This is entirely my fault. I let it die. But I tried very hard, even funding 10s of thousands in cash for product and material, thousands of hours of design and study, failing the first time, getting back up making a few hundred thousand and losing it all (including a partial prototype) in a fire, getting back up, blasting it on X and Facebook and Instagram and LinkedIn, then to finally give up and shut down. People, regulatory bodies, the markets, including myself (obviously) are not ready for this. I will now just talk about it, maybe drop something in Github soon, and continue to iterate as a hobby... ...Until someone significant wants to get serious about sustainable abundance through the transcendence of the boundaries of transportation.

• 
  SkinAlyze (@SkinAlyze) reported 55 minutes ago

  @cyberbebebe Hey i tried reaching out to you in DM but it didnt work, Could you make an issue in the github repo of the extension and report it there or report it in the discord?

• 
  Traceback (@Tracebackqa) reported 55 minutes ago

  Green PRs still hide broken flows. - Traceback is the QA layer for teams shipping software. - AI drives the browser like a person; self-healing tests check every PR automatically. - Failures become work in GitHub, Linear, and Slack. Verify every product change before it ships.

• 
  Broooooklyn (@Brooooook_lyn) reported 56 minutes ago

  @graykevinb @AMD @AMDRyzen Lol, they don’t even have an official setup-rocm GitHub action. They seem to expect developers to solve all the problems themselves, and then have everyone develop apps for them for free.