#discord update detector

1 messages ยท Page 1 of 1 (latest)

tough spire
#

meow

spark idol
dreamy topazBOT
#

is this thing on

tough spire
#

it do be on

zinc crow
#

meow

spark idol
gloomy hawk
#

also please don't lock this thread

dreamy topazBOT
#

New canary version: 011412995dad4d93eec0899d7d388ac035fe8888

zinc crow
#

WOA

#

i love

gloomy hawk
#

can we get build number too?

tough spire
#

whats the point ๐Ÿ˜ญ

#

use some other tool for that

#

this is just for automatically running reporter

dreamy topazBOT
#

New canary version: 5b1f7dd63babdab908b7fc50051914ed39176cbd

gloomy hawk
#

eh, would be nice so I don't need to subscribe to another service for it

tough spire
#

no

#

out of scope lol

dreamy topazBOT
#

New canary version: 30e4d748b4109e846bb6860496905059ca01e12f

tough spire
#

WTF DISCORD

#

WHY SO MANY PUSHES

zinc crow
#

lmao

#

is canary just their live git repo

#

i would assume it rolls out in batches

gloomy hawk
dreamy topazBOT
#

New canary version: 3b703fdcdce81009b657817e30b19d9e5eb2e1c4

gloomy hawk
#

I am running 2 updates old canary now blobcatcozy

#

and I reloaded less than 10 minutes ago

tough spire
#

how tf do they push this much man

gloomy hawk
#

why the fuck does discord ptb exist

#

its just canary

tough spire
#

theyl iterally have discord staging

gloomy hawk
#

i refuse to believe

gloomy hawk
#

does discord have such thing as an update queue?

gloomy hawk
dreamy topazBOT
#

New canary version: 0e0437ce41f50293d4cec75ff38dd4ed2a08eab1

gloomy hawk
#

WHAT ARE THEY COOKING?

gloomy hawk
#

horror

dreamy topazBOT
#

New canary version: b9d5310a99ca43411596d2b52bdffeb274f470a8

gloomy hawk
#

can you stop

dreamy topazBOT
#

New canary version: e2e86b89cf06dd595be085da61aac850bfc71a62

robust goblet
#

they dont rly test client stuff on stg

tough spire
robust goblet
gloomy hawk
#

did they break

#

fuck you discord blobcatcozy

keen lagoon
#

the messenger of impending doom

gloomy hawk
zinc crow
#

UH OH

gloomy hawk
#

why does it have to happen when I want to show my friend some plugin I built recently trolley

keen lagoon
#

didcord i beg of you

gloomy hawk
#

@fair crescent can you cook for us

fair crescent
#

oh hell nah

#

not again

gloomy hawk
#

discord fucked up canary

#

wreq cant be found

#

vencord is still loading patches, it just can't apply them

fair crescent
#

are you sure you are up to date

#

it's still working

gloomy hawk
#

on canary?

fair crescent
#

yes

#

I'm not gonna lie it's almost impossible for it to fail now

gloomy hawk
#

am I just stupid?

#

0 days since going literally insane because I forgot to do something obvious

#

so sorry trolley

fair crescent
#

did you stop working on this @tough spire

tough spire
#

for now ye

#

needs some changes to reporter if u wanna implement them

fair crescent
#

what needs to change?

tough spire
#
  1. need to be able to dispatch only one branch
  2. i want to dedupe, so if something was already reported before it won't be reported again
  3. 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

fair crescent
tough spire
#

basically i want to run it whenever there is new stable or canary and then only report new stuff

fair crescent
#

it only sends canary and stable because we run on both

tough spire
#

so we see breakages immediately without getting spammed

fair crescent
#

ahh

#

I don't quite get 3

tough spire
#

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

fair crescent
#

seems good

tough spire
#

btw do we even still need to login?

#

i think it might work without

fair crescent
#

unsure actually

#

might produce more errors so have to test

tough spire
#

anyway what do u think?

#

wait

#

we don't even need any changes

fair crescent
#

can't we just run a bot that keeps checking the branches and updating it's own messages

tough spire
#

well we dont need a bot

#

u can edit webhooks

#

we could remove the workflow and move it onto my server

fair crescent
#

how do you want to run it?

tough spire
#

and just run it whenever there's a new deploy

fair crescent
#

systemd timer?

tough spire
#

nah

#

fetch version every 30 seconds

#

if version is new, run

fair crescent
#

yeah but how are gonna make it check every 30 seconds

tough spire
#

i alr wrote it bro

fair crescent
#

I just want to know how you did

#

not like the fetching

#

but how you are running it

tough spire
#

on my server

fair crescent
#

okay I get it now

tough spire
#

it just polls these

const (
    StableUpdaterUrl = "https://discord.com/assets/version.stable.json"
    CanaryUpdaterUrl = "https://canary.discord.com/assets/version.canary.json"
)
fair crescent
#

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

tough spire
#

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 trolley

#

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?

fair crescent
#

what's the oracle bandwidth limit again

tough spire
#

we could make it both edit + post new message to some thread

tough spire
fair crescent
tough spire
#

yeah i would say just make a thread with full history

fair crescent
fair crescent
tough spire
#

but its fine

fair crescent
#

it would be nice to have a channel with like only 3 or 4 messages that update

tough spire
#

if it's same as prev message it doesn't post

fair crescent
#

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