API access is not coupled with being a ChatGPT+ subscriber, and I believe GPT-4 API access is also not included in that. That means you can use GPT-3.5-turbo via API right now, and GPT-4 through API is available via waitlist.
I'm not yet, because I haven't got confidence in ChatGPT's answers or abilities so far (e.g. the fact that it 'lies' with a straight face when it doesn't know the answer is especially troubling for me). I hope ChatGPT 5 or 6 are much better in this regard, and I will very gladly pay for it then.
At least as a non-native english speaker I was a bit confused as to what an agent would do compared to using plain ChatGPT. I tried then the examples "Plan a detailed trip to Hawaii" and "Write some code to make a platformer game". I tried the same Hawaii sentence with plain ChatGPT and told it that it can browse the web. Now I am thinking that AgentGPT does seem a good tool on top of ChatGPT. As they say on the Github page it "It will attempt to reach the goal by thinking of tasks to do, executing them, and learning from the results". This was a whole lot more thorough service than what plain ChatGPT did with the prompt. I'm just thinking that maybe they should emphasize more those points already on the app page, about the core value it adds and how it does it. Perhaps even explain it some more than what that sentence from their Github page does.
The usual and the right way to enjoy finnish sauna is by throwing water on the hot rocks every 30-60 seconds or so. That way the heat is very endurable, feels very nice and the sauna is actually very humid. Trust me, I am a finn.
Ah, open the link and first thing I see is Finlandia Hall's main concert hall. I worked there as an event assistant and host as young student back in the day. Was very nice to listen to classical music concerts and other on the work there. Nice place, great historic atmosphere. :) No events anywhere near as important as the Helsinki Process during my days though. This was between 2005-2010.
Yes, it's surprising how large amount of the SMSs get lost. At least in Finland this has been the case when using the most popular international SMS API providers. I previously thought also that eventually the messages will be received but have learned otherwise after trying several providers for two different apps. And I have not even found any good explanations for the SMSs getting lost. I think this is sad from the perspective of Progressive Web Applications because often SMSs could act as an easy replacement for push notifications (which are kind of unavailable/unreliable for PWAs).
This is true. However, email is explicitly not a reliable/guaranteed delivery system, so, despite the fact that is is really quite reliable, we keep that in mind when designing systems that make use of that channel of communication. SMS? Not so much. Idiots persist in thinking of it as reliable/guaranteed.
I've been involved in trying to create services and authentication for two web applications with the help of SMS API services from several of the largest international providers of such services. It has been amazing to see how large portion of the authentications SMSs and other messages do not reach the receiver at all. Some numbers don't seem to be reachable at all and some numbers can be reached most of the time, even though the numbers are totally valid mobile phone numbers. At least in Finland this is the case when using the international SMS API service providers.
