When do you think we will get Starship flight 14?

When do you think we will get Starship flight 14?

Personally I think we will have a launch by the end of the first week of September - when do y’all think?


Progress according to NSF: [x] Booster 21 Proof Campaign

[x] Ship 41 Proof Campaign

[ ] Booster 21's Raptor 3 Engines Installed

[x] Ship 41's Raptor 3 Engines Installed

[ ] Booster 21 Static Fire Campaign

[ ] Ship 41 Static Fire Campaign

[ ] Confirmation from SpaceX

[ ] Booster 21 at Launch Site

[ ] Ship 41 at Launch Site

[ ] Vehicles Stacked

[ ] FAA Operations Advisory

[ ] COMPASS Airspace Advisory

[ ] Notice To Air Mission (NOTAM) for Launch

[ ] USCG Notice to Mariners (NOTMAR) for Launch

[ ] NGA Notice to Mariners (NOTMAR) for Launch

[ ] Notice To Air Mission (NOTAM) for Ship Splashdown

[ ] NGA Notice to Mariners (NOTMAR) for Ship Splashdown

[ ] Temporary Flight Restriction (TFR)

[ ] Road Closure for Launch

u/Time-Water-8428 — 1 day ago

Codeberg's ban on LLM-assisted code is the most out-of-touch FOSS take I've seen in years.

I’ve been backing Codeberg for a while now. I’ve donated, migrated a bunch of my repos over from GitHub, and constantly recommended it to people who wanted a non-profit, privacy-respecting Git forge.

So reading their recent blog post and seeing their vote to ban "vibe-coded" or heavy LLM projects in their Terms of Use legitimately pissed me off.

It is an absurd policy. It mixes up a basic infrastructure problem, uses completely dishonest statistics to justify gatekeeping, and ironically ends up pushing developers directly back into Microsoft’s arms.

  1. Banning tools instead of setting quotas makes zero sense

The practical argument Codeberg makes is that "ghost projects" created by AI are clogging their CI/CD runners, eating up disk space, and getting hammered by scrapers.

Fair enough, server administration is hard. But since when do you solve infrastructure abuse by banning developer tools instead of setting resource limits?

If people are abusing free runners or taking up too much disk space, you cap runner minutes per user and enforce strict storage quotas. That’s how GitHub and GitLab handled it. Low-effort, unmaintained junk repos have been getting pushed to open source since the SourceForge days. Trying to police how someone writes code instead of just setting hard limits on bandwidth and storage is administrative insanity. If a solo dev writes a clean, fully-tested Rust tool in an afternoon using Claude, why on earth does Codeberg care as long as it stays under their storage cap?

  1. The stats in their blog post are completely dishonest

They go on this massive rant about data center energy, SSD prices, and water usage in Frankfurt to frame AI code as an environmental crime. The logic falls apart the second you look at actual data.

They literally complain about enterprise SSD prices jumping from €700 to €3,700 and blame LLM projects on their site. No, enterprise NVMe prices didn't spike because some hobbyist used Copilot to write a bash script. They spiked because Big Tech hyperscalers like Microsoft, Meta, and Google are dropping over $150 Billion a year in hardware CapEx to build massive clusters.

Same story with their energy and water claims. According to the IEA, global data centers account for roughly 1% to 1.5% of global electricity. As for water? Data center cooling is a fraction of a percent of industrial water use—compared to something like US golf courses which consume 1.5 billion gallons of water every single day. Blaming open-source devs using AI assistants for Frankfurt's grid problems (in a country that shut down its own zero-carbon nuclear plants) is pure bad faith.

  1. Linus gets it.

The post assumes that any code written with an LLM is automatically unmaintainable slop. That just shows they haven't paid attention to how modern dev workflows actually look.

Frontier models like Claude 3.5 Sonnet hit over 80-90% accuracy on benchmarks like SWE-bench. People aren't just blindly pasting hallucinated code anymore. Developers use these tools to generate unit tests, write documentation, catch edge cases, and refactor legacy code way faster than they could alone. It raises the floor for solo maintainers.

Linus Torvalds called this out on LKML:

> "AI is a tool, just like other tools we use... But the solution is not to put your head in the sand and sing 'La La La, I can't hear you'... The solution is to make sure those LLM tools help maintainers instead of just causing them pain."

