tg3

7 ms·

1.
Please take our programming assessment with an LLM(creatingvalue.substack.com)
15 points by tg3 2y ago|0 comments
2.
The Guide to building Sync-friendly APIs(xkit.co)
7 points by tg3 4y ago|4 comments
3.
by tg3 5y ago
Xkit | Senior UX Engineer | REMOTE | https://xkit.co Software is eating the world, and that software is going to be connected together. Xkit is helping bring that future to fruition by building tools that make it easier for deve
4.
Xkit (YC S18) Is Hiring a Senior UX Engineer(github.com)
1 points by tg3 5y ago
5.
by tg3 5y ago
Xkit | Senior UX Engineer | REMOTE | Full-Time | https://xkit.co Xkit lets developers add direct, native, embedded integrations to their SaaS app as easily as building a Zapier app. With one straightforward integration to Xkit,
6.
by tg3 5y ago
SEEKING FREELANCER | 100% Remote (one weekly meeting at 11:30am PT) Looking for a Senior React/Typescript Engineer to help build out a new project at https://xkit.co (YC S18). We build developer tools to make it easier to a
7.
by tg3 6y ago
The specific framing of founders buying capital (dollars) is super helpful in understanding VC behavior, which is nearly are marketing. VC’s sell a commodity product, money. In order to sell it, they add marketing, branding, and freebies -
8.
by tg3 6y ago
Great read. Two days I wrote about my own experience learning Elixir to build Xkit[1]. As I wrote there, the language guide is one of the best I've ever seen and is pretty much all you need to get started. There are drawbacks of course
9.
How I learned a language and launched a product in 60 days(xkit.co)
3 points by tg3 6y ago|0 comments
10.
by tg3 6y ago
I'm planning to build something like this with Next.js / Vercel. All of the changes will be managed via GitHub Pull Requests (so no need for any other authentication) with automatic deployment on Vercel.
11.
by tg3 6y ago
> I really wanted to like OAuth but implementing it is a nightmare! Not only is the spec itself challenging, it leaves enough ambiguity and rough edges that most providers end up extending it some way that makes it hard to standardize. M
12.
by tg3 6y ago
Thanks for the note on the typo, I've fixed it. I'm happy to add other auth providers to our docs. Shoot me a note (trey@) with the instructions and I'll add it in. Many developers want to have their integration catalog match
13.
by tg3 6y ago
Thanks for the kind words. I agree we need to re-think our home page a bit. We initially focused on "OAuth" to really get specific about what we do, but it's had the unfortunate side effect of making us seem like an auth prov
14.
by tg3 6y ago
We have a Developer plan that's free up to 10 users. Our Startup tier ($50/month) is intended for early stage projects without significant funding. If you have a project that can't afford our Startup tier for some reason, sho
15.
by tg3 6y ago
That's good feedback. We'll have to examine the native use-case a little more closely.
16.
by tg3 6y ago
You can create an account and set everything up without ever talking to us if you prefer (that's the "Create a free account" link above the fold, https://app.xkit.co/sign-up ).
17.
by tg3 6y ago
Shoot me an email for more details on the SOC2 (trey@). We're unlikely to support private cloud in the near term.
18.
by tg3 6y ago
We have docs for it here: https://docs.xkit.co/docs/auth0-authentication You can create a separate token specifically for Xkit or re-use an existing one.
19.
by tg3 6y ago
We've had a handful of requests for native app support, so it's definitely something we'd like to do eventually, although we're more likely to start with Electron since it will be easier to port from our existing SDK. Th
20.
by tg3 6y ago
Hmm, there is an unfortunate resemblance there. Thanks for the feedback.
21.
by tg3 6y ago
That's great! We support Intercom, Salesforce is coming soon, and I can look into adding Calendly too. Re: staying motivated. I was always a solo founder. I think for me it starts with experience. I co-founded a startup when I was just
22.
by tg3 6y ago
Xkit acts purely as an agent for our customers, we don't make use of the access granted ourselves (and as mentioned in another comment, we're happy to sign contracts to that effect). As a result, the consent screen and what users
23.
by tg3 6y ago
Thanks! a) Yes, I'm testing our Salesforce integration this week b) While we don't have documentation for it yet, we support migration both in and out by loading and reading the current tokens for all of your users. That's go
24.
by tg3 6y ago
We don't exactly compete with Auth0. Their focus is on how you authenticate users, where we're trying to make it easy to add integrations to extend your product with data or functionality from other products. There is some signifi
25.
by tg3 6y ago
Yes, we absolutely sign contracts.
26.
by tg3 6y ago
The access log is a great idea, we'll build that.
27.
by tg3 6y ago
Yeah, Xkit is unfortunately also the name of a defunct Tumblr extension. We thought it was worth the (minor) collision. Our github is https://github.com/xkit-co
28.
by tg3 6y ago
That's an understandable position to take - these are sensitive pieces of information that provide a high degree of access. We take the security side of this equation very seriously. All the tokens and credentials are encrypted (both a
29.
by tg3 6y ago
Yes, the integration catalog experience for a logged in user would be very similar to the My Apps screen in Zapier. (by default the styling is a bit different, but you can customize that e.g. if you prefer the list vs grid view)
30.
Launch HN: Xkit (YC S18) – OAuth infrastructure as a service
138 points by tg3 6y ago|54 comments

More ›