sbauch

6 ms·

1.
by sbauch 5y ago
Before you dismiss CryptOrchids as not technically interesting, please believe that’s how I feel about most projects in the NFT space, and I set out to create something unique, clever and only possible because of blockchain technology. NFTs
2.
Show HN: CryptOrchids – an Ethereum based game to keep finicky flower NFTs alive(cryptorchids.io)
2 points by sbauch 5y ago|1 comments
3.
CryptOrchids: The NFT That Dies If You Don’t Water Them(thenifty.com)
3 points by sbauch 5y ago|0 comments
4.
SSO for Serious Startups(mtruyens.medium.com)
2 points by sbauch 6y ago|0 comments
5.
by sbauch 6y ago
I don't think I've changed the meaning unilaterally, others here seem to agree that the meaning is evolving. I can concede that we are guilty of wanting the wave of goodwill, but I have a hard time agreeing that this is a bait and
6.
by sbauch 6y ago
Perhaps. Let's use plain English as neither of us are lawyers. Allowed: Deploy your own Osso instance and use it in applications you own and operate. Not allowed: You use Osso to start a business where your primary business is in helpi
7.
by sbauch 6y ago
Fair enough. I stand by our interpretation of the current license though - the usage you describe is fair use, but let us know if your attorney disagrees as we'd definitely want to fix that.
8.
by sbauch 6y ago
thanks!! we're running out of names for startups and people! hope we can peacefully co-exist. Spanish for bear and Portuguese for bone! fun :)
9.
by sbauch 6y ago
The other industries you mention have gone through similar changes though haven't they? Not long ago, "idiot", "imbecile" and "moron" were all terms with strict definitions in the field of medicine. Langua
10.
by sbauch 6y ago
merged! the beauty of open source, er... source available software ;)
11.
by sbauch 6y ago
As I've mentioned or alluded to in other comments, I think "open source" as you describe it is broken and unsustainable, and we're happy to have a constructive conversation about commercially viable open source. But if w
12.
by sbauch 6y ago
I didn't mean for you to take my comment as a guarantee, but if you're more than curious I'd have your counsel read the license, as we are under the impression the use you describe is well within the rights granted by the cur
13.
by sbauch 6y ago
I don't think we've intentionally made false statements nor committed any fraud. But we appreciate the feedback, we'll review as a team and see what sort of decision we can make that will maintain source availability without
14.
by sbauch 6y ago
Thanks, we'll review this and other folks' comments and see if we can make a change that works for us and maintains an OSS ethos. This is our first launch FWIW, we're appreciative of the feedback but clearly seemed to have ru
15.
by sbauch 6y ago
We don't have definite plans to build a full-featured IDP, but we did build a Mock IDP we use in CI, QA and demos that could possibly be a starting point for your purposes? Other OSS IDPs include Keycloak and Gluu Server if you wanted
16.
by sbauch 6y ago
So the intent of the license is to prevent copy-cats from using Osso's source to run a competing business. We certainly intend for you to be able to authenticate external customers in a SAAS app. IANAL but the license text hsa been vet
17.
by sbauch 6y ago
You are absolutely free to use Osso's source to onboard and authenticate your own customers without paying us! The goal of the license is to prevent someone from creating their own SAAS offering that competes with ours. Using Osso for
18.
by sbauch 6y ago
Frankly we're using existing open source to handle this - we use ruby-saml which is maintained by OneLogin for the SAML parsing, but we also wrote a little ts parser for federated metadata files - https://github.com/ent
19.
by sbauch 6y ago
Thanks so much! We're super confident in the 6 IDPs we've built first class support for. But we also know that there are sure to be edge cases we haven't totally caught, we're still a bit early. But at least we can catch
20.
by sbauch 6y ago
Thanks so much for the kind words! The pricing here is definitely more applicable to Auth0 :) But for us, charging per user makes predicting the cost of your SAML provider difficult, and everyone seems to do this. We charge per customer acc
21.
by sbauch 6y ago
Certainly a fair critique, and one we can admit we saw coming. We currently use the BSL license, created by MariaDB and used by companies like Sentry. We do think Osso is open source by common understanding and view the BSL as a fair model
22.
SAML on Rails: How to Implement SAML SSO in Rails 6(ossoapp.com)
3 points by sbauch 6y ago|0 comments
23.
by sbauch 6y ago
Thanks so much! A useful framework for thinking about SAML vs OAuth from an engineer's perspective is to think of OAuth as class based, while SAML is instance based. When you set up a new OAuth provider such as Github you typically gra
24.
by sbauch 6y ago
Hey HN! We're Sam, Sam, and Michael, the founders of Osso ( https://ossoapp.com/ ) Osso is open-source software for integrating SAML SSO with any web application. It provides an Admin UI to onboard your customers, genera
25.
Show HN: Osso – Open-source SAML SSO service(github.com)
41 points by sbauch 6y ago|56 comments
26.
Implement SAML SSO in a Rails App(ossoapp.com)
3 points by sbauch 6y ago|0 comments
27.
All About Identity Providers: The ABCs of IDPs(ossoapp.com)
3 points by sbauch 6y ago|0 comments
28.
by sbauch 11y ago
https://vcardme.com My current side project is Vcardme. It's a service for hosting your contact information at a URL where it can be accessed or saved. Idea being you should put your Vcardme URL in your email sig. For me, w
29.
Show HN: Bar Recommendations by Text(textrecs.com)
1 points by sbauch 11y ago|0 comments
30.
A Twitter Ads Hack to Get a Twitter Interview(medium.com)
2 points by sbauch 12y ago|0 comments

More ›