#discord update detector
1 messages ยท Page 1 of 1 (latest)
meow
is this thing on
it do be on
meow
poggers?
New canary version: 011412995dad4d93eec0899d7d388ac035fe8888
can we get build number too?
whats the point ๐ญ
use some other tool for that
this is just for automatically running reporter
New canary version: 5b1f7dd63babdab908b7fc50051914ed39176cbd
eh, would be nice so I don't need to subscribe to another service for it
New canary version: 30e4d748b4109e846bb6860496905059ca01e12f
sounds a lot like "you need to execute the code to find that value and it's too much effort for this tiny project"
New canary version: 3b703fdcdce81009b657817e30b19d9e5eb2e1c4
how tf do they push this much man
little trick called "i made this tiny fuckup let me fix it" and "i dont have local testing environment so lets use canary" (maybe?)
why the fuck does discord ptb exist
its just canary
theyl iterally have discord staging
i refuse to believe
does discord have such thing as an update queue?
WHAT IS THAT
New canary version: 0e0437ce41f50293d4cec75ff38dd4ed2a08eab1
WHAT ARE THEY COOKING?
horror
New canary version: b9d5310a99ca43411596d2b52bdffeb274f470a8
can you stop
New canary version: e2e86b89cf06dd595be085da61aac850bfc71a62
client builds are slightly behind canary usually lol
they dont rly test client stuff on stg
why ๐ญ
prod exists
the messenger of impending doom
trol
UH OH
why does it have to happen when I want to show my friend some plugin I built recently 
didcord i beg of you
@fair crescent can you cook for us
discord fucked up canary
wreq cant be found
vencord is still loading patches, it just can't apply them
on canary?
am I just stupid?
@tough spire @fair crescent I'm sorry to report that I'm as stupid as #๐ฅ-vencord-support-๐ฅ users and forgot to actually git pull on my laptop
0 days since going literally insane because I forgot to do something obvious
so sorry 
you are explode
did you stop working on this @tough spire
what needs to change?
- need to be able to dispatch only one branch
- i want to dedupe, so if something was already reported before it won't be reported again
- i want to disable sending if all is working (or all was already reported before)
i think best way to implement 2 and 3 would be to make it able to post some json to my server
or maybe i can run it directly on my vps and get the output and skip github actions
json output would be ideal
I mean it already works like this
basically i want to run it whenever there is new stable or canary and then only report new stuff
it only sends canary and stable because we run on both
so we see breakages immediately without getting spammed
well
forget about that
we can just make it edit the message
so we have 2 messages that r always up to date
just need json output
seems good
can't we just run a bot that keeps checking the branches and updating it's own messages
well we dont need a bot
u can edit webhooks
we could remove the workflow and move it onto my server
how do you want to run it?
and just run it whenever there's a new deploy
systemd timer?
yeah but how are gonna make it check every 30 seconds
i alr wrote it bro
I just want to know how you did
not like the fetching
but how you are running it
okay I get it now
it just polls these
const (
StableUpdaterUrl = "https://discord.com/assets/version.stable.json"
CanaryUpdaterUrl = "https://canary.discord.com/assets/version.canary.json"
)
so we just need to send the json to the local machine so the script that runs the fetching can access it?
and apply the correct logic
nah
we don't need many changes
just remove the reporter from github actions
my server will run it
or well we could still do it via github actions so my server has less load 
we just need to edit it slightly so it keeps editing the same message instead of posting new ones
although idk if we want history?
what's the oracle bandwidth limit again
we could make it both edit + post new message to some thread
unlimited lol
I want at least to keep a message saying the last hash working 100%
yeah i would say just make a thread with full history
ik upload has a limit
that would be too spammy I think
it would be nice to have a channel with like only 3 or 4 messages that update
well that's where we could dedupe
if it's same as prev message it doesn't post
I see
if it's same message we should maybe just update the hash?
so we are gonna have a message with the latest updated hash of the 100% working
and then other messages with the hash of the latest version where x patches break
but we only update the hashes if the patches failing did not change
I don't know if you understand what I mean
well with this we would have to keep stored the last messages ids and it's broken stuff
to avoid having to re fetch
store like last 6 messages ids and it's broken stuff -> test new version -> if broken stuff matches update message id hash of the one that matches -> if it doesn't delete the oldest message id and post a new


