Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Show HN: Base – API for authentication, email sending, images and more

base-api.io

Post reply on HN
Print view View original

41–50 of 56 posts

Re: Show HN: Base – API for authentication, email sending, images and more

#41

Post by growt »

andwaal wrote: post #19
gdotdesign wrote: post #2

I released Base about a month ago and created a blog post with some details https://dev.to/gdotdesign/base-api-for-authentication-email-... Let me know what you think! :)

Hi, could you explain this section from your TOS? "You will provide us the right to reproduce, modify or create derivative works from your Content. Obviously we won’t be modifying your Content, we need these rights for example to be able to share your designs with other users. You will also provide us a right to publicly perform or display your Content to allow us to display the material on other users’ monitors. Bas…

That's almost a standard disclaimer by now. If this API let's you upload an image and by request (of yourself or a user) it returns a resized version of that image, that might already be a derivative work and distribution of that content.

Re: Show HN: Base – API for authentication, email sending, images and more

#42

Post by swyx »

algodaily wrote: post #34
Scarbutt wrote: post #32

Earlier quoted context omitted.

Not Crystal related but from where do you get the art? ;)

Not OP but google around for vector-style images. There was even a Show HN project that generated them, I'll look around

i'd appreciate a link, i did a basic search on those keywords but didnt find anything matching.

Re: Show HN: Base – API for authentication, email sending, images and more

#43

Post by matdehaast »

swyx wrote: post #42
algodaily wrote: post #34

Earlier quoted context omitted.

Not OP but google around for vector-style images. There was even a Show HN project that generated them, I'll look around

i'd appreciate a link, i did a basic search on those keywords but didnt find anything matching.

https://undraw.co/ https://www.humaaans.com/

Re: Show HN: Base – API for authentication, email sending, images and more

#44

Post by ttul »

theseanstewart wrote: post #16

I would reconsider the "Unlimited Emails" offering for the "Ultimate" $100/mo plan. Assuming you're using SES, a customer sending 1,065,000 emails would cost ~$100. All it takes is one person to abuse it before it's costing you big money. On the surface, "Unlimited" sounds great, but your target market is developers that know the cost of sending emails. This may result in the opposite effect as it signals your model…

The even greater problem with sending email is that your platform will immediately and comprehensively be abused by spammers.

To make your email woes go away, I would recommend using MailChannels [1] rather than SES or SendGrid because MailChannels has a built-in anti-abuse layer that will send you a webhook whenever a bad user is detected. SES will just terminate your account, which probably isn't what you want. Also, at high volume, MailChannels costs less.

[1] Disclosure: MailChannels is my company.

Re: Show HN: Base – API for authentication, email sending, images and more

#45

Post by jaequery »

statictype wrote: post #30
jaequery wrote: post #28

It’s the beginning of an Api-as-a service trend.

Isn’t that what AWS started more than 10 years ago?

I was thinking more in terms of a full-fledged API SaaS platform that have business logic and data-schemas/storage.

It comes w/ an admin and you just pick and choose what you need, for example:

/users /posts /products /orders /login /emails etc ...

It'd be neat to see a community-driven marketplace to boot, for all types of solutions.

Perfect for SPAs and JAMstacks.

Re: Show HN: Base – API for authentication, email sending, images and more

#46

Post by Blackstone4 »

FrancoisBosun wrote: post #11
gdotdesign wrote: post #2

I released Base about a month ago and created a blog post with some details https://dev.to/gdotdesign/base-api-for-authentication-email-... Let me know what you think! :)

Looks nice. I’m uncomfortable pushing the password in plaintext to an unknown entity. I can always bcrypt the password locally before sending it through the API, but it would be great to see examples of this, to prevent deva from pushing secrets outside their zone of control. Otherwise, I can see myself using this in some side-projects. Good work!

When I login/signup to a website, I'm always sending my password in plaintext to the server (obv. encrypted via TLS). What's the difference?

Re: Show HN: Base – API for authentication, email sending, images and more

#47

Post by [deleted] »

jaequery wrote: post #45
statictype wrote: post #30

Earlier quoted context omitted.

Isn’t that what AWS started more than 10 years ago?

I was thinking more in terms of a full-fledged API SaaS platform that have business logic and data-schemas/storage. It comes w/ an admin and you just pick and choose what you need, for example: /users /posts /products /orders /login /emails etc ... It'd be neat to see a community-driven marketplace to boot, for all types of solutions. Perfect for SPAs and JAMstacks.

[deleted]

Re: Show HN: Base – API for authentication, email sending, images and more

#48

Post by FrancoisBosun »

Blackstone4 wrote: post #46
FrancoisBosun wrote: post #11

Earlier quoted context omitted.

Looks nice. I’m uncomfortable pushing the password in plaintext to an unknown entity. I can always bcrypt the password locally before sending it through the API, but it would be great to see examples of this, to prevent deva from pushing secrets outside their zone of control. Otherwise, I can see myself using this in some side-projects. Good work!

When I login/signup to a website, I'm always sending my password in plaintext to the server (obv. encrypted via TLS). What's the difference?

The difference is my customer's don't have a first-party relationship with the data store that holds their password.

    browser -> www.example.com

    browser -> www.example.com -> Base
That's the biggest problem I see with this approach. The password will be seen by two parties instead of just one.
Post reply on HN