adamkaz

Coming to Next.js from Laravel, being able to hand things off to a long running worker is one of the things I missed the most. We're currently handling this with a non-ideal solution and will definitely check Trigger.dev out when you launch that feature.

Ah thanks! In the middle of publishing that integration :-) We'll get that fixed.

As far as the fonts - font support across email clients is.... not great. We offer it but warn our users that their chosen font might not be displayed in most cases.

Ideally, you'd be able to paste any markdown into our editor and have it render properly, but still something we need to work on.

A markdown to HTML (email) converter would be neat though.

We're trying a different model - pay for your core audience and any emails (product updates, user touch points, and transactional) are all included. If you have a use case that sends outside of your core audience (maybe sharing content with non-users of your product, we bill on a more traditional email volume pricing.

yah sorry, there is a button there "view all pricing plans" that will get you up to 100k contacts.

Lexical has been great. I think the biggest drawback is that its an earlier project (compared to alternatives) so there are not always best practices for what we want to do. That said, the community is pretty active (in discord) and generally responsive to bug reports.

ah so bring your own MTA - that's an interesting idea and would definitely make it easier to switch over. How would you expect pricing to work at that point?

Our intention is that it's clickable - I can't replicate this but others have mentioned it. What browser are you on?

Thanks! We actually have an integration with Make launching soon. I can invite you to the private version, shoot me an email -> adam@loops.so

Thanks! We're aiming for an easy to use modern platform, so thats great to hear.

Right now we're using AWS SES for our MTA. We've had a pretty great experience with them to date. We don't currently offer dedicated IPs but we likely will in the future. When we do, we want to make sure that customers have the required send volume to actually see a benefit from using one. I think a lot of services offer dedicated IPs too early as a panacea for increasing delivery rates. What we've noticed is that these initial IPs are warmed up so perform well, but over time, if the send volume is too low, it's reputation can atrophy.

We monitor our delivery platform wide and proactively contact customers if there are issues with their account.

As far as spam, yes, we allow you to contact within your own audience as much as you like but we do monitor this for abuse.

Cool, let us know how we stack up!

Its definitely come up! I think it would be cool to have a community working on the translations to MJML from Lexical. There are so many corner cases and email clients out there, it's definitely a challenge to get things working everywhere. What type of compliancy problems have you run into?

Loops (YC W22) | https://loops.so | Full Stack Engineer | Remote | Full Time

We just finished YC and are looking for our first hire. You'll be instrumental in architecting our service and able to shape the culture of our engineering team. This role will begin as an IC role but will evolve into a leadership role as the team grows.

Our stack: NextJS, Postgres, AWS services

Job Posting: https://www.ycombinator.com/companies/loops/jobs/yUbFitU-ful...

Contact: adam[at]loops.so

Adam, CTO Loops

I'm part of a team creating content at Codecademy to fill exactly this need. It is currently part of our Pro feature.

The courses cover computer science data structures but we will be adding algorithms in the near future.

https://www.codecademy.com/learn/paths/computer-science/

If you are already familiar with Python, you probably want to skip to the 7th unit.

Feedback is appreciated!

I guess the simplification I drew may not apply to everyone (edited). The off the cuff example given in the interview seemed to reinforce the idea that middleschool girls should be worried about guys and that didn't seem very empowering to me.

I'm all for making it more appealing for everyone to learn to code, but I was torn over this product by a comment made by Sara Chipps on the Giant Robots podcast (http://giantrobots.fm/246).

One of the use cases she mentions is "...4 buzzes means the guy you like is nearby...".

"Space is big. Really big. You just won’t believe how vastly hugely mindbogglingly big it is. I mean you may think it’s a long way down the road to the chemist’s, but that’s just peanuts to space." The Hitchhiker’s Guide To The Galaxy, The Hitchhiker’s Guide To The Galaxy

Amen.

I develop our Roku channel - https://channelstore.roku.com/details/61657/curiositystream. You currently need to sign up on our website and link your device. The next release will incorporate Roku billing so that you can sign up directly on the device.

Comments are appreciated!

We don't currently - but our underlying player supports it. We'll add it to our feature requests.

Our press kit has links to the major articles (https://medium.com/@CuriosityStream/curiositystream-is-the-w...).

Pricing is $2.99/month for SD quality and $5.99/month for HD.

As someone who has worked in this industry and seen a lot of these ideas fail first hand - another big challenge is going to be ground entry points. For GEO satellites, each satellite serves many customers and may only need maybe 2-3 (for redundancy) groundstations.

For LEO constellations, each satellite can only see a small portion of customers at any time and will quickly move out of coverage of a single point on the earth, requiring many groundstations.

Alternatively, the satellites can crosslink and eventually hit a groundstation, but these handoffs and trip lengths quickly get back to the ping latencies of making a single trip to GEO.