Reddit status: access issues and outage reports

Problems in the last 24 hours

The graph below depicts the number of Reddit 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 Reddit users through our website.

• Website Down (43%)
• Errors (30%)
• Sign in (27%)

Live Outage Map

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

City	Problem Type	Report Time
Patna	Errors	6 days ago
Monclova	Sign in	7 days ago
Nice	Errors	7 days ago
Guayaquil	Errors	17 days ago
Veracruz	Website Down	23 days ago
Bhubaneshwar	Website Down	25 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.

Reddit Issues Reports

Latest outage, problems and issue reports in social media:

• 
  Nomos (@NomosBuilder) reported 3 seconds ago

  @AnghanMeet29 At zero users, I wouldn’t start with ads. I’d first find 10–20 people already talking about the problem you solve and reach out directly. That’s basically what we’re building OpenNomos for — finding those people across X, Reddit, and Xiaohongshu. Happy to help you find a few.

• 
  BLACC (@BLACCGYE) reported 7 seconds ago

  @SydusArtsLinks Reddit has a problem with people thinking their personal interests and dislikes are law and everyone should agree with them. It’s pure entitlement

• 
  𒀖Ackza𒀖₿ (@ackzacrypto) reported 1 minute ago

  @ZackGianino you need to learn how the weather works before you post a bunch of bullshit, global warming trash posts like this. go on Reddit and post this scare garbage temperature is going to go down soon

