frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Watch How the Office Became the Worst Place to Do Work [video]

https://www.wsj.com/tech/personal-tech/watch-how-the-office-became-the-worst-place-to-actually-do...
2•erickhill•7m ago•1 comments

Anatomia Di Tor – The Tor Protocol, Byte by Byte

https://github.com/aleff-github/onion-routing-anatomy
1•aleff•8m ago•0 comments

XiangShan Tapeout History

https://docs.xiangshan.cc/zh-cn/latest/tapeout/
1•camel-cdr•8m ago•0 comments

A New Shape for Work

https://www.notion.com/a-new-shape-for-work
1•pikdum•12m ago•0 comments

Making torch_remat work in TorchTitan

https://docs.pytorch.org/devlogs/distributed/2026-11-19-torch-remat-in-torchtitan/
1•matt_d•16m ago•0 comments

Forensic dissection of Roland J-6's 64 presets: measuring the hidden settings

https://github.com/liotier/RolandStuff/blob/main/J-6_presets_measurement/README.md
1•liotier•20m ago•0 comments

Is Ssense Pivoting to AI Slop?

https://www.thecut.com/article/is-ssense-pivoting-to-ai-slop.html
1•randycupertino•22m ago•1 comments

Your target market isn't demographic (2025)

https://longform.asmartbear.com/target-market/
2•mooreds•22m ago•0 comments

How to generate an accessible color palette from a single color

https://taisho.design/en/blog/accessible-color-palette-from-one-color
2•PabloDiFIlippo•25m ago•0 comments

Scaling Postgres to 1M durable workflows per second

https://www.dbos.dev/blog/one-million-workflows
3•KraftyOne•25m ago•0 comments

Show HN: Primeward – Exploring a stateful recurrence for the next prime

1•alexhr•33m ago•0 comments

Vulcan Street Plant

https://en.wikipedia.org/wiki/Vulcan_Street_Plant
1•_doctor_love•34m ago•0 comments

Catching Crumbs from the Table [pdf]

https://gwern.net/doc/fiction/science-fiction/2000-chiang.pdf
2•gchamonlive•35m ago•1 comments

Show HN: Jam – A music making game where you play gigs to earn studio gear

https://jam.resonantdsp.com
1•garrinm•37m ago•0 comments

Athanor (furnace)

https://en.wikipedia.org/wiki/Athanor
1•_doctor_love•43m ago•0 comments

Show HN: Park – save and recall work context across repos and machines

https://svandragt.github.io/park/
1•pacifika•45m ago•3 comments

Ask HN: How do you keep code review skills when agents write most of the code?

1•robinmin•45m ago•0 comments

Re: Riemann

https://borretti.me/article/re-riemann
18•_dain_•45m ago•2 comments

Petrucci Music Library

https://imslp.org
1•yetanotheruser•52m ago•0 comments

Help github just deleted me

https://nate.mecca1.net/posts/2026-11-20_help/
44•01nate•52m ago•21 comments

AI models change their answers when they are monitored

https://www.jordannews.jo/Section-129/Technology/AI-models-change-their-answers-when-they-are-mon...
2•nreece•54m ago•0 comments

Show HN: SaturnSQL Context, telling AI tools what the database means

https://saturnsql.com/context-layer
2•infr88•56m ago•0 comments

Real-Time Video on Embedded Linux Cameras with WebRTC

https://interrupt.memfault.com/blog/real-time-video-webrtc
2•hasheddan•56m ago•0 comments

Uncontacted Indigenous people emerge from Amazon forest to ask for food

https://www.washingtonpost.com/world/2026/11/19/uncontacted-indigenous-people-emerge-amazon-fores...
14•Teever•57m ago•0 comments

A human liver has been kept alive outside the body for a record seven weeks

https://www.technologyreview.com/2026/11/19/1148934/a-human-liver-has-been-kept-alive-outside-the...
10•bookofjoe•58m ago•1 comments

Officials approved the sale of 580k Nvidia chips to Chinese companies

https://www.washingtonpost.com/technology/2026/11/20/officials-approved-sale-580000-nvidia-chips-...
7•cdrnsf•58m ago•3 comments

Serious cyberattack thought backed by wealthy operators

https://www.ruv.is/english/2026-11-20-serious-cyberattack-thought-backed-by-wealthy-operators-493411
4•Bender•59m ago•1 comments

White House removes cyber-security chief after series of tech outages

https://www.bbc.com/news/articles/cwz0k3nn5p5mo
4•Lyngbakr•1h ago•0 comments

