olliepop

Component lifecycle methods to hooks and HOCs, does that ring a bell?

I'm a long-time Reflect user, the progress in the last 12 months alone has been enormous.

- The web app is super snappy, works well offline on long-haul flights, and notes are end-to-end encrypted.

- I backup my notes weekly on Monday mornings by downloading the raw JSON file and storing it in safe cloud storage.

- The UX is a pleasure to use, and each new feature is added thoughtfully and seems an obvious addition once implemented.

The reality is that virtually all of the public AI tech available right now is from OpenAI. Over time as more models are commercialised and generally available, it's probable that Helicone will serve them too.

Congrats Justin and team! Excited for you.

Unfortunately they are relying on the iOS app store to distribute their app, so safe to say they won't be around much longer due to third-party services etc etc.

This made my day. Thanks dude, you're amazing and very inspiring.

Essentially, Bolt (and Fast etc) are offering the convenience of a "1-click checkout" identical to Amazon's 1-click checkout button.

If you transact with Bolt at least once through any of their merchants, then Bolt will have saved your billing and shipping information so that future purchases are instant and do not require checkout forms to be completed. Theoretically with the reduced checkout friction there is a reduction in abandoned carts.

Makes no sense to me either.

Assuming those order-books are legitimate.

@Bitfinexed (https://twitter.com/Bitfinexed) would argue that order books based on USDT (Tether) are not, and either the rug would be pulled or you will quickly find that you're holding ~2% of filled value (actual backed Tether)

key takeaways:

- fonts can be unnecessarily huge

- monolithic js = slow. Chunk at build time.

- content-visibility: auto for lazy rendering

I migrated our entire fleet to Fleetsmith a few weeks ago, largely due to their third-party catalog and features like Chrome extension deployment.

All third-party apps have now been pulled and we have virtually no fleet management.

Happy for them, but it's painful for us. Classic Apple move.

This is open-source, requires self-hosting, is free... There really isn't anything to compare.

This is a phenomenal explanation. Thank you - I've saved this for next time I need to explain to a junior.

They are. Microsoft, especially under Ballmer, was notoriously anti-OSS (open-source). Not only did Satya make the decision to shift the company to be cloud focused, he represented a change of guard when it was critically important to make peace with the open-source community.

Ballmer: Called Linux "Cancer". Literally.

Satya: "We are all in on open-source"

No doubt because Jack Dorsey was SIM jacked[1]. SMS 2FA is incredibly insecure.

[1] https://www.nytimes.com/2019/09/05/technology/sim-swap-jack-...

Ironic that this would appear below a banner with the slogan "Making Web Content Available For All"*

*Screen cap: https://i.imgur.com/tnTvaAJ.png

If you're interested, please be warned that these betas are extremely buggy. I don't mean 1 or 2 bugs experienced per day, I mean a bug in almost every minute of interaction. You will incur severely reduced battery life and many broken apps, particularly on the iOS beta. On the upside, this is an invaluable preview particularly for an app developer or Apple enthusiast.

At the very least you should back up your device first so that you can roll back if necessary - officially there is no other way other than performing a factory reset.

Yes, and it's worse than ever before.

Ironic, because you claim without any supporting references that you "thought" that the statement ("claim with high confidence") is intelligence speak for no evidence, and then use this assumption to conclude that it's no better than citing anonymous sources.

I struggled with this. We implemented Firestore (successfully) in a production mobile game for the real-time chat and configuration aspects. The SDK WebSocket implementation for real-time updates was a huge factor here.

At the time we were using the Firestore beta, Security Rules were also very poorly documented with no tooling apart from the editor (beta product - I know, I know).

Ultimately we found several vulnerabilities in our own implementation of Firestore that were difficult or practically impossible to resolve on our end. The workaround was to communicate with Firestore only by using the admin SDK.

I still completely vouch for Firestore and Firebase as a product.

We're closing our seed round this week - this is such a good reference, especially because I have a technical background.

Is anybody able to shed some light on the key differences between a seed term sheet and this Series A term sheet?