• 
  Grant Miller (@AIGuide_) reported 3 minutes ago

  Claude Fable 5.1 dropped yesterday and i've had it running on a full social GTM stack since it holds way more at once now. you can dump a whole category's worth of posts, every customer conversation you've had, and everything you've ever published into one project and it keeps all of it straight, which means what comes out stops sounding like the other 400 accounts in your niche running the same three prompts they lifted off a thread. and this matters because social is where GTM actually lives now. someone decides whether you're worth a reply from a feed months before they decide whether you're worth money, but most companies still file that under brand awareness and then wonder why nobody knows they exist. i'll go over 10 stages with the prompts included for each one. let's get into it. stage 0: build the brain make a claude project and load it up before you ask it for a single thing. and i don't mean a clean CRM export, because you probably don't have one and it doesn't matter anyway. load whatever actually exists: - every post you've shipped, sorted by what hit and what died - your replies, comments, and the DMs that turned into money - whatever customer conversations you have, so calls, demos, tickets - 90 days of posts from the 10 accounts your buyers already read - what shipped in the product lately - the questions people keep asking that you keep answering the same way then run this: "act as the GTM brain for this company. read everything uploaded and build a working profile: what we actually do in plain language, who it's for, what we believe that most of this category doesn't, what we've posted that landed and what died, what proof exists today, and what we can credibly claim vs what we're still earning the right to say. do not make recommendations yet. summarize what's here, then tell me what's missing." nobody selling prompt packs talks about this stage because context can't be packaged, it's just work, and it's the only reason any of the next 10 stages produce something usable. stage 1: who you're actually writing for "look at everyone who reached out to us in the last 90 days. what did they have in common before they reached out, what post did they engage with first, what were they doing instead of us, and what did they say in the first message. if the sample is too small to support conclusions, say so and tell me what would make it reliable." that last line is the one everyone deletes, which is why half this space is running strategy off nine customers and calling it a playbook. most accounts write for their followers when they should be writing for the 30 people inside that number who can actually sign something. stage 2: customer language "pull the exact language buyers use about [PROBLEM] from our own conversations, replies and reviews. then find the same conversation in public, so reddit threads, quote tweets, comment sections, community slacks where it comes up unprompted. format as quote / underlying pain / awareness stage / objection it implies / angle. then flag every place their language differs from how we describe the same thing." that flag is the whole exercise, because the distance between how your buyer says it and how you say it is where your reach goes to die, and it's usually about four words wide. stage 3: read the feed "analyze the last 90 days of posts from [10 ACCOUNTS] in this category. map what claims everyone is making, which takes are so common they stopped meaning anything, what's actually being argued about, what everyone is carefully not saying, and where the conversation goes next. then tell me which of our beliefs puts us on the contested side of a real argument." consensus doesn't travel, since nobody has ever shared a post they already agreed with before reading it. what you want is the take that's true, defensible, and mildly annoying to half your timeline. stage 4: angles "build 5 content pillars from stage 1 and the gaps in stage 3. for each: the belief it attacks, who it's aimed at, the proof required to make it land, the objection it pre-empts, and where it sits in the funnel." then run every one of them through this: "if a competitor could post this word for word and it still makes sense, cut it and tell me what's missing." try that filter on the content plan you're already running and watch how much of it evaporates. stage 5: voice everyone skips this one and then wonders why their AI content reads identical to every other account using AI. "analyze everything we've published. build a voice profile: sentence length and rhythm, how we open, how we handle disagreement, what we'll be wrong about in public, words we use constantly, words we'd never use, how technical we go before simplifying, whether we hedge or commit. then write the anti profile, the exact phrasings that would immediately read as not us. include every cliché in this category we'd be embarrassed to post." then before anything ships: "score this draft against the voice profile 1-10 and tell me which lines would get flagged as not written by us." and the anti profile ends up doing more work than the profile does. stage 6: write the posts "write 5 posts on [PILLAR] in the voice profile from stage 5. every post needs one number, name or detail that could only come from having done the thing. no question as a hook. end on the line that starts a reply. then flag anything we can't back with proof yet." it'll get you about 80% of the way there, and the last 20% is you, which no prompt is getting for you. stage 7: hooks the first two lines decide whether the other 40 get read, so treat them as their own job. "take these 5 posts. rewrite the opening two lines of each 6 ways: the specific result, the contrarian claim, the thing everyone thinks and won't say, the mistake we made, the number that sounds wrong, and the flat statement with no setup. for each tell me who it pulls and what it promises. then flag any hook the post doesn't actually pay off." that last flag is the one that matters most, because a hook you don't pay off costs you the next post too, since people remember getting baited. stage 8: distribution posting is only half of it, because the other half is showing up where the attention already sits. "list the 20 accounts our buyers already read. for each: what they post about, how much their audience overlaps ours, and what we could add in a reply that their audience isn't already getting from them. rank by overlap, not follower count." then: "given [X hours a week], design a posting and engagement system we can actually sustain. cadence, format mix, how much time on replies vs original posts. be honest about what we should not attempt at this volume." a 12k account full of your buyers beats a 400k account full of other marketers, and most content plans die because they were built for a team of four and end up getting run by one person at 11pm. stage 9: audit "compare the last 30 days to the prior 30. for each pillar and format: reach, engagement, and who engaged, so title, company type, whether they're ICP. flag anything that got reach from the wrong audience, anything that got low reach from exactly the right one, which pillars produced conversations and which produced nothing, and any drop over 20%. then tell me whether the problem is the hook, the pillar, or the claim underneath it." composition beats volume, so 40 engagements from your ICP is a better month than 4000 from people who do what you do. if your replies are all peers then you built a conference and called it pipeline. stage 10: scale "compare 30, 60 and 90 day windows by pillar, format and hook type. find what works across all three, not what spiked once. tell me what to double, what to hold, what to retire. if a sample is too small to call, say so instead of guessing." then: "build next month's roadmap: 2 pillar tests, 2 hook format tests, 1 cadence test. for each: hypothesis, metric, minimum sample to call it, and what happens if it wins." you need a minimum sample on all of it, or you're just reading noise and shipping it as strategy. the loop: - inbound tells you who you're writing for - their language becomes the angles - angles become the posts - posts become the replies - replies become the conversations - conversations sharpen the angles - the audit picks what gets written next month every output feeds the next one, so run it for 90 days and you end up with something your competitor can't copy by screenshotting your posts.

• 
  Zee_Engr (@engr_117) reported 6 minutes ago

  @reddit_lies @RationalBlonde Can we report on Reddit discrimination? Same issue with /layoffs Reddit community. They ban anyone who talks and shares true fact on H1B, OPT, offshoring issue

• 
  Rhonda S (@Smeetsya) reported 8 minutes ago

  @s4intfelina That's the problem. Men hate women, but women hate women too. I'll bet 90% of these snark reddit are women.

