it's been a hot minute since ive been on reddit, but iirc shadowbanned means "it appears I can interact, but in fact my posts and comments are silently being hidden from other users"

it looks like you're just straight up being banned.

just under 50% of people voted in Ohio in the 2020 election.

Trump won by 8%.

If just 9% of the people who felt like you (what's the point of voting) had showed up to vote for Biden, that would have flipped the state.

No single raindrop believes it can make any difference. But together, all those insignificant raindrops can change the course of a river in a single day.

The client is open source, so it doesn't matter what the server code is, you can see everything the client sends and therefore tell what possible data is being collected.

It's run by a non-profit so there's no shareholders to please.

Your messages and decryption key are not stored on their servers.

It's been independently audited.

They have publicly posted responses to user information requests where they only provide the account creation date and last access time.

The (admittedly incompetent) US government recommends using Signal (for non-classified information) and top officials have been caught using it (Houthi Working Group).

You can never be 100% sure, but it appears to have excellent security and privacy.

What happened?

You put all your eggs in one basket then let someone else carry it, that's what happened.

Headphones don't make you go deaf, it's the volume level. Just keep the volume low and your hearing will be fine.

weird way to spell "run DOOM" but okay.

When you hear “I’ve got this great app idea—it just needs someone to code it,” it may sound to you like you’re halfway there. But from a programmer’s point of view, that’s actually the least interesting and riskiest way to start. Here’s why:

1. There’s no roadmap—just “code this”

• Undefined scope: If all I have is a vague idea, I don’t know what “done” even looks like. Am I building a basic prototype? A polished product? What features must it have on day one, and what can wait until later?
• Endless scope creep: Without clear boundaries, every conversation becomes “Just one more little thing,” and suddenly what was supposed to be a weekend project balloons into months (or years).

2. You’re asking me to invent half the project

• UI/UX design: How should it look and feel? What screens go where? How do users navigate? That’s a specialized discipline all its own.
• Product strategy: Who exactly is this for? Why will they use it? How will you reach those users? If you can’t answer that, I can’t write code that solves a real problem.
• Testing & polish: Code needs testing, bug-fixing, documentation, deployment, maintenance… none of which you’ve accounted for.

3. No incentives, no commitment

• Why me? Great programmers want to work on problems they find meaningful, challenging, or fun—and ideally get compensated for their time. “Just code my idea” won’t light anyone’s fire.
• Who owns it? If I invest weekends or nights building your vision, what do I get? Equity? Pay? Recognition? Without a clear agreement, it’s a recipe for frustration and resentment.
• Long-term support: Apps need updates, server maintenance, user support. If you haven’t thought through who handles that, you’re building technical debt.

4. Real success stories are team sports

• Cross-functional collaboration: The best apps come from teams that include product thinkers, designers, data analysts, marketers—and yes, developers. You can’t outsource half the work and expect a hit.
• Iterate and learn: You start with sketches or clickable wireframes, show them to real people, iterate, then bring in developers to build a minimum viable product. That way, you’re coding something people actually want.

What you can do instead

1. Write a one-page spec: Describe the core problem, your ideal user, key features, and success metrics.
2. Mock it up: Even hand-drawn sketches of each screen help communicate your vision.
3. Validate your idea: Talk to potential users. If they’re excited, you’ve got something to build.
4. Find a partner: A developer who’s excited by your clear plan—and who sees a fair path to reward for their effort.

In short: coding is only about 20% of what it takes to launch a successful app. If you can’t show a programmer that you’ve thought through the other 80%, they’ll politely pass—because turning a half-baked idea into a working product is a lot more work (and risk) than it looks.

https://www.atomictunayachts.com/...

Bill Clinton ordered the GPS system to be available for civilian use in 2000. The GPS system has replaced mechanical navigators on almost all boats and ships.

Part of being an academic is being available to discuss your publications. Your full name will not only be flying around the internet but recorded permanently in libraries and journals.

Science is about collaboration, and standing behind the work you do, publicly. You will find it extremely difficult or impossible to get your PhD without being known to the academic community.

I think you won't find many anonymous scientific papers held in high regard.

In the US, discussing salary with coworkers is protected speech. It helps people find out if they are being underpaid or unfairly discriminated against. I always share my salary information when asked and I think it's important to do so.

My salary is not indicative of my net worth. I could have a 7 figure salary and be drowning in debt, or make 75K and be doing fairly well because of responsible choices.

I dislike the stigma of discussing salaries, and believe that it's propagated by companies to dissuade workers from getting fair salaries.

uBlock is a content filter. Cookies are set when a server responds to a web (http/https) request. So if uBlock has a domain blocked, not only are any cookies blocked, but no requests make it to that domain (whatever.com) at all.

If a domain is not blocked by uBlock Origin's filters, then cookies are set per your browser's configuration. Firefox I believe blocks some 3rd party tracking cookies by default, but can be configured to block all third-party cookies as well, but this may break site functionality like single sign-on.

Give it to the dev, and explain the situation. Let them know it seems too big/complex of a PR, but you're willing to make additional changes, or break up PR to make it more palatable for merging. It's in the dev's hands after that.

I don't think you should release your own fork without at least trying to work with the original project.

Make sure all your commits have detailed commit messages so that the dev can follow what you were doing (upgrading deps, refactor because xyz, etc.) Don't just record what was changed, explain why it was changed.

anyway that's what I would do.

Think they are joking? A Cat Explains DNS

https://www.zalgo.org/

T̸̛̟͚͋͛̈̊͜͝Ờ̶̤̫̦͙̜̫͇͕͈̘̭̈̑̓̀̈́̌͊͛̆͐̌̈́͝ͅN̸̯̫̺̄̿̎͗͗́͜Y̷̢̱͚̖̤̠̞͉̅́̋̉̿̇̎̋͆͝͝ ̸̧̡̨̧̡̛̖̤̜͔̲̯̞͉͈̻̎̈̄̓̊̄́̕͘͝͠ͅT̷͎̝͌̅̔̓̒H̷̨̧̧̳̱̜͓̮͍̣̬̩̜̙͚̑̌́̑͋̽͗̎͑̊͛̍́͒̕͝͠Ḙ̵̥̥̘̻͔͛̑͒̿͋͝͝ ̶̡͚̬͈̏͌̓̔̈̔̀͌̔̓̾̓͘͝P̷͙̃́̈͐̆̂́͗̏͌̈́Ô̶͎͓̹͖̘̟̬͚̻̦̩͔͛͜͠ͅŅ̶͖̜̱͍̦̔̊͐͆̾̎́́̈́̄̓ͅẎ̸̨̭̜̼͎̜̜͕̥͙̼̤̟̞̄̊̂́ͅ ̴̡̡̛̲̟̳̯͔̝̟͙̌̽͋̏̾̆̅̏̐̅͑̿̀͒̉H̵̪̞̩̥̫̺̅̑̈́̾͌͛́̾̅̈͛͒̾̌̈͐͝Ȅ̶̘̲͙̖̬̞͕̱͍̥͈̦͈͍͔̩̑̒̐̇̑̈́̏͊̽͜͝͝͝ ̸̨̛̛̻̘̙̯̰̦̻͈͓̒̽̉̈̄̌̄͊͂̈͆ͅC̵͙̗̣̮͈̜̪̞̰̣͎̙̏̌̄͗͜Ȯ̸͇̖̼͈̗̝͔̜̘̲̦̦̾̃̆̍͝͝ͅM̷̨̧̮͕̠̘̔ͅÉ̶̡̡̢̡͕̺̗̩̝̩͇͓̄͐͆͛̔̈́̕͜ͅS̵̡͙̬͔̞̞̳͓̜͔͑̌̓̎͆͌̈͌̌̂͛̚͘͝

"This is how I spent the previous month, creating these 3D printed objects to achieve a goal", not "I am about to pass away and I spent my final month 3D printing these forgettable objects"

Some antibiotics, like sulfonamides, can be used in dogs but might cause adverse reactions in humans, such as allergies or severe skin reactions.

https://actionnetwork.org/...

if you know how to code, you can vibe code because you can immediately see and be confident enough to identify and not use obvious mistakes, oversights, lack of security, and missed edge cases the LLM generated.

if you don't know how to code, you can't vibe code, because you think the LLM is smarter than you and you trust it.

Imagine saying "I'm a mathematician" because you have a scientific calculator. If you don't know the difference between RAD and DEG and you just start doing calculations without understanding the unit circle, then building a bridge based on your math, you're gonna have a bad time.

ftfy