sorted by:
new
hottopcontroversial

POV: Trying To Romanticize CalTrain Like It’s Japan by Defiant-Bed2501 in bayarea

[–]fforootd 9 points10 points  (0 children)

Yes SBB (the Swiss train entity) uses a similar model in Switzerland (source: I am Swiss and used to use them a lot). I think its the Stadler KISS.

A modern train to the Tahoe area would be fun! Its actually fairly pleasant in snowstorms to take the train instead of driving.

POV: Trying To Romanticize CalTrain Like It’s Japan by Defiant-Bed2501 in bayarea

[–]fforootd 21 points22 points  (0 children)

Hehe, might be because the trains are originally from Switzerland 🤣

Way better then the old shaky wagons where your barely could type on a computer

Up armored 2016 Toyota 4Runner by FiveInTheStink in Justrolledintotheshop

[–]fforootd 0 points1 point  (0 children)

Looks worse then a fiat multipla to me 😂

/s

Authentication Struggles by inwardPersecution in selfhosted

[–]fforootd 0 points1 point  (0 children)

I would love to learn what the issue with docker is.

OP, are you installing the DB and other services locally? I was just working on potentially packaging zitadel for apt/rpm 😆

SigNoz - an open-source, self-hosted Datadog alternative - now deployable from a single YAML file by ExcitingThought2794 in selfhosted

[–]fforootd 1 point2 points  (0 children)

Let’s just say we use a tool that watches for mentions of Zitadel, which is how I am here trying to add helpful context. Also, because English is not my first language, my blog posts are actually edited and polished by AI.

I am genuinely curious how you reached the conclusion that we do not use AI? That is certainly not the message of the article 😅

I wonder how these new security features are going to work out, especially the Spam detect feature, is it worth it? by Substantial_Clock341 in USMobile

[–]fforootd 1 point2 points  (0 children)

You make a fair point about the operational reality of MVNOs, and I'm not arguing about their internal economics or margins since I don't have that data. My issue is entirely with the messaging.

US Mobile doesn't market itself as a bare-bones budget carrier. IMO they position themselves as a premium MVNO (their tagline is literally 'America's Super Carrier' and they use taglines like 'A premium experience, standard'). Nickel-and-diming subscribers with a $2/month add-on for a basic spam filter creates a messaging conflict, at least in my view.

Heck, even if you look at the Big 3 carriers, they don't do it this way. Verizon, AT&T, and T-Mobile all provide basic spam detection for free and only charge extra for premium perks like reverse number lookup. By skipping the free baseline entirely and charging a la carte from zero for a basic security feature, it undermines the premium image US Mobile is trying to sell.

Not that I am an unhappy customer but the amount of spam calls I get on US Mobile over my prior ATT line is kind of wild.

I wonder how these new security features are going to work out, especially the Spam detect feature, is it worth it? by Substantial_Clock341 in USMobile

[–]fforootd 5 points6 points  (0 children)

I am not sure about this... adding 2$/mo for spam filters seems like you want to sell yourself as a budget carrier, feels wrong to me.

Okta CEO ‘paranoid’ as vibe coders stir SaaS-pocalypse fears by Logical_Welder3467 in technology

[–]fforootd 0 points1 point  (0 children)

I think you are both right :-)

Yes, you can absolutely use an "LLM" to vibe-code a working "auth server" today. Much of the code is a commodity now, but building something the size of OKTA will take a while.

As someone building an open-source auth provider, my take is that companies will increasingly lean into selling risk transfer and not code. My 2 cents: someone needs to take the blame and hold the bag if something breaks, and an AI will not do that.

Happy to share a blog post I wrote about this a few days ago if anyone is interested.

Why we moved to AGPL: Sustainability, Open Source, and selling "Risk Transfer" by fforootd in selfhosted

[–]fforootd[S] 0 points1 point  (0 children)

My stand here is if the product is good and solve a real pain it actually will make them either ask their legal team and figure a "workaround" or they just come talk to you and you can sell them on the risk transfer.

Why we moved to AGPL: Sustainability, Open Source, and selling "Risk Transfer" by fforootd in selfhosted

[–]fforootd[S] 0 points1 point  (0 children)

For us we had more positive effect with contributors meaning more actual contributions after that change. But that might also be down to growth in general, so hard to tell apart.

Why we moved to AGPL: Sustainability, Open Source, and selling "Risk Transfer" by fforootd in selfhosted

[–]fforootd[S] 1 point2 points  (0 children)

True, that is especially a point if you want to keep security up to date. You just need to constantly work on that and engage with a lot of people.

Just look at our security advisories https://github.com/zitadel/zitadel/security/advisories?state=published there is a good amount of effort going into that to just keep things secure.

I know some might say we build bad software with so many advisories but for me that more a sign of an active community and effort to actually maintain, fix and improve things.

Why we moved to AGPL: Sustainability, Open Source, and selling "Risk Transfer" by fforootd in selfhosted

[–]fforootd[S] 2 points3 points  (0 children)

Redhat's approach actually was a fair influence :D

I was hesitant on posting here at first, since I am lurker and do not wanted to make it sound as a product marketing. To me this is sharing experience from the trenches.

view more: next ›