google

Attention over time

7-day rolling share of analyzed posts/comments mentioning this entity · 90 daily points ending 2026-10-15

Final complete day: 2026-10-15. Attention was 1.1% — this entity appeared in 30 of 2,852 analyzed posts/comments in the seven days ending that day (46 mentions).

Each point is a seven-day rolling window of complete UTC days; a point is comparable only when at least 100 analyzed posts or comments fall inside it. A day with no analyzed records counts as zero; missing coverage is marked and never shown as zero. The series ends at the latest complete analyzed day — it never extends into the current incomplete day. How attention is measured.

Recent mentions

1. 2026-10-15 23:05 UTCComment

   O% I use it as a Google on my personal phone.

2. 2026-10-15 13:04 UTCComment

   Legally, Google was obligated to disable active APIs and require explicit re-acceptance before charging a dime. Automatically extending a contract under new financial terms without consent is flat-out wrong. Five years ago, I had this exact issue with Google. I stood my ground, cited contract law, threatened to take it all the way, and their legal team immediately backed off and wiped the debt. They knew they had no leg to stand on. Its frustrating to see the tech community just swallow this without pushing back or filing formal complaints. Jokingly, we almost need a devs union for this stuff.

3. 2026-10-14 12:39 UTCComment

   The lion’s share of their business is from big corporate customers paying API prices, not individual subs It’s just like video game console prices are always subsidized. That doesn’t change, because they just want to encourage people to be on the platform to buy games So if you want to know why this assumption is wrong, just look at Google. Google search and Gmail have been free and cost-subsidized for decades, because the majority of the money comes from Ad/Business/power customers That’s much closer to what you’re likely to see with AI. Getting complete market dominance for your brand (to draw in ‘bigger fish’) is worth more than price-gouging a smaller number of cheap sub customers

4. 2026-10-14 11:03 UTCComment

   Unfortunately there's a very steep slope between watching a tutorial coding along and actually applying that knowledge at work. Watching more tutorials won't be much help, either (google "tutorial hell"). Try to make a new project from scratch using what you learnt (and the documentation), only referring to google/stackoverflow (but \*not\* AI) when you're really stuck on something. You'll get better over time. It's best to make some app that you would find useful, for example a personal todo-list, but if you struggle to come up with any idea, you can use this list for example: \- it's good, because every idea has specific requirements and user stories, so you know what exactly to achieve.

5. 2026-10-13 08:49 UTCComment

   A few things to try. Since the Google TXT worked before, the issue is probably with this specific record's value or name, not your DNS setup. 1. Check the value length. DNS TXT strings max out at 255 characters per chunk. Resend's DKIM public key can be longer than that. If it is, split the value into quoted chunks of 255 characters each and paste them together. Most DNS panels accept that. Netlify's form may silently reject an over-long single string. 2. Use the Netlify CLI or API instead of the dashboard. The web form hides errors. Adding the record via CLI or API will show you the real error message, which usually points straight at the problem. 3. Double-check the name field. Netlify appends your domain automatically, so enter only resend.\_domainkey, not the full resend.\_domainkey.yourdomain.com. Also strip any quotes and trailing spaces from the value when pasting. 4. Try a different browser or an incognito window. A silent save with no error sometimes means the dashboard's JavaScript failed, not your record. 5. After it saves, verify with dig TXT resend.\_domainkey.yourdomain.com or an online DNS checker before hitting verify in Resend. Propagation can take a few minutes to a few hours. If none of that works, the Netlify community forum is worth a post. Their team answers DNS threads fast.