0.4.7.x will be EOL on 2024-01-31. We should do the usual dance of notifying relay operators who still have not upgraded by then and then reject the relays/bridges from the network.
Does that mean we, the directory authorities, should start un-recommending these versions now?
Or maybe rather: does eol mean this is the beginning of trying to notify people that they should upgrade, or does eol mean this is when we start not wanting them to still be running?
Does that mean we, the directory authorities, should start un-recommending these versions now?
I don't think so. It's fine IMO if we push a respective commit at the day Tor versions go actually EOL.
Or maybe rather: does eol mean this is the beginning of trying to notify people that they should upgrade, or does eol mean this is when we start not wanting them to still be running?
This is not exclusive, so I'd say both, depending on what you mean. For instance, I've sent a public service announcement to our tor-relays mailing list yesterday, indicating that it would be very nice if no relay or bridge would be on 0.4.7.x on 2024-02-01 anymore. However, taking past experiences into account, this very likely won't happen. Thus, we use the EOL date to start collecting information about not yet upgraded relays or bridges and nagging respective operators or doing social media campaigns etc..
FWIW, we agreed on our network-health sync on Monday to start with collecting EOL info and reaching out to operators in the week of 2023-02-19. @gus will do some outreach on social media etc. before that.
Focusing on relays right now, attached are the .csv files with and without contact information. For the contact information part this leaves us with 628 relays, which means roughly 300 relays for @gus and me (note: there are still a bunch of bogus contact information and families included in the data, so the actual amount of emails to be sent (while still high) is lower).
@gus: I can take the first half and you the second?
AD56555C3CCCE9EA49872967B0C90F169E7EB753,myNickName2,no-body@example.com,0.4.7.10,,6007EF215FA156F200B634CC83BD76BB2D563DAA,t00r,nice try,0.4.7.10,,E4A17C156ECD4E450DC15233B4724E1D51175E5D,AATorRelay,not@re.al,0.4.7.13,,FBD40937C6E1523CA717036FC4FD5ECC832A93B7,nononicetry,nicetrynono@gmail.com,0.4.7.7,,EA6F18C4D5588159969A49F6C13AB56E28502D83,Unnamed,your mom at your house in my pants,0.4.7.16,,460DD7292569D1276C50E2536C47677D739C4661,fremont,your@e-mail,0.4.7.13,,D80F322CAF47D89324E42AF56209B5E8607103FF,myNiceRelay,your@e-mail,0.4.7.13,,550F8C238D36F6117F319817CC3BF16D23FC8555,undisclosed,undisclosed@undisclosed.undisclosed,0.4.7.8,,395E279217D4DA98E458E723F4C2F1BCDCF9A8C2,tor,unknown,0.4.7.8,,6F32594A7A1E6D43290CCF7FA2289FB5234B1810,toreeka,unknown,0.4.7.8,,15AE6FFE0E245A820D4F74EA64B4C304EE555C1D,5b82I0IfxsHI7ekh,tor-operator@your-emailaddress-domain,0.4.7.11,,0853576E12BA9CD473254FAFF820BD4699E22077,theactualNSA,faker@email.spr,0.4.7.16,,06FED88BF954615FC636C8B74EDC48DDA2001355,Spacestone1,null,0.4.7.16,,467220318E152A4EBEFC0E3A3F7ED05A08098C54,Crazystone1,null,0.4.7.16,,A092C1D49ECEB9C48657851BA2224933D0C41ADB,Spacestone1,null,0.4.7.16,,7FF192FF74267E6636F23ECFFB62A4B342417ED3,iambaidu,i.am.baidu,0.4.7.13,,4A4E6C40307D7670016EF01FA443B9DD19AA1F96,redhead3,none@blahblahblah.com,0.4.7.16,,EE9FFFB8FC1B120275BDDAFBC0BCBD98C8E7D532,GetYourOwnRelay,no@thank.you,0.4.7.13,,8BBE474111CD55562945D0E4B15709382E8C1298,aquamarine,nobody@nowhere.local,0.4.7.13,,ECD18351D9BA04E1F4055084BA8C6DF19DAF339D,need4speed,tor4@example.org,0.4.7.13,,915E9786806C93BC984CEF2C00F62218A48EB8A7,myRelay,mail@domain.com,0.4.7.13,,D01DEAC9ABA986CF0DDB2E4FF9997D01149BDBF2,FootPedal2,mail@domain.com,0.4.7.13,,EE3D77F49C119FAD11C3AB17A24DE9EE08118C38,TofuTor,mail@domain.com,0.4.7.13,,8FBA0648AA281EAAC510873ED8FAB3278E1EFA1D,PhilTorRelay,t.me/philosof,0.4.7.16,,6E9FE14123B8E7F91F0FBC7B2B6A08CC15063F58,zankoku,tbc@example.com,0.4.7.16,,21FFF594CFE691A4A03B828E9597A9F74F878053,Woodman,tbd [tor-relay.co],0.4.7.13,,FA4D02F71E5B59DA43EB98BC9694875154FAF6FE,p8miz7ttgr5,me@example.com,0.4.7.7,,
Let's start with contacting bridge operators. Attached are the .csv files with and without contact information. This leaves us with 514 bridges with some sort of contact information. @gus: I'll do the first half again and you the second?