News for hackers. Stuff that matters.

ucarion

Not yet, but we're thinking about it!
These are all great points!

1. Definitely want to improve favicons. For deriving fields, we do have formula fields. Would love to show that to you, it's not obvious enough how to use to enable for this HN launch.

2/3. Sorry about that. This username/password approach for the HN launch is definitely a hack.

4. Right now, search is just on the current type of record you're looking at. I want to fix this, and I just haven't because I haven't made the UI for filtering what objects to search across. The backend is in place though. Glad it seems suspiciously fast! I can assure it's a real FTS talking to a database.

5. I want to fix this too. A way to make data of type "Link" for better UI treatment.

6. Archiving is meant for data that others shouldn't be looking at -- it's a staging ground for data. That's why you can't point into archived data. It's also a precursor for deleting data, and we want to guarantee no dangling references to deleted data.

7. Will fix this.

So far, we've been doing setup on behalf of customers precisely because it's the easiest option for our customers.

We're open to exploring self-serve, but realistically that's going to be really hard to get right. I'm imagining we may have templates that customers can choose from down the line, where they can one-click setup a CRM for their kind of business.

Should be healthy again, sorry!
Yup, that's a good catch. Fix going out now.
You should check out https://www.stacksync.cloud/ (YC W24) -- they do a bidi realtime sync between CRMs and databases. Not sure if that scratches your itch!

We are definitely looking to make our API public. We've built our core data model in such a way that business users can't accidentally break API users by, for example, making backwards-incompatible changes to their objects. It baffles me that everyone else in the space gets this wrong. But still, I want to feel really good about making an API that can stick around a long time before telling people to use it to run their business, and we're just not there yet.

You should check out Twenty! https://twenty.com/ (YC S23) -- they're an OSS CRM.

I totally agree the object management UI is too clunky right now. I want to redo that set of pages, they were the first ones we shipped. Not gonna lie, idk if anyone except me and Ned are really pining to learn hotkeys for managing object schemas, since in practice we're the only ones doing that on a regular basis -- we do initial setup on behalf of our customers.

Yeah, I consider latency part of UX. We're doing some somewhat fancy stuff to reliably replicate every record into a couple of stores, each of which is optimized for different access patterns (search, get latest by ID, etc.). The big central Postgres(TM) is mostly there to be authoritative and to transactionally maintain invariants in the system.

Working on the account lock, sorry. Password stuffing alarm is tripped. EDIT: in the meantime, a jank workaround. Just added a few more users:

[email protected]

[email protected]

[email protected]

All have the same password as in the original post: sk9ueEAfhXP9j4cuxLCVmw7. (include the trailing period)

We rely on GMail or Outlook's spam and checks. We only sync emails that made it to your non-spam inbox.

Totally agree we're way too barebones to say we're an SFDC alternative today. Reports and dashboards/views are the next two things on the roadmap. For workflows we've been using our Zapier app so far, but we're looking to potentially do that built-in. Integrations is going to be a long list of work. Going to feel like working at Segment again. :)

For sourcing and campaigns, our initial plan is a two-way Apollo integration. Not sure if you have thoughts on the necessity of doing everything in-house (the Hubspot approach) or just focusing on integrating with the best tools (the Salesforce approach).

Your feedback on the website is well taken. We've got a lot of work to do there.

Right now our email sync is maximally simple, so that it's predictable for customers. If anyone on a thread has the sync set up, then any thread with outside parties gets synced. Each outside company/person is associated with the email. Also no BCC stuff, too easy to forget.

We're working on a simple way to do deal->email association. Right now you can only do deal->company->email, so if you have concurrent deals on a company there's not a great way to disentangle them.

You got thoughts on how you'd want that to work?

An Outlook/Excel add-in is a great idea. Something that lets you peek at CRM data related to a person/company, you mean?

We support syncing Outlook email/contacts into Okapi. Definitely agree that outside of tech, Microsoft's stack is predominant.

The plan for winning is: slowly at first, then suddenly. We'll start with smaller businesses transitioning between CRMs, and grow with them. Number one goal is to never give customers a reason to churn.
Attio is great. I think it's among the best new entrants.

So far, the main difference is that Okapi can be even simpler than Attio if you'd like it to be. There are no mandatory built-in objects, and no enrichments/automations/etc that you can't disable. You can KISS your sales process as much as you like.

To that end, we've also been eschewing self-service onboarding. We just set up customer's CRMs and import their data for them, shooting for the simplest setup they can get away with. The software is generic, and we make it concrete for customers by hand.

Thanks!

Launch HN: Okapi (YC W24) – A new, flexible CRM with good UX

Hi HN!We’re Ulysse and Ned from Okapi. We’re making a modern CRM. It's kind of like if Airtable/Notion built Salesforce today. https://okapicrm.comWhen I was fresh out of college, working for startups, Salesforce was this big mystery to me. It's the perpetual second screen for everyone in sales. They were building this gigantic obelisk downtown. What was this thing? And why did every...

