I CREATED A SPREADSHEET LISTING ALL ~728,000 RUNS ON SRC THAT LINKED TO TWITCH. PLEASE SHARE OR SOMETHING. DATA/README CAN BE FOUND HERE: github.com/Artemis6425/... - ThreadSky

artemis.sm64.live • 3 days ago

I CREATED A SPREADSHEET LISTING ALL ~728,000 RUNS ON SRC THAT LINKED TO TWITCH. PLEASE SHARE OR SOMETHING. DATA/README CAN BE FOUND HERE:

https://github.com/Artemis6425/at-risk-vods

Comments

l0g1c-b1t.bsky.social•11 hours ago

Crazy how much history is in jeopardy of being lost thanks to this awful decision. Thanks for the effort you have put in on this. Currently (slowly) migrating everything over to youtube myself.

artemis.sm64.live•3 days ago

The 2nd sheet was private, that is now fixed :)

artemis.sm64.live•2 days ago

NOTE: There was an issue with gathering some of this data, TLDR it overcalculates some people's numbers, and marks some users as "AT RISK" when really they are not. This will be fixed by tonight!

artemis.sm64.live•2 days ago

IMPORTANT: While I am fixing the above still, the Twitch API requests do NOT account for any unpublished/private highlights. This means that regardless of what the sheet may say, some runs may still be at risk. Please back up any important runs, regardless of their "status"!!!!

artemis.sm64.live•2 days ago

https://bsky.app/profile/artemis.sm64.live/post/3ljdk37k5hc2o

THIS ISSUE IS FIXED AS OF RIGHT NOW. PLEASE USE THE NEW SPREADSHEET LINKS!

artemis.sm64.live•1 day ago

AS OF 30 SECONDS AGO I ADDED CODE THAT YOU CAN USE TO MAKE YOUR OWN GAME-SPECIFIC CSV FILES. GOOD LUCK

darktwinge.bsky.social•2 days ago

Nice work!

Dunno if reporting specific oddities matters, but in case it is indicative of a wider issue: There's a Donkey Kong Tropical Freeze Run listed under 'DarkTwinge' as the runner on the spreadsheet when it should be 'JockeMS' (Sheet 1)

artemis.sm64.live•2 days ago

Interesting! I looked at it, and the issue is not something I can really account for. TLDR, the link is old enough to live through twitch's ID change. it USED to be 5484880, and now it's 44884215. and somehow, that original 5484880 got changed to one of your VODS.

I have no idea why twitch did that

sharkie.bsky.social•2 days ago

First, thank you very much for your work and your efforts.

These are the second largest CSV files I’ve ever seen. It’s really impressive.

a2rhombus.bsky.social•2 days ago

girl you're a legend

wesdog.bsky.social•1 day ago

GOATed shit right here

madmegax381.bsky.social•2 days ago

This is awesome, thank you!! 💜

matse007.bsky.social•1 day ago

A small problem is that communities already started the archiving process. Could you share the code that communities could create their own up to date csv's?

artemis.sm64.live•1 day ago

the highlight check was done yesterday so that part is as up-to-date as it can be

that said, im not gonna release the current code cuz its shit but when im less burnt out ill make a better tool for individual boards

matse007.bsky.social•1 day ago

I dont think anyone minds messy code, especially the community can contribute on it and fix stuff. Or you can put a disclaimer up for it. Especially when you are burnt out I think its a good call to just release it, people can then work from that point on so you can take a break.

artemis.sm64.live•1 day ago

still burnt out but added rewritten code designed for exactly what you asked for, hope it helps :)

bucklepants.co.uk•2 days ago

YOU DROPPED THIS

caysekong.bsky.social•2 days ago

The Fucking GOAT

kalarse.bsky.social•2 days ago

nice one, tho saw 2 runs of mine which got flagged due the twitch vod being on the comment/description while the actual upload is from yt :)

artemis.sm64.live•2 days ago

I didn't want to just blanket say all runs that had twitch and youtube links were safe, because I am familiar with multiple instances where they aren't the same exact video. Better safe than sorry :)

kalarse.bsky.social•2 days ago

understandable, felt safe to do a double check :)
thanks for the work

xel.reallyreally.live•3 days ago

2nd spreadsheet is set to private.

artemis.sm64.live•3 days ago

fixed now!

yorkie.speedrun.moe•2 days ago

What timescale did you pull this from? My runs are listed as AT RISK but i'm under the highlight cap now and have been since about 12 hours after the cap was announced

thefiz.online•2 days ago

They didn’t look at the cap. They just looked at every run that was linked to twitch as a primary video source.

yorkie.speedrun.moe•2 days ago

I thought i'd read all the github, apparently not, but now I found my own answer as well lol. Must've been caught whilst my cap was still being reduced.

yorkie.speedrun.moe•2 days ago

Also they state they did in their methodology.

thefiz.online•2 days ago

Fair, I would consider everything on twitch to be at risk though

artemis.sm64.live•2 days ago

Long term, of course, this is more specifically for the announcement they made

yorkie.speedrun.moe•2 days ago

They have the "Total Highlight" field in the spreadsheet which is how things are categorised as "AT RISK" or "SAFE"

artemis.sm64.live•2 days ago

Unfortunately I found an issue with thanks to you and a few others mentioning, which counted more than just highlights (like it was supposed to). I'm currently re-running the data and will have it all updated by tonight. Thank you for calling that out!

yorkie.speedrun.moe•2 days ago

Just updating here as well because apparently I just glossed over this in the Github.

Comments

Posting Rules

Reply