I wish I had the time for conventions, competetions and other fun stuff like that...

@retoor Isn't skyRant iOS exclusive??

I was considering making an third party Android client for devRant. But Android is SUCH a pain in the ass in terms of development that I'd need to be REALLY bored and hate myself really hard to actually do it. Fuck Android development, I have made a few Android apps, and each and every one had me genuinly struggle keep myself from tearing my own hair off. Android development invokes primal fucking rage and hatred in me.

No, you're not the only one, I also used the official dR client for android, and yeah, it doesn't work since the certification expired.

Why, is there a different dR client for Android???

(Since you're calling it old)

@Lensflare Except whatever broke images is probably a complex problem that might require either money or a lot of debugging time to figure out, which would make no sense for an abandoned project. Meanwhile renewing ceritificates takes a few minutes and a couple terminal commands and then you forget about it

Yaaay, at least for iOS it will work.

I don't have or use any Apples, but it's still good news :D

Let's hope it won't take too long until certificates are renewed (Which I assume they will be because it's not the first time)

@retoor cert isn't short for certbot, it's short for certificate (which is why certbot is called certbot)

But also I did check, and devrant was using Let's Encript since the very start (since 2016, the first certificates were signed by Let's Encrypt) sooooooooo xD xD xD

@jestdotty Wait, what do you mean "was", is sharing food/drinks taboo or something nowadays???

I am completely aware these problems are very probably EASILY solvable, I'm not sayin "Muh, Uh, Windis sucks, I don't know how to do a thing, it's wundus fault".

There are solutions, I just couldn't find them, and I'm not willing to spend more than a day on this.

@retoor Actually it's my first time making a user service too :D

I only ever made system services for my servers and other random stuff.

And yeah it's somehow working better than expected.

Also works really nicely with combination with a conventional RSS reader, I use Akregator and if I accidentally close a notification or want to go back to one that I closed I just launch Akregator.

@whimsical I don't have the amount of free time you do, so nothing. Will probably make the install script for windows together with a task to run it automatically on boot on the weekend if I'll have the time.

If you add items about new rants to the RSS feed (or into a different /dr.notifs.xml feed containing both mentions and new rants, if it breaks @Lensflare's things) then I'll be able to implement the "Subscribe" feature that currently exists in the script but is not implemented until the RSS will have it. Like "@user posted a new rant" items. And then I could enable the "Subscribe" feature in my script, when I'll have the time.

@AlgoRythm Nah, this actually only took a single sitting of 16 hours straight of coding on a "free" day. Otherwise I'm not that active here (for a lack of time)

The "bug fixes" today were more like a few minutes here, a few minutes there, while I was doing other stuff

Works on windows :D

https://devrant.molodetz.nl/preview...

https://devrant.molodetz.nl/preview...

Windows Test @SoldierOfCode @retoor

Oh, totally forgot to update,

The update is live on GitHub

@retoor @whimsical @Lensflare @12bitfloat

Last test just to be sure @SoldierOfCode

Okay, yeah, it works, I'll push an update to github soon enough

@whimsical test @SoldierOfCode

@whimsical Ah, okay, I'll set it to 90secs then

@12bitfloat - Don't install yet, update(fix) incoming

@retoor, so the interval/sleep/timer/whatever is now every 60 seconds?

I'm testing the fix I mentioned (relying on last actual item, and not rss date) on my end right now, I'm going to make the sleep interval close to yours.

In the original script it was 300(i.e. 5 minutes like yours) but I accidentally commited the test version which had SECONDS set to 15 instead of 300 after I was testing with text files.

@retoor

> it's logic, fetching the comments takes some time. So, it can be minutes behind, but this new version will be almost live.

No no, it's a different error. Making the delta (difference between feeds) smaller doesn't make the problem go away, because it would still make messages appear 2 deltas behind (instead of one delta as it should)

There's no need to overload the dR APIs because it's still the same error, no matter how quick you'll make it poll it would still be the same error

(Well, unless you make the RSS feed more than twice as fast as my script, but that's not a good solution, 5 minutes was a good delta)

Oh...

You just made it update much faster, I'm seeing on my logs we get a new RSS feed at least once per minute

Let's see, last was 19:50:17 GMT

When's the new one? Ah 19:51:32 GMT

@retoor

> Oke, so, how will we continue on fixing this? Do you expect anything from my end / what exactly?

I don't know what you did, but you fixed it, I just saw that in the new XML the new items are actually withing 5 minutes of the XML's update date, instead of 10 minutes like the previous cases.

I.e. the date is 19:44:20 GMT, (so prev should be 19:39:xx GMT) and the last message is 19:42:15 GMT, so between 19:39 and 19:44

It's an easy "fix" on my end (instead of relying on the faulty RSS, I will make it rely on the most recent message in the feed, to fix the RSS's one step behind issue.

On your end... I'm not sure what the fix would be because I don't know why it would "jump back" like it does. It's weird. Almost as if it first updates the RSS feed, and then reads new messages(instead of first reading new messages and then updating the RSS feed), which would make it always being one leg behind. Idk

So basically, even tho the current RSS feed should be showing NEW items between 19:24:31 GMT(last feed) and 19:29:50 GMT (new feed)

It's actually ONLY showing items older than 19:24:31 GMT - the previous feed, and wasn't showing any of the new mentions that happened between the times of the feeds. The feed is "one update behind", and that's why it breaks the script

Yep, I'm correct

Current time: 19:30:30 GMT

RSS time: 19:29:50 GMT

Last messages:

19:22:55 GMT (x3), 19:22:55 GMT, 19:18:41 GMT

Let's test: @whimsical, @retoor, @SoldierOfCode

Current time: 19:28:21 GMT

RSS time: 19:24:31 GMT

Last item time: 19:18:41 GMT

I think I realized why it doesn't work most of the time!

This needs to be tested but I think it has to do with the time of posting and the time that the RSS feed claims to be updated at.

I noticed that when looking at the feed at 19:09:xx GMT the last item was 19:02:16 GMT (devrant-mention-19384907-to-SoldierOfCode)

But then, the next RSS update was at 19:14:31 GMT, as expected, BUT the two new messages it shared were devrant-mention-19384908-to-whimsical and devrant-mention-19384908-to-retoor at 19:08:50 GMT, so messages that would've expected to be at the feed before that at 19:09:xx GMT! It's "remembering" up new items from the past which should've been included in the previous feed.

And that why my script doesn't see them, after each feed it updates it's date to match the date of the feed's update date, any messages before the previous feed are ignored - That's how my script know which mesages are new

Oh hey it works!

https://devrant.molodetz.nl/preview...

Test @retoor @SoldierOfCode test