I was also trying to set up GPSLogger whilst it was crunching through the backlog, and I manually transferred a file from that app before I had autologging configured. Not sure if that could have done it?
The times don't overlap, as the takeout file is only up until 2023
It's a 1gig json file that has about 10 years of data. I get multiple repeats of the rabbit timeout in the logs. The Job Status section tells me that it's got just under 9 hours of processing remaining for just over 16,000 in the stay-detection-queue. The numbers change slightly, so something is happening, but it's been going for over 12 hours now, and the time remaining is slowly going up, not down.
reitti-1 | 2025-07-04T03:06:08.820Z INFO 1 --- [ntContainer#2-1] c.d.r.s.p.VisitDetectionService : Detected 61806 stay points for user ada
reitti-1 | 2025-07-04T03:06:17.848Z WARN 1 --- [ntContainer#2-1] o.s.a.r.l.SimpleMessageListenerContainer : Consumer raised exception, processing can restart if the connection factory supports it
reitti-1 |
reitti-1 | com.rabbitmq.client.ShutdownSignalException: channel error; protocol method: #method<channel.close>(reply-code=406, reply-text=PRECONDITION_FAILED - delivery acknowledgement on channel 9 timed out. Timeout value used: 1800000 ms. This timeout value can be configured, see consumers doc guide to learn more, class-id=0, method-id=0)
reitti-1 | at org.springframework.amqp.rabbit.listener.BlockingQueueConsumer.checkShutdown(BlockingQueueConsumer.java:493) ~[spring-rabbit-3.2.5.jar!/:3.2.5]
reitti-1 | at org.springframework.amqp.rabbit.listener.BlockingQueueConsumer.nextMessage(BlockingQueueConsumer.java:554) ~[spring-rabbit-3.2.5.jar!/:3.2.5]
reitti-1 | at org.springframework.amqp.rabbit.listener.SimpleMessageListenerContainer.doReceiveAndExecute(SimpleMessageListenerContainer.java:1046) ~[spring-rabbit-3.2.5.jar!/:3.2.5]
reitti-1 | at org.springframework.amqp.rabbit.listener.SimpleMessageListenerContainer.receiveAndExecute(SimpleMessageListenerContainer.java:1021) ~[spring-rabbit-3.2.5.jar!/:3.2.5]
reitti-1 | at org.springframework.amqp.rabbit.listener.SimpleMessageListenerContainer$AsyncMessageProcessingConsumer.mainLoop(SimpleMessageListenerContainer.java:1423) ~[spring-rabbit-3.2.5.jar!/:3.2.5]
reitti-1 | at org.springframework.amqp.rabbit.listener.SimpleMessageListenerContainer$AsyncMessageProcessingConsumer.run(SimpleMessageListenerContainer.java:1324) ~[spring-rabbit-3.2.5.jar!/:3.2.5]
reitti-1 | at java.base/java.lang.Thread.run(Unknown Source) ~[na:na]
reitti-1 | Caused by: com.rabbitmq.client.ShutdownSignalException: channel error; protocol method: #method<channel.close>(reply-code=406, reply-text=PRECONDITION_FAILED - delivery acknowledgement on channel 9 timed out. Timeout value used: 1800000 ms. This timeout value can be configured, see consumers doc guide to learn more, class-id=0, method-id=0)
reitti-1 | at com.rabbitmq.client.impl.ChannelN.asyncShutdown(ChannelN.java:528) ~[amqp-client-5.25.0.jar!/:5.25.0]
reitti-1 | at com.rabbitmq.client.impl.ChannelN.processAsync(ChannelN.java:349) ~[amqp-client-5.25.0.jar!/:5.25.0]
reitti-1 | at com.rabbitmq.client.impl.AMQChannel.handleCompleteInboundCommand(AMQChannel.java:193) ~[amqp-client-5.25.0.jar!/:5.25.0]
reitti-1 | at com.rabbitmq.client.impl.AMQChannel.handleFrame(AMQChannel.java:125) ~[amqp-client-5.25.0.jar!/:5.25.0]
reitti-1 | at com.rabbitmq.client.impl.AMQConnection.readFrame(AMQConnection.java:761) ~[amqp-client-5.25.0.jar!/:5.25.0]
reitti-1 | at com.rabbitmq.client.impl.AMQConnection.access$400(AMQConnection.java:48) ~[amqp-client-5.25.0.jar!/:5.25.0]
reitti-1 | at com.rabbitmq.client.impl.AMQConnection$MainLoop.run(AMQConnection.java:688) ~[amqp-client-5.25.0.jar!/:5.25.0]
reitti-1 | ... 1 common frames omitted
I don't use bluesky or nostr for the very reasons I outlined in my comment, and I wouldn't recommend them to anyone. Especially nostr, which is a shit hole.
My point is though, they both do non centralised ID, giving similar benefits to what the OP is suggesting, without the centralisation they're suggesting
And no, a central account doesn't require a central service, it just requires amendments to the protocols to allow for a decentralised identity. Nostr, bluesky, etc all work that way. Nostr is full of nazis and bitcoin bros, and bluesky is effectively centralised in other ways, but both of them do have a genuinely decentralised single identity system.
There are a few ways of doing it. A single account on the first platform, and then signing up to remote platforms with that account. A system of trust that allows a user to verify that other remote accounts are genuinely also them. Combine it with platforms that recognise content posted from other accounts/platforms that belong to the same person, and let them edit the "remote" content locally and federate it out again etc.
So you don't end up with a centralised identity, but rather, the ability to manage your identity from whichever instance you happen to be signed in to as if it were created locally on that instance.
A passport in the way described here doesn't need to be centralised. Your profile could link to your other profiles through metadata, rather than a centralised system.
I have zero interest in going to a place where people who want to take away other peoples rights are given a welcome mat.
The people that will go there are people who want to (civilly) hate on other folk, and free speech absolutists.
What you won't get, is a genuine cross sampling of perspectives and viewpoints, because it will end up being dominated by hateful voices (civil voices, but hateful). And that's what the other person meant when they said that no moderation is a form of censorship/bias in and of itself. Which is to say, you won't saving anyone any time soon, because the people who do want to save folks will be the least likely to use the spaces
The first time I tried to use the scan and go system, I got pulled up at the exit point and had to prove that I'd purchased the stuff. Wasn't keen on being made to feel like they thought I'd robbed the place, so I never went back to it
The domain you linked isn't a public domain. It's only visible within your local network