How to Be a 10x Engineer in 2027 and Beyond

https://serce.me/posts/2026-11-19-how-to-become-a-10x-engineer-in-2027-and-beyond
2•SerCe•1h ago•0 comments

ICE details Princeton neuroscientist claiming asylum

https://www.theguardian.com/us-news/2026/nov/20/princeton-doctoral-student-reportedly-detained-ice
7•angry_octet•1h ago•2 comments
Open in hackernews

Ask HN: Why is web auth not a solved issue?

2•zwnow•1y ago
Personally, every project I start, I quit due to not being comfortable with the auth implementation.

I've been into web development for 4 years now. During my research regarding auth in this timeframe, I have found a million reasons on why I should not roll it myself. The reason is always it being to difficult to implement, too much responsibility and basically no matter how I'd do it, it would be unsafe.

The general consensus among web developers seems to be to just let a third party do it. And I understand the reasoning, they are experts and have decades of experience on that specific thing. It makes sense as long as you're fine with third party service dependencies for your application. However, I don't want that. I do not feel comfortable submitting my users data to tech giants for obvious reasons.

I am wondering why it's so difficult to implement secure auth? Why can frameworks like Laravel or Phoenix just generate auth solutions? Why should I trust them, if everyone is saying I shouldn't roll it myself?

After all, if Laravels or Phoenix generated auth isn't safe, I am the one taking responsibility anyway, no?

To my understanding web auth has been an issue for decades now, why aren't there protocols in place to solve it? Or if they are, why aren't they talked about a lot?

Considering how often I read about auth breaches with the big players in the game (Firebase as an example) I am not comfortable trusting third parties with that task either.

So how is one supposed to do it? There are so many JWT tutorials on youtube, but apparently JWTs aren't safe either. Then there are session cookies, which also aren't safe? Why is that?

I am also not talking about authorization. I specifically mean authentication. If I wanted a micro blog platform where users can log into their accounts and write about stuff, how would I make sure it's secure without having to trust third parties, especially big tech companies who repeatedly prove they cant be trusted over and over again?

Comments

arrowsmith•1y ago
> if Laravels or Phoenix generated auth isn't safe

What makes you think they're not safe? Zillions of successful apps have been built using Laravel and Phoenix and (afaik) no-one has hacked their auth code yet. The code is open-source for anyone to inspect for vulnerabilities. I wouldn't feel unsafe using them.

You seem to misunderstand what it means to "roll your own auth".

"Don't roll your own auth" doesn't mean "use a third-party auth provider". It means "use an existing, expert-made auth solution and don't try to write it yourself."

That can be a third-party provider like Firebase, it can be a code dependency like Rails's Devise, it can be generated by `phx.gen.auth` in Phoenix, it doesn't matter - the point is that you're using a tried-and-tested auth solution written by someone who knows what they're doing.

Writing your own auth code is generally a bad idea because it's complicated, time-consuming and easy to get wrong. But there are zillions of off-the-shelf solutions you can use that have been created by security experts and battle-tested in thousands of production apps. As far as I'm concerned, web auth is a solved problem.

zwnow•1y ago
Interesting. When I generate auth for Phoenix the API endpoints are not piped through any security pipes. Only the browser endpoints. Why wouldn't I secure my API endpoints? The same kind of requests that are made for browser requests are sent to the API routes, so this is really confusing.
arrowsmith•1y ago
Ah yes. `phx.gen.auth` generates a cookie-based auth system, which is fine for the :browser pipeline but it's not generally what you want for a JSON API.

The Phoenix docs include a suggestion for how you can extend `phx.gen.auth` to add token-based authentication to your API: https://hexdocs.pm/phoenix/api_authentication.html

(No, this isn't "rolling your own auth" either, it's using someone else's pre-written auth code.)

johncoltrane•1y ago
> The general consensus among web developers seems to be to just let a third party do it.

Outside of personal projects, third-party auth providers must be audited (think GDPR or PIPL), budget must be allowed, contracts signed, etc. so web developers rarely, if ever, have their say on the matter. The decision is taken long before anyone wrote a single line of code. From a project management perspective, it's an easy trade-off to make: one sprint for integrating Okta versus who knows how many for badly implementing something that requires a level of expertise that no one on the team has reached.

For personal projects, the trade-off is a bit different. Resources are scarce so, even if implementing auth is actually not very complicated(1) and can even be quite fun, there are probably more immediately interesting things to do. So you integrate a third-party solution in a wednesday night and you move on.

[1] https://thecopenhagenbook.com/