Pokémon Ruby and Sapphire footage shared by the official Japanese Pokémon account has sparked fresh speculation of a new Nintendo Switch release. https://t.co/r4yR55tXO7
Bad news for Pokémon scalpers.
Nintendo says it’s working on new ways to stop scalpers.
At the annual shareholder meeting this year, president Furukawa said they are working to make sure cards end up with fans instead of resellers.
Do you think Pokémon can beat the scalpers?
Pokémon scalpers are complaining that the franchise's new 30th Anniversary set has been too generous with its rare cards — leaving resellers unable to generate their usual profits.
And everyone applauded. https://t.co/oZiOgFAFdJ
After warning her repeatedly about hanging around people involved in theft and crime, a father finally stepped in and pulled his daughter away himself.
Was he protecting her… or crossing a line?
ShinyHunters is claiming they popped @FBI recruitment via a @PeopleSoft 0-day, pivoted into @AWS GovCloud, and walked out with 2–3TB on agents and applicants. @FBI is only confirming it’s looking at activity on https://t.co/x4mrMidw3b. Not confirmed. Still a reminder that HR/ATS stacks are high-value targets and “gov cloud” is not a magic word.
52% of QA folks say bug volume went up after teams started shipping AI-generated code.
58% say their own workload grew.
0% fully trust the output.
AI didn’t replace testers. It gave them a firehose
If you missed @shubgaur’s Founders session at Grok @Bot Galaxy today, here are my favorite 20 tips:
1. browser and computer use is powerful, but also expensive… if the job does not need a UI walkthrough, a login, or visual QA, run a connector, API, or MCP first. keep computer use for the jobs that need a screen.
2. most spend gets driven by clicking through forms or sites a structured tool already covers.
3. routines are awesome until you don’t audit them. put your recurring work on a clock… then kill anything wasteful on a schedule. auto-optimization is cheaper than hoping you remember it later. duplicates or every-15-minute routines might already be running. be wary of your wording and check often.
4. have a bot who regularly runs auto-optimization routines for cost hygiene.
5. don’t treat bots like disposable agents. keep em, feed em corrections, and let em compound like employees instead of throwing them away after one imperfect run or a temporary job.
6. use the compounding of your bot learnings and multi-bot work so your bots keep improving.
7. let bots compare their drafts and mistakes against what you finalize.
8. you can teach your bots skills and tell them to forget things to improve memory and context management.
9. make a voice bot that keeps learning from your tweets, emails, drafts, writing, etc.
10. group your bots by expertise so random asks do not pollute your specialists.
11. your founder or chief of staff bot seat should stay focused on decision quality and your velocity. every other craft you have is a candidate for a persistent bot with real tool access.
12. map all your responsibilities for at least one day, even if it takes 1 to 2 hours. then deep delegate, including verification. you’ll be surprised how much you can automate.
13. when you want something done, prompt the whole job, including the verification, and then stop babysitting completion.
14. things you think couldn’t scale can become repeatable when a bot runs them. so try and connect more if you’re comfortable there… f*ck around and find out.
15. for bots and routines, tell them to stay quiet and ping only when something actually matters, or you could get message spam.
16. use groups and channels wisely. if you don’t set the correct parameters and don’t individually ping a bot, all of them could talk and churn token usage.
17. import cookies only where you want to stay signed in and where you trust the bot.
18. ship skills and saved learnings often. repeatable flows beat clever one-off prompts.
19. as a founder, your feedback to ship can now move in mere hours. the only bottleneck is which feedback you accept. set up systems to filter the quality feedback from the noise.
20. check the official marketplace for Grok Bot templates already vetted by the team that you can use or remix… also ask questions to get familiar if you add/port one into your setup.
save this list. audit your setup tomorrow.
@Gallard70146933@ijustine If it was the size of the Pixel 11 Fold then that wouldn’t be bad but the size of the original Pixel Fold is why I’m skeptical about it
@ijustine 2000 dollars is crazy money for a glorified IPad Mini 🤦♂️I prefer to pay that towards a nice holiday for me and my family and capture the moments with my IPhone 16 Pro.
@MrColionNoir looking to see what your thoughts are on this since Idaho has constitutional conceal carry and I believe open carry for 18+ https://t.co/Qsg0qeVRjj