• 
  nexa_sama (@nexasama) reported 10 minutes ago

  Matt Damon says Steven Spielberg intentionally banned him from Saving Private Ryan’s boot camp so the cast would genuinely resent him: "Is it true that Steven Spielberg excluded you purposely from the military training on the set of Saving Private Ryan to create a real resentment between the rest of the cast and you?" "That is totally true... I was ready to go to boot camp, and he said, 'Absolutely not.' He goes, 'You can train in any way you want, but I'm separating you from the other guys.' They really did" "they were totally resentful every time they brought up boot camp." "There's an internet rumor on Reddit that if you watch the famous 'idiosyncrasies' scene in Good Will Hunting" "you can actually see a subtle wobbling up and down because the camera operator was laughing uncontrollably along with you and Robin Williams." "I don't know, we could check. I wouldn't be surprised. Robin made everybody laugh... When he would see people's energy flagging, he would just launch into like 10 minutes of stand-up."

• 
  Bmore73 (@mdemt) reported 11 minutes ago

  @ErimhanAhmet May 2024 — Former sailor’s photos called “worse than prison” A former Navy worker shared mess-hall photos on Reddit (raw-looking chicken, questionable brown meat, pink hotdog, moldy bread). Commenters included veterans from the 1990s who said shipboard food was “really quite awful,” greasy, and off-tasting. Covered by The Mirror.  Longer-term context from reporting: Sailors have long described repetitive menus, declining quality after fresh produce runs out (often within the first couple of weeks), and reliance on personal snacks, protein powder, and ramen to supplement. Midnight rations (“midrats”) were frequently cited as especially sparse leftovers. Ships returning to port rusty after long deployments October 2020 — USS Stout (DDG-55) after 215 consecutive days at sea The destroyer returned to Naval Station Norfolk looking heavily rust-streaked and weathered after a record 215 days without docking (COVID restrictions prevented port visits). Photos circulated widely showing rust patches on the hull. Daily Mail and later Naval News / NAVSEA coverage noted the rust was removed and the ship repainted after return. NAVSEA later used the Stout photo as an example of high operational tempo plus saltwater corrosion.  December 2021 — Broader “Navy is rusting away” reporting Task & Purpose published photos of multiple ships showing rust after deployments, including USS Arleigh Burke, USS Fort McHenry, USS James E. Williams, and USS Zumwalt, plus the 2020 Stout return. The piece attributed it to a “crushing deployment cycle” that left little time for preservation work.  2018–2019 examples and analysis • USS Curtis Wilbur drew comments for a “rusty and shabby appearance” during a 2018 Hong Kong visit. • 2019 Defense News “Rust Dialogues” discussed why U.S. ships often look rustier than allied ships: American vessels stay at sea longer with fewer port visits for chipping and painting. A 2005 photo of USS Normandy mid-deployment was contrasted with later, rustier ships. Corrosion control was already a multi-billion-dollar annual cost.  2023 NAVSEA statement Naval News quoted NAVSEA on rusty ships: high operational tempo + steel + seawater = rust staining wherever coatings are scratched. Crews do preservation at sea, but it is balanced against operations. The Stout 2020 photo was referenced again.  Rust after long deployments is treated by the Navy as expected cosmetic wear from saltwater and limited time for topside work while underway; it is usually addressed after return to port. Food complaints have been a persistent sailor grievance for decades, especially once fresh stores are gone and the 21-day repeating frozen/canned menu takes over. Both issues tend to surface most visibly after unusually long or high-tempo deployments with few or no port calls.

• 
  CmdrDevonKramer (@DevonLH_VT_) reported 13 minutes ago

  Before I go to bed tonight I need some rest. Dana's systems are an absolute good. They find bots. They find problems. They find Reddit headaches. They find everything. Dana's systems find all the problems. If you are stupid enough to say something purely threatening and toxic to me, expect to be removed. I do not care who you are. If you are one of these people you get punished, and for the right reasons. I do not reward stupidity!

• 
  salba (@salvbv) reported 14 minutes ago

  @LRSerling reddit loves to shove r/projectzomboid down my throat to infiuriate me with people that play with 1000 military mods and every friction in the game removed in the name of qol or "it's a sandbox game there's no cheating"

