dewey

Grinding through abandoned source code in hopes of finding a vulnerability isn't exactly the most fulfilling work for many, perfect use case for AI which doesn't sleep.

> and they need people with the right incentives in place to get it done

Their c-levels wrote blog posts about the current state and why it happens, pretty sure they know what's going on.

You are basically saying that you, from the outside, have solved the problem perfectly and the whole team of engineers at GitHub just don't know about this one simple solution you are proposing.

Have you considered that you don't have the full context of the problem and it's not "just" a few small tweaks?

Many people, as your TV and sometimes friends have to connect to it and you don't want to explain Tailscale to them.

No https://cursor.com/blog/git-at-any-scale

The attention for ideas like that usually fades as quickly as it came after the downtime is over.

The "but don't you know git is distributed" commentary always sounds clever, but it really isn't.

GitHub isn't just used to host your actual git work tree and everyone knows that, it's an issue tracker, an easy way for projects to get contributions as everyone already has a GitHub account, an easy way to receive bug reports, CI, a website for your project, a popularity metric like GitHub stars (For better or worse).

That's exactly why you put it on GitHub, which is the most visible place so people will mirror, check it out locally etc.

From the documentaries I've watched it's usually the other way around. There's either already a known buyer, or the thief has someone in their circles that already knows how to sell it. So there's a middleman between already trusted entities.

Thanks, I misunderstood that and thought you meant colocating next to their server by figuring out where their infra is. Didn't know it's an official feature of theirs.

Do you know what KYC stands for?

Also you don't need a separate container for each of them. Why not run one and have multiple databases in there?

I actually always find SQLite more annoying than Postgres. Postgres I just run on the host and let all my containers talk to the same instance, one thing to backup. With SQLite it's always about volumes, permissions, backing up individual files for multiple projects.

It also makes it much easier to just point my Postgres GUI client to my remote server (Behind Tailscale of course) and query the database there without copying over the SQLite file to my local machine, or mount it somehow. Even for simple projects that I start I always prefer Postgres.

There’s also https://autobrr.com/ - not exactly the same but many overlapping features, lightweight, written in Go and works well with que and qbitorrent.

Also all the developers are angry and trying to build for Duo right now that didn’t even give them a simulator in time, so makes sense to not rush this out right away.

"make no mistakes"

Dupe with more comments on the front page: https://news.ycombinator.com/item?id=50057956

> But they don’t ask for your password anymore.

Just because you haven't seen it, doesn't mean it's not happening. I'm getting a monthly email from my brokerage (IKBR) that literally says phishing:

> Our clients have seen a wave of “phishing” attempts in which scammers are impersonating Interactive Brokers. They send requests—sometimes by text, sometimes by email—for urgent updates of client information (often tax or other key information) and include login links pointing to websites that appear legitimate but are actually fake websites. If you click those links, you may inadvertently give bad actors access to your account.

> Phishing isn’t a big threat to regular consumers.

Can you back that up with data? Anecdotally regular people get phished all the time, why do you think banks are sending out frequent reminders, show banners on their websites and apps about phishing attempts in the wild and mail providers explicitly showing if something is an official Google / Fastmail communication and when it's not.

When I see phishing mail they are always for banking, Google / iCloud accounts and not specifically targeted at "corporate" or government agencies.

Opinion from someone who's working on Passkeys at Apple and is very open and transparent about his work there (For many years already), which is rare for someone working at Apple. This makes me appreciate this much more.

https://mastodon.social/@rmondello@hachyderm.io/117428259125...

Running a website with comments and "social" elements became much harder the longer time went on, can't really blame them for shutting it down.

Communicate what you do -> "master of social media"

Don't communicate what you do -> "what did they even do?"

Yes, because it would not be an "or" but an "and", more features = more tokens.

That’s a pretty common title format for talks or blog posts long before LLMs existed.

It's as centralized as everyone running their znc on Hetzner. It's mostly just a bouncer with a nice web interface (Like The Lounge) and a rudimentary app for people who want to pay someone to run this setup. You'd still connect to Libera and other networks and there's zero lock in.

You don't need protocol support for uploading images to storage, and then rendering it inline. Many clients have been doing that for years.

Sadly https://x.com/palaverapp is no more, it was a great iOS client. I just tried to find it in the app store and saw it got removed.

Ergo looks really cool, will have to take a look at that. Thanks for sharing.

I like IRC, and I am online all day on various servers, for nostalgia reasons mostly, but I think everyone knows it's dated, had its time and will slowly fizzle out if we like it or not.

I think the main problem there is that there's not really any motivation to build that on top of a simple protocol like IRC. The strength of the protocol is that it's distributed, easy to understand, text based and lightweight and I'd guess most current IRC users are people who use it for a very long time already.

Tucking all these mainstream features that people are used to this days to get feature parity with any other competitor (Slack / Teams / Discord / Matrix etc.) will not make IRC more popular, it will make the protocol more complicated and fragmented.

Yes, but compared to "modern" apps IRC is very rudimentary and you would not get messages if you "close the app". You always have to run some secondary infrastructure like a bouncer to get offline messages or see what happened while you were away.

I know that's not the fault of the protocol itself, but that's always one of the biggest hurdle for IRC adoption when everyone is used to just open apps and see the full history at all times.