Hmmm, some InboxTimeouts are to be expected. The second one could be the result of a scraper or bot. It's still strange your federation list is empty. I'd take a look at the database, clearing the federation queue (public.federation_queue_state) is a good idea. 'public.instance' should be populated with servers (mine has 2836). Peaking into the log files of the database could give some more insight as well.
A successfully federated incoming action will look like this:
2025-07-14T22:40:54.321151Z INFO HTTP request{http.method=POST http.scheme="http" http.host=0d.gs http.target=/inbox otel.kind="server" request_id=61bf0ea2-8df3-42ff-a433-3bec8b37047c}: actix_web::middleware::logger: 10.10.0.1 'POST /inbox HTTP/1.1' 200 0 '-' 'Lemmy/0.19.12; +https://lemmy.ml/' 0.158242
Your outgoing federation seems to be fine now on my end, this is how my server sees yours:
/inbox is the endpoint for federation with ActivityPub, so definitely on the right track. Try increasing verbosity to get a full stack traceback to where in the code it's bugging.
InboxTimeout means your server is taking too long to process API calls to /inbox, I've had them before too due to misconfiguration of the reverse proxy. Make sure you're passing on the right headers, especially the IP headers so they aren't rate limited and the Accept header so your server knows to send json when requested.
Troubleshooting federation gives many options for testing and checking your configuration, running through them might give your more insight.
The strange thing is, in my Lemmy back-end, everything seems normal, and your server is telling mine it's receiving correctly, but we can see it is not.
I left a comment on your server but it doesn't seem to be federating so I'll leave it here as well! original comment
Terribly sorry about nerd sniping you! I'm the owner of martijn.sh, and I'm guessing it was only a matter of time. We're solving the same problem in a completely different way though, so I'll definitely be following your progress and might use it for my lemmy instance as well.
The only difficulty I've found is when federating our small instances to lemmy. Your community only federates with other servers if at least one user on that instance is subscribed to it. An easy way to fast track federation is using lemmy-federate. If you register your instance and your community, an army of bots will automatically subscribe to your community making it available on many more instances at once. The only reason your server now federates with mine is because I searched for it manually and subscribed that way.
Anyway, best of luck on your blog. If you've questions or want to discuss, feel free to send me a message!
If we look at historic crashes, they had major catalysts causing mass sell orders. Right now markets have had time to adjust because the speed of decline has been very slow.
Markets are also largely speculative, many stocks are traded way above their fundamental value (think Microsoft, tesla, or coca-cola). These will probably be hit the hard, algorithms will default to what a stock should be and drop hard. But these companies might have the strongest chance to bounce back as well.
Companies with the strongest books will be safer, but many more risk taking companies won't be as lucky. This is part of what due diligence of a stock will tell you, but also probably one of the hardest parts of investing.
As long as decline is slow, stability can be found. But when uncertainty rises fast, so does the unstability of the stock market. Catalysts such as the public losing confidence in banks causing a bank run, companies downsizing at unseen scales to cut costs, or global political instability are possible.
TLDR: it needs to get way worse, very quickly for the market to crash
My first year professor in electronics started his first lecture "yeah so forget everything you've learned about electricity because it's wrong" - then gave out an infinite matrix of resistors and made us cry.
The problem with this in the OP is the first 'if' checks if the object exists and the second gets a property of said object only if the original object exists.
I'm not saying the OP is good code, but chaining them like this would result in exceptions.
Hmmm, some InboxTimeouts are to be expected. The second one could be the result of a scraper or bot. It's still strange your federation list is empty. I'd take a look at the database, clearing the federation queue (public.federation_queue_state) is a good idea. 'public.instance' should be populated with servers (mine has 2836). Peaking into the log files of the database could give some more insight as well.
A successfully federated incoming action will look like this:
2025-07-14T22:40:54.321151Z INFO HTTP request{http.method=POST http.scheme="http" http.host=0d.gs http.target=/inbox otel.kind="server" request_id=61bf0ea2-8df3-42ff-a433-3bec8b37047c}: actix_web::middleware::logger: 10.10.0.1 'POST /inbox HTTP/1.1' 200 0 '-' 'Lemmy/0.19.12; +https://lemmy.ml/' 0.158242Your outgoing federation seems to be fine now on my end, this is how my server sees yours:
id 2794; ;domain "blog.kaki87.net"; published "2025-06-30T11:35:32.398830Z" ;updated "2025-07-14T00:42:32.758669Z" ;software "lemmy" ;version "0.19.11" ;federation_state: ;instance_id 2794 ;last_successful_id 46037 ;last_successful_published_time "2025-07-14T21:12:27.481507Z" ;fail_count 0You could try updating or reinstalling your back-end as well, lemmy is at 0.19.12.