Graham Schodde

Graham Schodde (born 19 June 1958) is a former Australian rules footballer who played with St Kilda in the Victorian Football League (VFL).[1]

Graham Schodde
Personal information
Full name Graham Schodde
Date of birth (1958-06-19) 19 June 1958
Original team(s) North Albury
Height 182 cm (6 ft 0 in)
Weight 79 kg (174 lb)
Position(s) Wing
Playing career1
Years Club Games (Goals)
1980 St Kilda 5 (2)
1 Playing statistics correct to the end of 1980.
Sources: AFL Tables, AustralianFootball.com


Notes
  1. Holmesby, Russell; Main, Jim (2014). The Encyclopedia of AFL Footballers: every AFL/VFL player since 1897 (10th ed.). Seaford, Victoria: BAS Publishing. p. 791. ISBN 978-1-921496-32-5.
gollark: It could record locally and upload later, though.
gollark: This person apparently reverse-engineered it statically, not at runtime, but it *can* probably detect if you're trying to reverse-engineer it a bit while running.
gollark: > > App behavior changes slightly if they know you're trying to figure out what they're doing> this sentence makes no sense to me, "if they know"? he's dissecting the code as per his own statement, thus looking at rows of text in various format. the app isn't running - so how can it change? does the app have self-awareness? this sounds like something out of a bad sci-fi movie from the 90's.It's totally possible for applications to detect and resist being debugged a bit.
gollark: > this is standard programming dogma, detailed logging takes a lot of space and typically you enable logging on the fly on clients to catch errors. this is literally cookie cutter "how to build apps 101", and not scary. or, phrased differently, is it scary if all of that logging was always on? obviously not as it's agreed upon and detailed in TikTok's privacy policy (really), so why is it scary that there's an on and off switch?This is them saying that remotely configurable logging is fine and normal; I don't think them being able to arbitrarily gather more data is good.
gollark: > on the topic of setting up a proxy server - it's a very standard practice to transcode and buffer media via a server, they have simply reversed the roles here by having server and client on the client, which makes sense as transcoding is very intensive CPU-wise, which means they have distributed that power requirement to the end user's devices instead of having to have servers capable of transcoding millions of videos.Transcoding media locally is not the same as having some sort of locally running *server* to do it.


This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.