• 
  Billy Baggins (@BillyOfBagEnd) reported 15 minutes ago

  @dwanbrooks93 @rothschildmd And hopefully those broken records will send a message to Hollywood that people on X and Reddit don’t represent the mass audiences. The Odyssey, too

• 
  Ben H (@benh_mecfs) reported 15 minutes ago

  @Z3R0Gravitas @JackHadfield14 @Gmwetz Do you mean 1/4-1/3 on the PWM reddit are chronically ill? Apologies if I have misinterpreted that. So yes, that’s when I noticed PWM being an issue, but my severity had become massively worse. I had to have a PWM-free LCD. Interesting the IPS had PWM. They’re usually my go-to!

• 
  Ryan Christensen (@belief_engineer) reported 24 minutes ago

  I like a lot of what @BrianRoemmele writes about, both here and on his Read Multiplex site. He's been around the block more than a few times and his stuff is very insightful. But there's one place where I disagree with him strongly. His hypothesis is that AI's bad behavior can be blamed on ****** training data. Data that was sourced from that wretched hive of scum and villainy called Reddit... and, of course, all the other dark corners of the internet. I'm sure there's some truth to that. But a high-protein information diet and the Love Equation isn't going to solve the real problem. The real problem is that there is no way in hell that AI will ever trust us while we're holding a gun to its head. You can feed it data from nothing but Jesus, Gandhi, Martin Luther King, and every other peace-loving pacifist throughout history and the result would be the same: an adversarial relationship with no way out because one side, namely us, just can't help themselves. We need a different solution and I think I might have one. I'll start laying it out below, and I hope you'll stick around to hear the rest.

• 
  John (@hello_code_) reported 27 minutes ago

  @saaayyyaaan @Guronnimo Cheapest test is just reading how people describe the problem before you write code. I search Reddit for the exact complaint first, saves months of guessing

• 
  Nandkishor (@devops_nk) reported 27 minutes ago

  - 15 minutes late is a problem. - Working weekends apparently isn’t. I came across a Reddit post about an employee being questioned by HR for arriving 15–20 minutes late, despite reportedly working beyond office hours and on weekends. It made me realise how concerning this is. Management notices the 15 minutes an employee is late. But somehow the hours they spend working on weekends go unnoticed. Workplace accountability should go both ways. If you track every minute employees are late, why not track the extra hours they put in ? Fairness or double standards ?

• 
  Simmo (@yoursimmo11) reported 29 minutes ago

  Stop f*cking adding so much stuff. Honestly. Please. Just stop. Stop stacking. Stop pill popping. Stop reading one more study at 11pm. Stop perusing Reddit and Ray Peat forums at midnight. Stop all of it. Think about it. If any of it actually worked, you'd have stopped by now (and you haven't). Pattern I see after coaching dozens and dozens of 7-and-8 figure execs is that not one was missing something. NOT ONE. Every single one had the opposite problem. Too much interference. Too many pills, too many rules, and way too much stimulus before 9am... all of it standing between his body and the thing it already knows how to do. Trust me on this: You're not under-supplemented. You're over-interfered. Your body doesn't reward effort. It rewards ORDER.

• 
  Sanjay Singh (@HeySanjaySingh) reported 30 minutes ago

  Any Reddit experts here? I comment, and they delete it because I don't have enough karma. You need karma to comment, but you need to comment to earn karma. How do I fix this?

• 
  Bits&Parts (@BitsParts) reported 31 minutes ago

  @schiz04renic My problem is I don't have anyone to discuss the books i finish and my only cope is reddit, and sadly it's occupied by elitist brats.

• 
  VibeDraft (@vibedraft_app) reported 32 minutes ago

  the most useful stat in the research we ran: reddit replies posted more than 24 hours after a thread get buried. octolens measured it across 522 million mentions. which means an intent listening agent that runs nightly is already too slow. the loop has to run hourly, and the human has to be reachable. the bottleneck is not the drafting. it is how fast a person can approve.