If the creator of the Linux kernel can understand that AI is just a tool that helps maintainers catch embarrassing bugs, why is Codeberg acting like using a coding assistant is a crime against open source?

This just pushes people back to GitHub

FOSS is supposed to be about democratising software and empowering individuals. LLMs give solo devs and non-native English speakers the leverage to build ambitious projects that used to require a whole team.

By declaring that AI-assisted workflows are unwanted "pollution" on Codeberg, they aren't stopping people from using AI. They are just telling those developers: "Go back to GitHub."

How does driving talented builders right back into Microsoft's proprietary ecosystem protect the open-source commons? It does the exact opposite. It enforces an ideological purity test that guarantees Codeberg stays a niche side project while GitHub keeps its monopoly.

Codeberg needs to protect its servers with proper quotas, rate limits, and bot mitigation. This tool-banning nonsense is a massive mistake.

reddit.com
u/Time-Water-8428 — 22 days ago

Codeberg's ban on LLM-assisted code is the most out-of-touch FOSS take I've seen in years.

I’ve been backing Codeberg for a while now. I’ve donated, migrated a bunch of my repos over from GitHub, and constantly recommended it to people who wanted a non-profit, privacy-respecting Git forge.

So reading their recent blog post and seeing their vote to ban "vibe-coded" or heavy LLM projects in their Terms of Use legitimately pissed me off.

It is an absurd policy. It mixes up a basic infrastructure problem, uses completely dishonest statistics to justify gatekeeping, and ironically ends up pushing developers directly back into Microsoft’s arms.

  1. Banning tools instead of setting quotas makes zero sense

The practical argument Codeberg makes is that "ghost projects" created by AI are clogging their CI/CD runners, eating up disk space, and getting hammered by scrapers.

Fair enough, server administration is hard. But since when do you solve infrastructure abuse by banning developer tools instead of setting resource limits?

If people are abusing free runners or taking up too much disk space, you cap runner minutes per user and enforce strict storage quotas. That’s how GitHub and GitLab handled it. Low-effort, unmaintained junk repos have been getting pushed to open source since the SourceForge days. Trying to police how someone writes code instead of just setting hard limits on bandwidth and storage is administrative insanity. If a solo dev writes a clean, fully-tested Rust tool in an afternoon using Claude, why on earth does Codeberg care as long as it stays under their storage cap?

  1. The stats in their blog post are completely dishonest

They go on this massive rant about data center energy, SSD prices, and water usage in Frankfurt to frame AI code as an environmental crime. The logic falls apart the second you look at actual data.

They literally complain about enterprise SSD prices jumping from €700 to €3,700 and blame LLM projects on their site. No, enterprise NVMe prices didn't spike because some hobbyist used Copilot to write a bash script. They spiked because Big Tech hyperscalers like Microsoft, Meta, and Google are dropping over $150 Billion a year in hardware CapEx to build massive clusters.

Same story with their energy and water claims. According to the IEA, global data centers account for roughly 1% to 1.5% of global electricity. As for water? Data center cooling is a fraction of a percent of industrial water use—compared to something like US golf courses which consume 1.5 billion gallons of water every single day. Blaming open-source devs using AI assistants for Frankfurt's grid problems (in a country that shut down its own zero-carbon nuclear plants) is pure bad faith.

  1. Linus gets it.

The post assumes that any code written with an LLM is automatically unmaintainable slop. That just shows they haven't paid attention to how modern dev workflows actually look.

Frontier models like Claude 3.5 Sonnet hit over 80-90% accuracy on benchmarks like SWE-bench. People aren't just blindly pasting hallucinated code anymore. Developers use these tools to generate unit tests, write documentation, catch edge cases, and refactor legacy code way faster than they could alone. It raises the floor for solo maintainers.

Linus Torvalds called this out on LKML:

> "AI is a tool, just like other tools we use... But the solution is not to put your head in the sand and sing 'La La La, I can't hear you'... The solution is to make sure those LLM tools help maintainers instead of just causing them pain."

If the creator of the Linux kernel can understand that AI is just a tool that helps maintainers catch embarrassing bugs, why is Codeberg acting like using a coding assistant is a crime against open source?

This just pushes people back to GitHub

