Man, the iPhone 15 Pro is the absolute worst iPhone experience I had thus far, really makes me reconsider if I shouldn't just get a cheap android next time. Most definitely not worth the premium.
To be honest I'm mostly fine with the price increase (it hasn't been adjusted for inflation in ages), the thing I do take issue with is that for over a year now (with the 'upgrade' to a new web interface) you can't easily create a password etc. anymore straight from the browser extension.
You click the button in the browser, choose what to create 'I want to create a password (or a note, or whatever)' and then get redirected to their web-app and be presented with a pop-up asking what you want to create (I just told you, didn't I?)
I get it, when you move to a new web-app some things can break. But after using stored passwords creating new ones is pretty much the only other thing you do in the app, it seems to be core functionality that's been broken for over a year now, it's kinda madness tbh.
Edit: To be fair they offered a 'solution' when I reported it: "Don't use the web-app, install our desktop app instead."
Funnily enough I've been using Codex 5.3 on maximum thinking for bug hunting and code reviews and it's been really good at it (it's just seem to have a completely different focus than Opus.)
I generally don't like the way codex approaches coding itself so I just feed its review comments back in to Claude Code and off we go.
I just created an OpenCode skill where both these models will talk to each other and discuss bug-finding approaches.
In my experience, two different models together works much better than one, that's why this subscription banning is distressing. I won't be able to use a tool that can use both models.
> All apps i found were either shit, real shit, or didnt solve my personal need.
Wow, what an amazing coincidence. I made something that looks pretty similar from the looks of it just a few weeks ago because I found the same thing. If I knew your app existed I probably wouldn't have made it. I wasn't even thinking of selling it, just made it for my kid because it makes following various daily routines easier.
It's a mostly vibe coded (well, I made tons of visual and technical decisions but didn't look at the code much except some spot checks) PWA that can run offline on an iPod Touch.
It has some quirks and hidden features for day schedules, timers, etc.
There's plenty of yank in there (yours is almost certainly built better) but it works pretty well for most daily routines.
Yeah, totally agree. Maybe it can inspire your app too, wish you the very best and a lot of sales.
Some of the hidden features:
- If you add a task to a routine and end it with a question mark it becomes a conditional where you can add specific tasks or subroutines on the yes or no condition.
- Make it 'weekday?' and it becomes a switch case for the week.
- 'is it 7:30 yet?' becomes a conditional that automatically detects if it's before that time. I use it for e.g. 'before breakfast' (at 7:30) -> go play (with a timer until 7:30)
N.b. 'fun' fact, my daughter wanted an avatar with clothes that you can earn. The idea was pretty easy to implement but getting nano banana (using a great Claude nano banana skill) to generate the correct images took... some practice. I think I spent more time on the images for the avatars than all the other features combined. It took way too long to realize simple stuff like "nano banana won't generate transparency, only a fake white/grey checker pattern"
Also learned the last iPod touch (great device by the way) has a really low screen resolution which can be quite challenging at times.
I was actually in the feedback form a few days (just to leave a quick rant what an absolute mess this 'liquid glass' iOS-update is after I sadly chose to update...)
And look what happens, it turns out if you switch app-focus and go back to the app (now immediately focused on the text input) your on-screen keyboard becomes pretty much unreadable (white on light grey...)
The feedback is probably going straight to the bin but I couldn't help myself to file a second bug with a screenshot from the first feedback submission with a broken keyboard.
I have the same. While it's a bit jarring the first time you see it, I now consider this a feature instead of a bug.
Maybe it could be styled a bit differently so the search bar is more prominent and in the center of the screen, but just having a search bar without any distractions is a fantastic feature.
If you want a pure search, you can get there from your address bar without even visiting the site first. Or if you really want the search bar on the site, you can go to youtube.com/search for a nice blank page.
You don't need the obnoxious refusal to show videos on the front page.
I real life if someone with an administrative job would jot 50 * 3,000 in a calculator and not notice the answer 1,500,000 is wrong (a typo) I will consider them most definitely at fault. Similarly I know some structural engineers who will notice something went wrong with the input if an answer is not within a given range.
A calculator can be used to do things you know how to do _faster_ imho but in most jobs it still requires you to at least somewhat understand what is happening under the hood. The same principle applies to using LLMs at work imho. You can use it to do stuff you know how to do faster but if you don't understand the material there's no way you can evaluate the LLMs answer and you will be at fault when there's AI slop in your output.
eta: Maybe it would be possible to design labs with LLM's in such a way that you teach them how to evaluate the LLM's answer? This would require them to have knowledge of the underlying topic. That's probably possible with specialized tools / LLM prompts but is not going to help against them using a generic LLM like ChatGPT or a cheating tool that feeds into a generic model.
> Maybe it would be possible to design labs with LLM's in such a way that you teach them how to evaluate the LLM's answer? This would require them to have knowledge of the underlying topic. That's probably possible with specialized tools / LLM prompts but is not going to help against them using a generic LLM like ChatGPT or a cheating tool that feeds into a generic model.
What you are desribing is that they should use LLM just after they know the topic. A dilemma.
Yeah, I kinda like the method siscia suggests downthread [0] where the teacher grades based on the question they ask the LLMs during the test.
I think you should be able to use the LMM at home to help you better understand the topic (they have endless patience and you can usually you can keep asking until you actually grok the topic) but during the test I think it's fair to expect that basic understanding to be there.
I know a teacher who basically only does open questions but since everything is digital nowadays students just use tools like Cluely [0] that run on the background and provide answers.
Since the testing tool they use does notice and register 'paste'-events they've resorted to simply assigning 0 points to every answer that was pasted.
A few of us have been telling her to move to in-class testing etc. but like you also notice everything in the school organization pushes for teaching productivity so this does require convincing management / school board etc. which is a slow(er) process.
Oxide and Friends recently had a podcast episode [0] with Michael Littman about this topic for anyone who's curious about this topic.
This topic has been an interesting part of the discourse in a group of friends the past few weeks because one of us is a teacher who has to deal with this on an almost daily basis and is struggling to get her students to not cheat and the options available to her are limited (yes, physical monitoring would probably work but requires concessions from the school management etc. it's not something that has an easy or quick fix available.)
I was evaluating codex vs claude code the past month and GPT 5.1 codex being slow is just the default experience I had with it.
The answers were mostly on par (though different in style which took some getting used to) but the speed was a big downer for me. I really wanted to give it an honest try but went back to Claude Code within two weeks.
reply