( Read More... | 103 comments | 26 points | on HN )
Re:Swiss Maps Are Full of Hidden Secrets on Tuesday February 27, 2024 @12:07PM (#39526508)
The "spider" on the Eiger might be a reference to the feature of the same name on the Eiger's north face?

https://upload.wikimedia.org/wikipedia/commons/e/e8/Eiger_no...

Re:RFC 9512: YAML Media Type on Wednesday February 21, 2024 @12:02PM (#39456371)
Roberto Polli and Erik Wilde are frequent IETF contributors. I'm not following their work much these days, but I don't think they have a specific interest here. They're active in httpapi, the working group that produced this RFC. Having worked a bit with both, they're great and thoughtful folks.

Eemeli Aro maintains the 'yaml' npm package. Seems like a good person to have aboard make sure things stay practical.

It doesn't appear to be linked to in the article, but I believe these are the docs for Claude 2.1:

https://docs.anthropic.com/claude/docs/claude-2p1-guide

> According to the declassified FISC ruling, despite paper reforms which the FBI has touted that it put into place to respond to the last time it was caught violating U.S. law, the Bureau conducted four queries for the communications of a state senator and a U.S. senator.

Ironically, it seems that a significant chunk of the progress FBI has made in terms of 702 compliance comes from a pretty trivial "paper reform": changing the default in their search portal to have 702 be defaulted to "off".

> In June 2021, the FBI changed the default settings in the systems where it stores unminimized Section 702 information so that FBI personnel with access to unminimized FISA Section 702 information need to affirmatively “opt-in” to querying such information. This system change was designed to address the large number of inadvertent queries of unminimized Section 702 information DOJ had identified in its reviews, in which FBI personnel did not realize their queries would run against such collection. Historically, users were automatically opted-in to querying unminimized Section 702 information in these databases if they had been authorized to access unminimized Section 702 information.

https://www.justice.gov/d9/pages/attachments/2023/03/03/rece...

Josh Geltzer (a deputy DHS advisor) said on Lawfare that this probably alone dramatically reduces the number of noncompliant FBI 702 searches:

https://www.lawfaremedia.org/article/the-lawfare-podcast-jos...

Article from Le Monde:

https://www.lemonde.fr/pixels/article/2023/07/06/le-senat-vo...

https://archive.li/krUfW

> To prevent multiple attempts at scams by e-mail or SMS, the bill must also allow the establishment of a free "anti-scam filter" sending a warning message to anyone who is about to to go to a site identified as malicious.

> And another fun fact (We had a lot of fun!): Time Zones often have a "friendly name" in the format Continent/City|Island except for UTC and... GMT+12, which only covers two uninhabited American islands :D

There's quite a few other non-slash-having names out there:

    ls -pL /usr/share/zoneinfo | grep -v '/'
"Eire" is in there, for instance, to deal with software that assumes that the "is_dst" half of the year is during the (northern) summer, but Ireland technically does it the other way around -- a distinction relevant only to computers.

https://github.com/eggert/tz/blob/c3e966c59b02b1f47f0b7b0e4a...

The only other timezone that currently has a non-1h offset for DST -- Ireland's is -1 hours -- is Australia/Lord_Howe, which has a 30-min positive leap.

Edit: there are also tzdb entries of the form "a/b/c" -- America/Kentucky/Louisville --- though they are not commonly used in practice.

Wishing y'all the best of luck. This would be huge for a lot of folks.
https://www.wsj.com/articles/twitter-missed-dozens-of-known-...

> The appearance of the images on Twitter was striking because they had been previously flagged as child sexual abuse material, or CSAM, and were part of databases companies can use to screen content posted to their platforms, the researchers said. “This is one of the most basic things you can do to prevent CSAM online, and it did not seem to be working,” Thiel said.

Re:The seven programming ur-languages (2021) on Thursday May 04, 2023 @04:25PM (#35821578)
The tooling thing goes both ways. I remember classmates struggling with homework because they were trying to use a different flavor of SQL than the SQLite we ran for class. This stuff is obvious to engineers, but very confusing to someone whose first hello-world was 8 weeks ago.
Re:The seven programming ur-languages (2021) on Thursday May 04, 2023 @12:17PM (#35817860)
To your point, Berkeley's intro-level CS class, CS61A, used to use teach Prolog as an example of logic programming. They use SQL now instead.

I can't really attest to whether that's a better choice for learning logic programming, though. It's easier to "run programs" in Prolog. SQL wants to be a cog in a machine where Prolog is more freestanding.

Re:The Vowel Space on Tuesday April 25, 2023 @05:46PM (#35707143)
Re:HTTP Response Header Field: Carbon-Emissions-Scope-2 on Tuesday April 11, 2023 @04:29PM (#35531083)
There is some ongoing discussion on this document in httpbis:

https://lists.w3.org/Archives/Public/ietf-http-wg/2023AprJun...

Some influential folks appear interested. I'm not sure I see the point, but that's just me.

Re:Glamorize Your Problem Domain on Monday March 27, 2023 @11:58AM (#35328323)
There are useful mental analogies between pedestrian line-of-business CRUD apps and a compilers. I don't disagree with that thesis at all. But I have seen it taken too far. Many engineers abstract and generalize business requirements until they find them interesting, and then implement against those requirements.

Programming languages are typically designed to be relatively simple and easy to compile. Line-of-business software tends to be as complicated and arbitrary as the organization requires. Trying too hard to make your mundane app into a compiler can push the software in a direction that makes it difficult to change in the messy ways you'll need to later on.

Note, for instance, that the author worked on a system that generates SDKs in multiple languages. This is pretty obviously a sort of compiler. Are your requirements really so fancy? Or are you making a CRUD app hooked up to a couple external integration APIs?

It's useful to see the analogies between one's domain and compilers, but see if you can't keep that analogy in your head and out of the code whenever possible.

Re:Hypermedia Clients on Wednesday February 01, 2023 @07:12PM (#34620172)
REST as understood by Fielding is useful when you have a highly heterogeneous, connected set of things your clients and servers operate on, like websites or a government intelligence system.

These sorts of domains are pretty uncommon. It's far more than just an extra layer of indirection to keep backwards compatibility; in practice, you can't change HTTP-layer APIs regardless of your hypermedia controls. People bookmark things and write curl scripts.

Older »