- 0 Posts
- 12 Comments
Thanks for all the work you’re putting into this! Did you see https://lemmy.world/post/33265623/18360512? Some things do work, like https://friendica.world/profile/gargle/profile. My script however queries https://friendica.world/api/statuses/public_timeline with my user and password.
This is good to know, thanks for posting this!
I wrote a script to facilitate reporting the issues. You may find it at https://codeberg.org/gargle/check-friendica. Documentation is included.
Sat 19 Jul 17:15:35 CEST 2025 : 504 : 504 Gateway Time-out The server didn’t respond in time. @ruud@lemmy.world
Sun 20 Jul 07:46:41 CEST 2025 : 504 : 504 Gateway Time-out The server didn’t respond in time. @ruud@lemmy.world
Mon 21 Jul 15:03:13 CEST 2025 : 504 : 504 Gateway Time-out The server didn’t respond in time. @ruud@lemmy.world
Tue Jul 22 07:45:11 CEST 2025 : 504 : 504 Gateway Time-out The server didn’t respond in time. @ruud@lemmy.world
Wed Jul 23 09:06:20 CEST 2025 : 504 : 504 Gateway Time-out The server didn’t respond in time.
Interesting! My script still reports “Wed 23 Jul 19:11:06 CEST 2025 : 504 : 504 Gateway Time-out The server didn’t respond in time” but my browser does render all friendica.world pages. It’s very slow though. My script queries api/statuses/public_timeline. If I change to api/externalprofile/show I get a 200 instead of a 504. I’ll keep my script on api/statuses/public_timeline however…
Thu Jul 24 09:07:51 CEST 2025 : 504 : 504 Gateway Time-out The server didn’t respond in time.
https://friendica.world/network initially gave a 504 Gateway Time-out in my webbrowser. https://friendica.world/profile/gargle works, and https://friendica.world/profile/gargle/conversations too. https://friendica.world/network (latest creation, latest post, and latest activity) work as well now. Tested at 9:15 CEST.
Tested again in my webbrowser at 9:30 CEST: https://friendica.world/network: 504 Gateway Time-out.
Fri 25 Jul 09:27:31 CEST 2025 : 504 : 504 Gateway Time-out The server didn’t respond in time.
Sat 26 Jul 20:00:51 CEST 2025 : 504 : 504 Gateway Time-out The server didn’t respond in time.
Sun 27 Jul 09:13:06 CEST 2025 : 504 : 504 Gateway Time-out The server didn’t respond in time.
Mon Jul 28 11:20:33 CEST 2025 : 504 : 504 Gateway Time-out The server didn’t respond in time.
https://friendica.world/network gives a 504 Gateway Time-out in my webbrowser every first attempt of the day. The second attempt however seems to work most of the last few days. My script always complains. 504 Gateway Time-out still appears in the webbrowser, but it’s usable.
Tue Jul 29 08:45:19 CEST 2025 : 504 : 504 Gateway Time-out The server didn’t respond in time.
https://friendica.world/network worked on first try today the 29th of July. It appears a bit slow, but usable.
Tue Jul 29 19:49:22 CEST 2025 : 503 : 503 Service Unavailable No server is available to handle this request.
Tue Jul 29 19:51:35 CEST 2025 : 504 : 504 Gateway Time-out The server didn’t respond in time.
Thu 31 Jul 10:47:55 CEST 2025 : 504 : 504 Gateway Time-out The server didn’t respond in time.
Thu Jul 31 21:56:11 CEST 2025 : 504 : 504 Gateway Time-out The server didn’t respond in time.
https://friendica.world/network gave 504 Gateway Time-out in my webbrowser all day. https://friendica.world/profile/gargle gave a 504 Gateway Time-out in my webbrowser too. https://friendica.world/contacts shows the contacts, but the style sheet seems missing. Tested at 21:57 CEST.
Fri Aug 1 09:57:15 CEST 2025 : 504 : 504 Gateway Time-out The server didn’t respond in time.
https://friendica.world/network worked first time in the browser today at 9:58 CEST.
Sat 2 Aug 10:01:35 CEST 2025 : 504 : 504 Gateway Time-out The server didn’t respond in time.
https://friendica.world/network gave 504 Gateway Time-out in my webbrowser on the first try. https://friendica.world/profile/gargle worked right away in my webbrowser. https://friendica.world/contacts shows the contacts with proper style sheets, tested at 10:05 CEST. https://friendica.world/network in the webbrowser works too.
Sun 3 Aug 19:17:38 CEST 2025 : 504 : 504 Gateway Time-out The server didn’t respond in time.
https://friendica.world/network gives a timeout at 19:33 CEST today Sunday the 3rd of August. https://friendica.world/profile/gargle/profile appears quick. https://friendica.world/contacts gave a ‘Not Found’ (Request: 688f9d89dc017). A second attempt at https://friendica.world/contact worked.
Tue Aug 5 09:18:19 CEST 2025 : 504 : 504 Gateway Time-out The server didn’t respond in time.
For the record, I experienced the same behaviour yesterday the 14th of July, but it didn’t take long. I tried again 5 minutes later and friendica.world was back. Today, it took way longer. 9:38 CET friendica.world is back it seems.
18 July, 09:42 CEST: 504 Gateway Time-out. The server didn’t respond in time. @ruud@lemmy.world
19 July, 11:21 CEST: 504 Gateway Time-out. The server didn’t respond in time. @ruud@lemmy.world
15th of July, 8:24 CET, 504 Gateway Time-out. The server didn’t respond in time.
5·6 months agoI asked Claude 3.5 Haiku to write me a quine in COBOL in the bs2000 dialect. Claude does now that creating a perfect quine in COBOL is challenging due to the need to represent the self-referential nature of the code. After a few suggestions Claude restated its first draft, without proper BS2000 incantations, without a perform statement, and without any self-referential redefines. It’s a lot of work. I stopped caring and moved on.
For those who wonder: https://sourceforge.net/p/gnucobol/discussion/lounge/thread/495d8008/ has an example.
Colour me unimpressed. I dread the day when they force the use of ‘AI’ on us at work.
I’m using friendica.world more since the 6th of July. My first login on the 6th failed. Since then I haven’t experienced any trouble logging in. Everything is usable since the 7th and performance is a lot better. I’ll report back whenever I experience trouble.
LibreCalc and python for the win! I just love from bs4 import BeautifulSoup, import json, import re, import urllib.request.
Friendica.world is down again. I read @ruud@friendica.world’s explanation yesterday. I hope they figure it out.
It’s down again right now. I see the @ruud@lemmy.world is working on it.
https://friendica.world/network worked first time in the browser on the 1st of August at 9:58 CEST. My script however goes for the api, and https://friendica.world/api/statuses/public_timeline reported trouble that day. The 2nd of August https://friendica.world/network gave trouble in the browser.