mastodon - Link to source

📢 #FOSSWarn 1.0.1 is now on F-Droid. This release addresses some issues with the push-notification setup and fixes some bugs.

One crucial bug fix was related to the coordinates of the subscription bounding box. The coordinates (after a subscription has expired and the resubscribe feature was used) might be swapped (so lat is long instead). Please check your subscription and remove it if it is incorrect, and re-add the place. You can check the bounding box by pressing the icon to the left of the place name.

Other improvements are:
- a notification self-check feature
- an easy check to switch between distributors
- bug fix with a parser error with biwapp alerts

Read the the full release note here:
github.com/nucleus-ffm/foss_wa…

github.com/nucleus-ffm/foss_wa…


Release 1.0.1 · nucleus-ffm/foss_warn

This update brings some new useful features for the push-notifications and bugfixes. This also fixes a bug with swapped coordinates after a resubscribe. If you have used the resubscribe feature aft...
GitHub
#fosswarn
in reply to FOSS Warn

mastodon - Link to source

Daniel Gultsch

@schlumpf timeouts? Not sure what that could be. I don’t have a rate limiting mechanism that would lead to timeouts.

Can you reach the redirect when you GET / on up.conversations.im? Generally GETs to the endpoint URL should get you a version number.

What about other hosts on that machine like gultsch.de

Daniel Gultsch

I’ve been a freelance software developer for over 15 years. My main interests lie in open standards and communication protocols, including instant messaging, email, and the fediverse. I’m the project lead for Conversations and Ltt.rs.
Daniel Gultsch
@schlumpf
in reply to Daniel Gultsch

mastodon - Link to source

FOSS Warn

@daniel @schlumpf Mh ok, I checked the server logs, and it seems like we are getting 404 responses here. Can this be related to deleted registrations for push notification on your server? So, if a user registers and later removes their registration, and we attempt to send a notification to that user, do we receive 404 responses in that case?
@schlumpf @Daniel Gultsch
in reply to Daniel Gultsch

mastodon - Link to source

FOSS Warn

@daniel That's due to our mechanism to protect us from running into timeouts all the time. We had quite a few issues with that in the past. We set a flag for servers where we can not deliver push notifications. The flag expires after 5 minutes; during this time, every request to the server is aborted due to the flag. So in this case, the error is that we set the flag in cases where we should just delete the subscription. Is there an easy way to let a conversation's up registration expire to test that?
@Daniel Gultsch
⇧