FOSS is supposed to be about democratising software and empowering individuals. LLMs give solo devs and non-native English speakers the leverage to build ambitious projects that used to require a whole team.

By declaring that AI-assisted workflows are unwanted "pollution" on Codeberg, they aren't stopping people from using AI. They are just telling those developers: "Go back to GitHub."

How does driving talented builders right back into Microsoft's proprietary ecosystem protect the open-source commons? It does the exact opposite. It enforces an ideological purity test that guarantees Codeberg stays a niche side project while GitHub keeps its monopoly.

Codeberg needs to protect its servers with proper quotas, rate limits, and bot mitigation. This tool-banning nonsense is a massive mistake.

reddit.com
u/Time-Water-8428 — 23 days ago
▲ 0 r/foss+1 crossposts

Codeberg's ban on LLM-assisted code is the most out-of-touch FOSS take I've seen in years.

I’ve been backing Codeberg for a while now. I’ve donated, migrated a bunch of my repos over from GitHub, and constantly recommended it to people who wanted a non-profit, privacy-respecting Git forge.

So reading their recent blog post and seeing their vote to ban "vibe-coded" or heavy LLM projects in their Terms of Use legitimately pissed me off.

It is an absurd policy. It mixes up a basic infrastructure problem, uses completely dishonest statistics to justify gatekeeping, and ironically ends up pushing developers directly back into Microsoft’s arms.

  1. Banning tools instead of setting quotas makes zero sense

The practical argument Codeberg makes is that "ghost projects" created by AI are clogging their CI/CD runners, eating up disk space, and getting hammered by scrapers.

Fair enough, server administration is hard. But since when do you solve infrastructure abuse by banning developer tools instead of setting resource limits?

If people are abusing free runners or taking up too much disk space, you cap runner minutes per user and enforce strict storage quotas. That’s how GitHub and GitLab handled it. Low-effort, unmaintained junk repos have been getting pushed to open source since the SourceForge days. Trying to police how someone writes code instead of just setting hard limits on bandwidth and storage is administrative insanity. If a solo dev writes a clean, fully-tested Rust tool in an afternoon using Claude, why on earth does Codeberg care as long as it stays under their storage cap?

  1. The stats in their blog post are completely dishonest

They go on this massive rant about data center energy, SSD prices, and water usage in Frankfurt to frame AI code as an environmental crime. The logic falls apart the second you look at actual data.

They literally complain about enterprise SSD prices jumping from €700 to €3,700 and blame LLM projects on their site. No, enterprise NVMe prices didn't spike because some hobbyist used Copilot to write a bash script. They spiked because Big Tech hyperscalers like Microsoft, Meta, and Google are dropping over $150 Billion a year in hardware CapEx to build massive clusters.

Same story with their energy and water claims. According to the IEA, global data centers account for roughly 1% to 1.5% of global electricity. As for water? Data center cooling is a fraction of a percent of industrial water use—compared to something like US golf courses which consume 1.5 billion gallons of water every single day. Blaming open-source devs using AI assistants for Frankfurt's grid problems (in a country that shut down its own zero-carbon nuclear plants) is pure bad faith.

  1. Linus gets it.

The post assumes that any code written with an LLM is automatically unmaintainable slop. That just shows they haven't paid attention to how modern dev workflows actually look.

Frontier models like Claude 3.5 Sonnet hit over 80-90% accuracy on benchmarks like SWE-bench. People aren't just blindly pasting hallucinated code anymore. Developers use these tools to generate unit tests, write documentation, catch edge cases, and refactor legacy code way faster than they could alone. It raises the floor for solo maintainers.

Linus Torvalds called this out on LKML:

> "AI is a tool, just like other tools we use... But the solution is not to put your head in the sand and sing 'La La La, I can't hear you'... The solution is to make sure those LLM tools help maintainers instead of just causing them pain."

If the creator of the Linux kernel can understand that AI is just a tool that helps maintainers catch embarrassing bugs, why is Codeberg acting like using a coding assistant is a crime against open source?

This just pushes people back to GitHub

FOSS is supposed to be about democratising software and empowering individuals. LLMs give solo devs and non-native English speakers the leverage to build ambitious projects that used to require a whole team.

By declaring that AI-assisted workflows are unwanted "pollution" on Codeberg, they aren't stopping people from using AI. They are just telling those developers: "Go back to GitHub."