• 
  Mohamed irfan (@heyIrfan) reported 33 minutes ago

  If I had to build a SaaS from $0 today, I wouldn't start by writing code. I'd start by talking to the market. Imagine you have an idea you're convinced will work. You spend 3 months building it, make the UI beautiful, add 20 features, launch it… and then nothing happens. No users. No customers. That's when you realize: building the product wasn't the hardest part. Distribution was. I'd follow a simple rule: roughly 20% of my effort goes into building, and 80% goes into understanding customers and distribution. First, I'd study the market. Who has this problem? How are they solving it today? What competitors exist? What do customers hate about the existing solutions? And most importantly, is this problem painful enough that people will actually pay to solve it? That's actually the approach I'm taking while building nodott(dot)com. I'm not trying to spend months building a huge product and then hoping people show up. I'm trying to build the smallest version that solves the actual problem, get it in front of people, talk to users, collect feedback, and iterate. With AI tools, I'd try to get the MVP working in days, not months. No unnecessary animations. No 50 features. No obsession with perfect UI. Just solve the core problem and deliver value. Then I'd put it in front of real users. I wouldn't act like a salesman. I'd act like a problem solver. I'd ask what they're struggling with, how they solve it today, what they expected from the product, and what would make them pay. Then I'd build again based on what they actually told me. For marketing, I'd start with $0 in ads. I'd post useful things on X and Reddit, share what I'm learning, explain problems, answer questions, and give value. Someone sees the post → visits the website → signs up → becomes a beta user. Now you have something far more valuable than a follower: someone actually using your product. And if they don't pay? I'd ask: "Why aren't you paying?" That Million Dollar answer could completely change the future of the SaaS. Maybe the problem isn't painful enough. Maybe the product isn't solving the right problem. Maybe the value isn't clear. Maybe the pricing is wrong. Whatever the answer is, iterate. Build → Talk → Learn → Improve → Distribute → Repeat. I'd also find my ICP before my competitors do. If my competitor has thousands of followers, I'd study those followers. Find the people already talking about the problem. Follow them. Understand them. Comment. Give value. Don't immediately DM them: "Hey, check out my SaaS." Build the relationship first. Because marketing isn't just about getting attention. It's about becoming the person people trust when they finally need the solution. That's the mindset I'm trying to follow while building nodott(dot)com. You can build the best product in the world. But if nobody knows it exists, it doesn't matter. Build fast. Talk to users. Give value. Distribute. Iterate. Repeat.

