This is such an HN comment and I love it. Get a cheap kitchen scale (with 0.1g accuracy) and weigh everything when you want a snack or an individual meal.
For family meals or when you want leftovers convert your common recipes to being weight based. On some common seasonings (Costco sized) I write the conversion for that seasoning for 1 tablespoon in grams. So much easier to combine dry ingredients without needing a litany of measuring utensils.
I'm not one to defend google, but it seems that they are only ending support for POP accounts, and retaining support for IMAP/SMTP. Seems like a reasonable deprecation for 2025, although they could have given more than a quarter to let people handle the change.
Google nowadays just seems afraid to store personal data. Google have moved your maps history/timeline to be on-device only, seemingly in response to geofence warrants. They're also deprecating health (Google Fit) APIs, and moving that data to be on-device.
So, removing POP (where they need to download emails to their servers), and only supporting IMAP (where emails stay on the third-party server) via their GMail app, that would be consistent with a policy to store as little personal data as possible. (it could also be completely unrelated :)
IMAP was never supported and is still not supported for external account un gmail web. And they don´t remove pop. You can use pop to access your gmail in any email client or in the app if you wish.
Likely because one of the backend systems that implements this functionality depends on some deprecated service. And nobody cares enough to port the POP checker to use something new.
They have worded things dishonestly to make you think that POP can be replaced by IMAP. The IMAP support is only available in the mobile app (not gmail.com) and isn't a "fetch" that integrates fetched emails to your Gmail inbox. It's kept as a separate inbox.
You didn´t understand the article. You can use your gmail with POP or IMAP. What you won´t be able to do is to use POP (IMAP was never an option) to download emails from external account into your gmail account.
1. How much did your involvement lead to the fundraising success?
2. How much did your involvement lead to the products' early success?
3. Does it make sense to take the IP early idea that you were passionate about as part of your exit package?
==========
Expectations:
* you should expect no cash. taking cash will lead to a lower chance of a return on your equity. if you desperately need cash, you should get a small package based on your salary.
* you have no way to protect against being diluted. you have no idea how much work it will take to make this project successful. making it successful will require dilution. at best you could negotiate never being diluted under a certain amount, and making that based on successive valuations. if you leave at pre-seed, and it becomes a unicorn, you likely don't deserve 10%. what do you think you realistically deserve if this is a massive runaway success AFTER you leave.
* one way to think about this, is what would your time have been worth at a company with a higher TC. if you would have been paid $500k including equity somewhere else, maybe you should get the same amount of equity as someone investing 500k in cash, and get the exact same dilution as they would.
* you will not find a standard answer anywhere. you need to find the best solution between:
1. your ego
2. your cofounders ego
3. giving this startup the best chance of success so that all of this time will be worth something for everyone. even if thats less than you want it to be, its better than $0. because all of the hard work lies ahead.
Small nit - protection against dilution - that may not be true; there are laws in the west coast about minority investor treatment. Your overall point -- do what you can to stay a little long and make sure the company is worth something -- is absolutely the right way to think about it.
he's incredibly nice and a passionate geek like the rest of us. he's just excited about what generative models could mean for people who like to build stuff. if you want a better understanding of what someone who co-created django is doing posting about this stuff, take a look at his blog post introducing django -- https://simonwillison.net/2005/Jul/17/django/
Thank you so much for checking something off of my todo list!
Apple TV lets you share with two sets of apple headphones, which is awesome... but I wanted a way to:
* Share to more than two sets
* Extend coverage past the (very generous) bluetooth range of AirPods.
* Have lossless (albeit 44khz/16bit) wireless audio with audiophile headphones.
I was considering using an esp32, but so happy this exists now! Thanks!
> From the team that brought you the magic of Google Search
This feels really disingenuous. Larry and Sergei are the team that brought us Google Search.
"Magic of" is trying to hide the fact that you didn't bring Google Search to fruition. The last 5 years of Google Search do not feel magical at all.
Instead, claim credit for something that you did do with Google Search.
From looking at your LinkedIn:
CTO > Joined Google via acquisition of ITA Matrix and worked on schema.org amongst other very impressive things. Before that, founding team of Bing @ MSFT.
CEO > Worked on search at Google from 2018 - 2024 ( 6 years )
These are impressive credentials-- so find a better way to showcase them.
I built a simple SwiftUI/Swift Data app to do the same thing across my Apple Watch, iPhone, iPad and Desktop.
With the heavy lifting of SwiftUI/Swift Data, and iCloud providing automatic and private syncing, this is the cloc output for my project, (including widgets and all of the code and projects needed to target all of these platforms.)
If you live in the apple ecosystem and want to make a simple tool for yourself, you really should go ahead and do that.
It started as a desire to have a "focus" on my Apple Watch at all times, and in less than 10 hours, I have widgets, shortcuts (and Siri) integrations, and syncing across every apple platform (although I haven't yet tried it on tvOS).
I've thought about productizing it, and I might one day, but that would add orders of magnitude to the time of making this something that people should be asked to pay for.
And I'm not going to open source it, because it is ~500 loc, with no libraries plus a bunch of Xcode generated stuff.
I might do that at some point... this is the main part of it, just a swift data model and one file of views. Plus a bunch of example code for making widgets work.
```
import Foundation
import SwiftData
@Model
final class FocusItem {
let created: Date = Date()
var completed: Date?
var theFocus: String = "New Focus"
var details: String?