How does driving talented builders right back into Microsoft's proprietary ecosystem protect the open-source commons? It does the exact opposite. It enforces an ideological purity test that guarantees Codeberg stays a niche side project while GitHub keeps its monopoly.

Codeberg needs to protect its servers with proper quotas, rate limits, and bot mitigation. This tool-banning nonsense is a massive mistake.

reddit.com
u/Time-Water-8428 — 23 days ago
▲ 27 r/microsoftsucks+2 crossposts

My 11-year-old Microsoft account is permanently locked after being compromised by a hacker and handled by ECR support

Hi all, not expecting much to come out of this, but at this point, I am feeling completely hopeless, desperate, and mentally exhausted. My inspiration for creating a public post was a thread I recently found by u/No_Motor_6299 whose long-standing account was finally returned after making noise publicly ("12-year-old Microsoft account permanently locked 2 weeks after being hacked and recovered"). Interestingly, u/No_Motor_6299 explicitly mentioned that his own inspiration for going public was a previous successful case shared by u/planetgrayareaMy 15-year-old account that was compromised has been returned back to me today.

Following in their footsteps, this is my story about my Microsoft account—originally created nearly 11 years ago—which is currently suspended, and my absolute nightmare dealing with their executive support.

Back in 2022, my account was compromised by a hacker. Immediately after taking over, they locked me out, changed my security information, and altered my primary alias to a completely different email address.

I didn't give up. I spent years gathering information and recently managed to escalate my case to the highest possible tier: the Executive Customer Relations (ECR) team. I even managed to overcome severe social anxiety to complete a live identity verification phone call with a support manager, who explicitly confirmed that my situation and explanations were entirely plausible.

Following their instructions, I compiled a massive, airtight document containing irrefutable historical evidence that only the original creator could ever possess:

  1. The exact worldwide unique PayPal Transaction ID and the original Mojang invoice for my Minecraft purchase, billed in my local currency and tied to my family's payment details.
  2. A list of multiple historical IP addresses spanning over several years, covering my original home internet connections and registration region, including down-to-the-minute timestamps of my very first password changes years ago.
  3. Original un-falsifiable screenshots matching those exact system notifications from the year the account was created, along with historical console hardware details and linked third-party apps.

Despite this mountain of absolute financial and technical proof, the Relationship Manager just sent me this completely generic, cold rejection email:

>

This makes absolutely no sense and feels incredibly insulting. Of course some current data points don't match what is currently on their active record—the hacker changed the alias and cycled through multiple phone numbers (including virtual generators) after I spammed them out of anger! But a unique banking transaction code from years ago cannot be faked or guessed by an intruder.

It feels like human specialists are blindly relying on broken automated scripts without looking at the actual legal and financial evidence. This situation has taken a massive toll on my mental health, and being stonewalled by the "highest tier" of support after providing everything they asked for is incredibly defeating.

My account has almost 11 years of memories, purchases, and personal data attached to it. I have proven beyond a shadow of a doubt that I am the rightful owner.

If anyone here has any advice, knows a workaround, or has any contact with a Microsoft employee, executive, or community manager who can perform a manual override on a blocked account, I would deeply appreciate your help.

TL;DR:

  • My 11-year-old Microsoft account was compromised in 2022 by a hacker who changed the security info.
  • I escalated the case to Microsoft's Executive Customer Relations (ECR) and did a live phone verification.
  • I provided absolute historical proof: multiple local IP logs with exact timestamps and the original unique PayPal/Mojang transaction ID for Minecraft.
  • Microsoft ECR still archived the ticket using a generic copy-pasted script because the data doesn't match the current hacker-modified template. [3]
  • Looking for any advice or internal escalation paths to get a real human to review the banking evidence.

Edit: My original deleted post, which was an inspiration of Planetgrayarea and No_motors got deleted on r/XboxMy 11-year-old Microsoft account is permanently locked after being compromised by a hacker and handled by ECR support

Thanks, everyone, for reading. <3

reddit.com
u/Time-Water-8428 — 3 months ago

Only 1 week until Artemis III crew announcement, who do you want there?

With a Canadian going last time which country should send up somebody if NASA allows? I heard the UK might send up John McFall?