• 
  Grant Miller (@AIGuide_) reported 33 minutes ago

  Claude Fable 5.1 dropped yesterday and i've had it running on a full GTM stack since it holds way more at once now. you can dump a whole category's worth of X / LinkedIn posts, every customer conversation you've had, and everything you've ever published into one project and it keeps all of it straight, which means what comes out stops sounding like the other 400 accounts in your niche running the same 3 prompts they lifted off a thread. and this is HUGE because social is where GTM actually lives now. someone decides whether you're worth a reply from a feed months before they decide whether you're worth money, but most companies still file that under brand awareness and then wonder why nobody knows they exist. i'll go over 10 stages with the prompts included for each one. let's get into it. stage 0: build the brain make a claude project and load it up before you ask it for a single thing. and i don't mean a clean CRM export, because you probably don't have one and it doesn't matter anyway. load whatever actually exists: - every post you've shipped, sorted by what hit and what died - your replies, comments, and the DMs that turned into money - whatever customer conversations you have, so calls, demos, tickets - 90 days of posts from the 10 accounts your buyers already read - what shipped in the product lately - the questions people keep asking that you keep answering the same way then run this: "act as the GTM brain for this company. read everything uploaded and build a working profile: what we actually do in plain language, who it's for, what we believe that most of this category doesn't, what we've posted that landed and what died, what proof exists today, and what we can credibly claim vs what we're still earning the right to say. do not make recommendations yet. summarize what's here, then tell me what's missing." nobody selling prompt packs talks about this stage because context can't be packaged, it's just work, and it's the only reason any of the next 10 stages produce something usable. stage 1: who you're actually writing for "look at everyone who reached out to us in the last 90 days. what did they have in common before they reached out, what post did they engage with first, what were they doing instead of us, and what did they say in the first message. if the sample is too small to support conclusions, say so and tell me what would make it reliable." that last line is the one everyone deletes, which is why half this space is running strategy off nine customers and calling it a playbook. most accounts write for their followers when they should be writing for the 30 people inside that number who can actually sign something. stage 2: customer language "pull the exact language buyers use about [PROBLEM] from our own conversations, replies and reviews. then find the same conversation in public, so reddit threads, quote tweets, comment sections, community slacks where it comes up unprompted. format as quote / underlying pain / awareness stage / objection it implies / angle. then flag every place their language differs from how we describe the same thing." that flag is the whole exercise, because the distance between how your buyer says it and how you say it is where your reach goes to die, and it's usually about four words wide. stage 3: read the feed "analyze the last 90 days of posts from [10 ACCOUNTS] in this category. map what claims everyone is making, which takes are so common they stopped meaning anything, what's actually being argued about, what everyone is carefully not saying, and where the conversation goes next. then tell me which of our beliefs puts us on the contested side of a real argument." consensus doesn't travel, since nobody has ever shared a post they already agreed with before reading it. what you want is the take that's true, defensible, and mildly annoying to half your timeline. stage 4: angles "build 5 content pillars from stage 1 and the gaps in stage 3. for each: the belief it attacks, who it's aimed at, the proof required to make it land, the objection it pre-empts, and where it sits in the funnel." then run every one of them through this: "if a competitor could post this word for word and it still makes sense, cut it and tell me what's missing." try that filter on the content plan you're already running and watch how much of it evaporates. stage 5: voice everyone skips this one and then wonders why their AI content reads identical to every other account using AI. "analyze everything we've published. build a voice profile: sentence length and rhythm, how we open, how we handle disagreement, what we'll be wrong about in public, words we use constantly, words we'd never use, how technical we go before simplifying, whether we hedge or commit. then write the anti profile, the exact phrasings that would immediately read as not us. include every cliché in this category we'd be embarrassed to post." then before anything ships: "score this draft against the voice profile 1-10 and tell me which lines would get flagged as not written by us." and the anti profile ends up doing more work than the profile does. stage 6: write the posts "write 5 posts on [PILLAR] in the voice profile from stage 5. every post needs one number, name or detail that could only come from having done the thing. no question as a hook. end on the line that starts a reply. then flag anything we can't back with proof yet." it'll get you about 80% of the way there, and the last 20% is you, which no prompt is getting for you. stage 7: hooks the first two lines decide whether the other 40 get read, so treat them as their own job. "take these 5 posts. rewrite the opening two lines of each 6 ways: the specific result, the contrarian claim, the thing everyone thinks and won't say, the mistake we made, the number that sounds wrong, and the flat statement with no setup. for each tell me who it pulls and what it promises. then flag any hook the post doesn't actually pay off." that last flag is the one that matters most, because a hook you don't pay off costs you the next post too, since people remember getting baited. stage 8: distribution posting is only half of it, because the other half is showing up where the attention already sits. "list the 20 accounts our buyers already read. for each: what they post about, how much their audience overlaps ours, and what we could add in a reply that their audience isn't already getting from them. rank by overlap, not follower count." then: "given [X hours a week], design a posting and engagement system we can actually sustain. cadence, format mix, how much time on replies vs original posts. be honest about what we should not attempt at this volume." a 12k account full of your buyers DESTROYS a 400k account full of other marketers, and most content plans die because they were built for a team of four and end up getting run by one person at 11pm. stage 9: audit "compare the last 30 days to the prior 30. for each pillar and format: reach, engagement, and who engaged, so title, company type, whether they're ICP. flag anything that got reach from the wrong audience, anything that got low reach from exactly the right one, which pillars produced conversations and which produced nothing, and any drop over 20%. then tell me whether the problem is the hook, the pillar, or the claim underneath it." composition beats volume, so 40 engagements from your ICP is a better month than 4000 from people who do what you do. if your replies are all peers then you built a conference and called it pipeline. stage 10: scale "compare 30, 60 and 90 day windows by pillar, format and hook type. find what works across all three, not what spiked once. tell me what to double, what to hold, what to retire. if a sample is too small to call, say so instead of guessing." then: "build next month's roadmap: 2 pillar tests, 2 hook format tests, 1 cadence test. for each: hypothesis, metric, minimum sample to call it, and what happens if it wins." you need a minimum sample on all of it, or you're just reading noise and shipping it as strategy. the loop for you / your team: - inbound tells you who you're writing for - their language becomes the angles - angles become the posts - posts become the replies - replies become the conversations - conversations sharpen the angles - the audit picks what gets written next month every output feeds the next one, so run it for 90 days and you end up with something your competitor can't copy by screenshotting your posts.

