AI-generated code may look promising, but is it really ready for the real world? I think it's time to focus on investing in ourselves first and not rely on #AI to do the heavy lifting for us yet. #softwaredevelopment#aifuture#OpenAI#OpenAIChatGPT
https://t.co/QZrDzuTgXt
@LiteMods @TwitterSafety @TwitterSupport Nope. They're not. Not at all. Already reported tons of accs posting unlawful content (in accordance to GER Network Enforcemnt Act NetzDG). They were spreading the RU propaganda and even using footage of civilian victims to accuse UA killing them. Not a single report was accepted
Mein Kollege @das_System trifft den Nagel auf den Kopf! Wer führt hier eigentlich wen und wohin führt das Ganze? Interessanter Beitrag über die gegenseitige, menschliche sowie fachliche Führung feat. echte Einblicke und Erfahrungen aus der @tarentsolutions
https://t.co/2XdeNgZX5n
Oh and just out of curiosity: is @ZenCronus with their stupid hardware cheat box actually complying to your ToS? I guess not. Please consider spending some of that energy into getting them off the market @Activision
@Activision@ATVI_AB get your stuff sorted out! Taking legal actions against your own community is certainly not a smart move. At least allow those two guys from @SbmmWarzone to comply to your own ToS and reach out to them!
Activision’s lawyers reached out and asked us to shut down https://t.co/aX094FtqB8. According to their ToS, we can’t use their API. We’ve tried to reach them multiple times to become Partners, now is our last shot. Anyone working at #Activision, please reach out [1/7] ⬇️
@Rich_Harris@aislan_maia@eugenioclrc just throwin it out there - as I personally need to hear that from others as well from time to time: done is better than perfect :)
*at least for a first public beta :D Oh and btw are the sources for sveltekit public yet?
With that generic error message one might think your servers are just under heavy load and trying again later, as I said, probably won't help at all ;) (3/3)
@homeaway you have a nasty bug on your https://t.co/fxFifbGFcN portal. Entering a cancellation message with more than 1000 chars leads to an error message advising the user to try again later. However that won't do much. Please show a better message or allow more chars. (1/3)
I could only figure that out by using the chrome dev tools to inspect the graphql response. I guess as many people are trying to cancel their bookings now and not all of them being capable of using the dev tools that would help them going. (2/3)