reddit.com
u/Time-Water-8428 — 3 months ago

Should the roman republic-era electoral college system be scrapped?

It is based on the Roman system and was designed for a system before centralised vote-counting was simple, by separating out power rigging is harder and elections are generally fairer, it is also very hard to change a system that has worked fine for millennia.

Do modern technologies make it a good idea to change this system or not?

reddit.com
u/Time-Water-8428 — 3 months ago

Increasing Polarisation in Politics, why?

Regarding the current political landscape in the US, and it feels like the system has grown incredibly polarised compared to previous decades. A lot of this shift seems driven by the political left. It feels like the Democratic Party has moved significantly further to the left, adopting positions on immigration and gender identity that would have been considered fringe or highly unconventional not too long ago. This has then sparked a response from the right, are any of the parties moderate anymore?

reddit.com
u/Time-Water-8428 — 3 months ago
▲ 206 r/spaceflight+1 crossposts

NASA to Announce Artemis III Crew, Provide Mission Progress Update

NASA will provide an update on the agency’s Artemis III mission and announce the astronauts assigned to the test flight during a live event at 11 a.m. EDT on Tuesday, June 9, at the agency’s Johnson Space Center in Houston.

Following the event, the Artemis III crew will be available for limited in-person and virtual interviews.

Artemis III will launch four astronauts from NASA’s Kennedy Space Center in Florida aboard the Orion spacecraft on the SLS (Space Launch System) rocket. The mission will test critical rendezvous and docking capabilities between Orion and commercial human landing systems needed to deliver astronauts to the lunar surface. Building on the successful Artemis II crewed test flight in April, Artemis III will pave the way for future surface missions.

u/Time-Water-8428 — 3 months ago
▲ 750 r/microsoftsucks+3 crossposts

If you thought the Mojang/Skyblock drama was bad, you should see how CraftBukkit died in 2014

For context, and an interesting story older than some of you (Minecraft veterans, feel free to add on):

  • A majority of server software today that the average Hypixel player takes for granted all descended from craftbukkit code in one way or another, like Spigot, PaperMC. To this day, if any of yall have ever coded (plugins, not mods), you will 100% have seen imports using the org.bukkit package
  • The reason those dominate now and not craftbukkit is because back when craftbukkit was the most popular server software in early multiplayer, Mojang recruited a few of the lead developers to join them. This was back when they recruited directly from the community and were more small, indie based.
  • However they also secretly purchased bukkit, which the community did not find out until two years later, when a controversial 2014 EULA crackdown happened (there are news articles about this). Developers like EvilSeph wanted to shut down Bukkit in protest but then Jeb tweeted that Mojang in fact owned Bukkit all along, with several Mojang employees backing him up. "Warren over at bukkit seems to have forgotten that the project was bought by Mojang over two years ago, and isn't his to discontinue"
  • Community programmers realized they had spent two years providing free, unpaid labor to a multi-million dollar corporation under the guise of an open-source community project. This was probably legal, but really really unethical. A lot of people got mad, and one person, Wesley Wolfe (better known online by his handle Wolvereness), invoked the DMCA since bukkit was technically open source under the GPL. The entire bukkit project was taken down.
  • It cannot be understated how bad the fallout was for the developers. While Mojang's legal team aggressively targeted Wesley Wolfe with accusations of extortion, the community, especially server owners, put the blame on bukkit devs as a whole, they viewed the coders as doing this out of revenge
  • This, along with the huge community anger earlier in the year, from the EULA enforcement, may have been a big contributor to Notch selling the game and Mojang to Microsoft, a mere twelve days after the DMCA drama.
  • I also theorize this might have changed Mojang's culture towards community creations, leading to them taking on the laissez faire approach we see today, preferring to let the community run its own server and modding ecosystem after this fiasco
  • The previously mentioned EULA crackdown was the first of many. Although this 2014 one may have been justified, since kids were paying for things like overpowered pvp kits and things parents would not be very fond of. Instead, now you can pay for cosmetics!
  • Spigot had already existed as a fork a year prior, but after Bukkit was taken down, it quickly became the biggest server software and lived in a gray area (that neither side was eager to get rid of) using BuildTools to locally download Minecraft source code, to create Minecraft servers.
u/DereChen — 3 months ago