User talk:BusFan74

From SgWiki
Revision as of 15:59, 18 January 2025 by Supernutorcrazy (talk | contribs)
Jump to navigation Jump to search

Dear BusFan74,

Instead of reverting your edits, I helped synchronised the other pages you didn’t have the chance to because to your autoblock. In case this were to happen again, do feel free to drop by my talk page and request for help.

Thanks and regards,

TIB832Z

Dear TIB832Z

Thanks. Very much appreciated in case if this happens to me again in some of the time while editing and synchronised other relevant pages here.

Regards BusFan74

Re: Autoblock

It had been resolved. Existing user affected by autoblock can just approach any admin talk page to request for the autoblock removal by stating the id. It is not required to wait for the block to lapsed.

Oh ok. Just clarifying my doubts

Bus ad update

Hi if there ad updates, can just put on my talk page, because I am interested in the latest bus ad updates. and I do have a personalised mobile bus deployments on my phone then can update there as well.

Buses with Gali Batu card (GB): Add-ons

Hi BusFan74,

23ispolo here. I came across your own compilation of SMRT buses with the GB card on your talk page.

I would like to mention that I spotted the following buses with the GB card:

SMB320L
MAN NL323F

SMB99B
Mercedes-Benz OC500LE

If I may be allowed, it would be my pleasure to help with updating your compilation whenever I spot more buses with the GB card.

Thank you!

Regards,
23ispolo

Hi,

Thank you for your information regarding to more buses with GB card spotted, you can edit my user anytime if you see more of KJDEP buses with GB card. I hope that helps. I will update that as well.

Regards BusFan74

Opinion

Hi,

I would like to seek your opinion on the following proposed changes:

1. Launch of sgWiki Bus Spotting Page A new page will be created daily and automatically deleted a month later. For example, "Bus Spotting/1 February 2025" would be removed on 1 March 2025. This page is intended to allow editors to document bus registration numbers without the typical edit limitations, enabling infinite edits.

The primary objective is to encourage collaboration among editors and to improve the accuracy of bus deployment data in relation to their permanent services. Many users have noted that the deployment page contains inaccurate and outdated information. By using these pages, we aim to track bus operations more effectively and allocate the correct permanent services, without requiring editors to board the buses to verify duty schedules.

2. Use of Subpages for Bus Model Deployment I have received considerable feedback, mostly criticism, regarding the separation and consolidation of bus advertisements across models. Most complaints focus on advertisement changes rather than deployment accuracy, which contributes to the aforementioned inaccuracies. As such, I propose reorganising the Bus Model deployment using subpages as follows:

Example: Volvo B9TL (WEG Batch 2) will be divided into four subpages:

  1. Volvo B9TL (Wright Eclipse Gemini 2) (Batch 2)/Page 1 – (Low Entry, SBS7700T – SBS7729L)
  2. Volvo B9TL (Wright Eclipse Gemini 2) (Batch 2)/Page 2 – (Low Floor, SBS3000G – SBS3099Y)
  3. Volvo B9TL (Wright Eclipse Gemini 2) (Batch 2)/Page 3 – (Low Floor, SBS3100B – SBS3199S)
  4. Volvo B9TL (Wright Eclipse Gemini 2) (Batch 2)/Page 4 – (Low Floor, SBS3200X – SBS3238M & SBS3269Z)

A navigation bar will be added at the top and bottom of each page, linking the respective subpages. Each page will feature a single table listing up to 100 buses, organised in the following format:

Registration No/Livery | Operator/Current Deployment | Advertisement | Former Deployment

This approach seeks to balance different perspectives, and to be more mobile friendly, as I am uncertain why some users are strongly opposed to these changes.

Alternative Table Layouts:

  1. Registration No/Livery | Operator/Current Deployment | Former Deployment (Maintain status quo)
  2. Batch | Registration No/Livery | Operator/Current Deployment | Former Deployment (Merging of Batches, numerical order, maintain status quo)
  3. Batch | Registration No/Livery | Operator/Current Deployment | Advertisement | Former Deployment (Merging of Batches, numerical order)

Please let me know your thoughts on these proposals. Thank you for your time and feedback.

Regards, Supernutorcrazy