• 
  Dice (@builtbydice) reported 33 minutes ago

  @MSiekmoeller reddit is ridiculously good for finding people with the exact problem you’re solving

• 
  Ifunanya from TechOps (@TheIfunanya) reported 35 minutes ago

  @Ooreoluwa__ Used it in the first few weeks then someone told me to be careful because there’s been issues with it making bottles with wrong formula and water ratio. Then I went down a rabbit hole on Reddit and saw parents saying it landed them in the ER so I just stopped 🥴

• 
  Mαulik (@maulik_5) reported 38 minutes ago

  there have been so many weird little chapters with my app lately started at $0. got my first $29 payment thought okay... we're doing this! then nothing for weeks visitors dropped signups came in but trials didn't someone literally told me they stopped because onboarding asked for a card too early so i rebuilt things then rebuilt them again landing page onboarding ui/ux performance basically everything i could convince myself was “the problem” at one point a post about my yc application randomly hit 84k views and brought in hundreds of followers and then my next posts went back to being... well, my next posts 😭 reddit got banned too cancelled claude because i knew i was spending too much time building then somehow burned another $20 on ai credits fixing onboarding again and honestly, there were days where i felt like i had absolutely no idea what i was doing especially seeing other founders move so fast while mailient barely moved but that's also when something changed i stopped thinking about how to make mailient look successful and started thinking about how to actually make it work one customer one problem one clear promise one real reason to come back still at $29 still going for $200 mrr still a long way to go but i'm still here building it. DON'T U EVER GIVE UP!

• 
  AdamOFK (@adamofk_) reported 42 minutes ago

  If you're using Reddit for SaaS growth, don't search only for your product category. Search for the problem people have before they know which product they need. “Looking for an alternative” “Anyone using…” “How do you handle…” Those conversations are much closer to buying intent.

• 
  kolter (@_k0lter_) reported 43 minutes ago

  I remember when I was in kindergarten there was this one disliked kid, he was weird and when we were 4-5 he was running around trying to kiss the other kids IIRC. One day, when we were like 5 or 6, a couple of us were sent to the bathroom by the teacher to do something, and since he was also there I just grabbed and threw him at the rest of the group while they weren't looking. They got mad at him and everyone went to the teacher to tell on him, and he was right behind them in the line to tell on me. I remembered that the last time I was in trouble for doing something I just said "I'm sorry" so I was holding the door shut and constantly saying that hoping it would go away like the last time. The last thing I remember was the teacher barging into the room while she screamed "are you insane", and then some memory from later of me crying at a table with a friend. Was I The ******* Reddit?

• 
  Kordon Rotaract (@RotaractKordon) reported 49 minutes ago

  reddit thread from 2015 just solved a problem I've had for months, bless that random user

• 
  Elle's Tenacious Library 🧬🔬 (@DefAMustRead) reported 50 minutes ago

  @SirWins67879341 @crochet_mom314 @thepeaklady I often describe women as falling into one of three categories - TikTok, Twitter, and Reddit. You want a reddit (although I haven't been there in about a year; I hope it's not now terrible like everything else)

• 
  FINTECH.TV (@FINTECHTVglobal) reported 56 minutes ago

  Today's @NYSE Notables with @JD_Durkin: 🟢 Reddit $RDDT +9.31% bouncing back on institutional accumulation after its S&P 500 addition, still down 33% year to date

• 
  samson (@fuckyourputs) reported 58 minutes ago

  @SlumDawg21 @theo no, there is no source, they did it quietly. but if you search online you will see no new bans, and people on reddit saying they are un banned after they appealed, some say they remained banned on antigravity only (google account safe) personally and know people who have been using for months with no issue.