Agree with the other 2 replies that hammering the dyndns server every minute is excessive and you should only send them updates when your IP address actually changes.

You should also check the TTL on the primary name server (the dyndns server) and the DNS server you use (likely your ISP’s DNS server).

https://johncireland.wordpress.com/2020/09/07/viewing-dns-record-ttl-on-windows/

The dyndns server probably has it configured right and it should have a low TTL like 5 minutes or below, but sometimes the DNS server you use can be a server that ignores TTL and caches the result for longer than expected. I don’t think this is the problem if multiple of your friends are having the same problem but it doesn’t hurt to check.

Gamers’ Nexus video says it’ll be laptop-type memory and upgradable.

Well, you do have the Gabe Virtual Boy.

Ironic Microsoft doesn’t have enough electricity to power their hoarded gpus.

Just a follow up, it is fixed with this pull request. I think piefed.zip has already deployed it and it is working for me now.

Thanks @wjs018@ani.social .

Thanks, so Voyager is showing the posts in the order the APIs returned them? I guess I’ll play around with the APIs a bit and see if there is a difference between lemmy and piefed.

FWIW, pinned posts do show on top on piefed’s native web interface.

Yes, piefed 1.2 just released, piefed.zip might have upgraded.

The problem seemed to have fixed itself today. I see an update for voyager is available in browser but I have not updated yet, still on 2.39.2. I don’t see any update on iOS app store, but 2.39.2 is working.

There was no announcement of change on piefed.zip but perhaps something changed there? I’m not sure. I have not received additional notifications since last time I replied.

EDIT:

I went into dev tools again and it seems piefed.zip did not return 404 this time.

deleted by creator

I deliberately did not clear the notifications (I could see them if I use piefed directly but I did not mark them read), I’ve received a few more notifications since then but there has been no change in voyager, still getting the same error consistently.

@aeharding@vger.social It is still occurring. Is there any logs I can collect to help you diagnose this?

Just ran into the same thing on piefed.zip. Happened (still happening) on both PC running browser and iOS app.

It worked fine when I received the last notification 10 hours ago, I don’t think piefed.zip changed their software between then and now.

There are 2 new replies to my post which caused the notification, I can see in developer tools the replies loaded and the json response looked okay at a first glance. Not familiar enough with piefed api to know what the “list” call that got a 404 is for or whether that is a problem.