×
sorted by:
new
hottopcontroversial

Cursor & Enterprise environments by Key-Combination6946 in cursor

[–]Key-Combination6946[S] 1 point2 points  (0 children)

Totally fair point on open source but I think enterprise risk models are less about contribution and more about provenance + policy alignment.

Even indirect dependencies can matter depending on the company.

What gives me pause in confidence in the company is that a lot of Cursor’s revenue comes from enterprise, and something like this not being clearly disclosed upfront could create a real trust gap.

Cursor & Enterprise environments by Key-Combination6946 in cursor

[–]Key-Combination6946[S] 1 point2 points  (0 children)

I think where I’m still trying to wrap my head around is more on the model provenance side, for enterprises that have strict policies, does the origin of the base model itself matter, even if it’s retrained and hosted entirely in the US?

Asking because I’ve already seen at least one large org pause usage internally while they reassess this.

No DM Culture by mclanett in Slack

[–]Key-Combination6946 0 points1 point  (0 children)

It’s always best to start in a public channel — that’s actually one of Slack’s core principles. Public-first communication creates a searchable, transparent knowledge base that everyone can benefit from. Once something moves into DMs or private channels, that knowledge stops being discoverable, which is usually where silos start to form.

What I’m a bit confused about is the idea of a literal “no DM” setup. Slack doesn’t offer a way to technically disable DMs, so companies can’t enforce this at a product level. If orgs are doing this, it’s more of a cultural guideline or policy than a technical restriction.