User talk:Zach386x

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia

Welcome!

Hello, Zach386x, and welcome to Wikipedia! Thank you for your contributions. I hope you like the place and decide to stay. Here are some pages that you might find helpful:

I hope you enjoy editing here and being a Wikipedian! Please sign your messages on discussion pages using four tildes (~~~~); this will automatically insert your username and the date. If you need help, check out Wikipedia:Questions, ask me on my talk page, or ask your question on this page and then place {{help me}} before the question. Again, welcome!--MollyPollyRolly (talk) 01:15, 27 July 2021 (UTC)[reply]

Adding of B720 to List of road routes in Victoria article[edit]

Heya,

Apologies, but I had to remove this listing for the following reasons: that B720 on Bridge Inn Road is just that sign, at that intersection: there's no other signs along the entire route (either Bridge Inn Road or Yan Yean Road) that show B720, so we don't have any idea of its actual end-point or routing. Also, B675 was added because it was listed in SRNS, B720 currently is not, doesn't have any other reliable sources.....it's much like the A21 situation along South Gippsland Highway. Should more B720 signs appear, to better suggest its actual routing - I spotted many coverplates on Yan Yean Road, so I suspect this will it), this can certainly be re-added. Just wanted to let you know why I reverted one of your changes, hope you understand? Please let me know if you have any further questions? Lordstorm (talk) 14:26, 1 November 2021 (UTC)[reply]

@Lordstorm: Hey no worries. I guess B675 was a bad example, a better one would have been A60, as like B720 it's not listed on the SRNS (still showing ALT1), we still don't know the end point routing (eg. Will it transfer to C101 at Monash Fwy or the Princes Link Hwy, Will it extend up Bulla Rd to M2, Will it follow different routing through the city?) and A60 has only been spotted on a handful of signs, the vast, vast majority are still showing SR60/ALT1 (including major transfers such as EastLink, M1/Kings Way and M2/Flemington Rd in which there is zero evidence of A60). I used to travel down Bridge Inn Rd everyday for work and the only evidence of SR57 even back then was a few trailblazers at Yan Yean Rd and maybe a few signs at Orchard Rd and Bassets Rd, so based on that I thought even the 3 or so B720 signs released at Plenty Rd would be close to 50%! But completely understand the removal as more info is probably needed. I was also confident that B720 would end at Plenty Road as one of the signs actually shows END B720 so that's why I only updated Bridge Inn Rd and not the rest of SR57. Zach386x (talk) 01:13, 2 November 2021 (UTC)[reply]

Your submission at Articles for creation: Yan Yean Road, Melbourne has been accepted[edit]

Yan Yean Road, Melbourne, which you submitted to Articles for creation, has been created.

Congratulations, and thank you for helping expand the scope of Wikipedia! We hope you will continue making quality contributions.

The article has been assessed as Start-Class, which is recorded on its talk page. Most new articles start out as Stub-Class or Start-Class and then attain higher grades as they develop over time. You may like to take a look at the grading scheme to see how you can improve the article.

Since you have made at least 10 edits over more than four days, you can now create articles yourself without posting a request. However, you may continue submitting work to Articles for creation if you prefer.

If you have any questions, you are welcome to ask at the help desk. Once you have made at least 10 edits and had an account for at least four days, you will have the option to create articles yourself without posting a request to Articles for creation.

If you would like to help us improve this process, please consider leaving us some feedback.

Thanks again, and happy editing!

Whiteguru (talk) 10:32, 6 December 2021 (UTC)[reply]

ArbCom 2022 Elections voter message[edit]

Hello! Voting in the 2022 Arbitration Committee elections is now open until 23:59 (UTC) on Monday, 12 December 2022. All eligible users are allowed to vote. Users with alternate accounts may only vote once.

The Arbitration Committee is the panel of editors responsible for conducting the Wikipedia arbitration process. It has the authority to impose binding solutions to disputes between editors, primarily for serious conduct disputes the community has been unable to resolve. This includes the authority to impose site bans, topic bans, editing restrictions, and other measures needed to maintain our editing environment. The arbitration policy describes the Committee's roles and responsibilities in greater detail.

If you wish to participate in the 2022 election, please review the candidates and submit your choices on the voting page. If you no longer wish to receive these messages, you may add {{NoACEMM}} to your user talk page. MediaWiki message delivery (talk) 01:23, 29 November 2022 (UTC)[reply]

ArbCom 2023 Elections voter message[edit]

Hello! Voting in the 2023 Arbitration Committee elections is now open until 23:59 (UTC) on Monday, 11 December 2023. All eligible users are allowed to vote. Users with alternate accounts may only vote once.

The Arbitration Committee is the panel of editors responsible for conducting the Wikipedia arbitration process. It has the authority to impose binding solutions to disputes between editors, primarily for serious conduct disputes the community has been unable to resolve. This includes the authority to impose site bans, topic bans, editing restrictions, and other measures needed to maintain our editing environment. The arbitration policy describes the Committee's roles and responsibilities in greater detail.

If you wish to participate in the 2023 election, please review the candidates and submit your choices on the voting page. If you no longer wish to receive these messages, you may add {{NoACEMM}} to your user talk page. MediaWiki message delivery (talk) 00:46, 28 November 2023 (UTC)[reply]