User talk:TTEDC - Revision history

Supernutorcrazy at 12:57, 4 September 2025

2025-09-04T12:57:35Z

← Older revision		Revision as of 20:57, 4 September 2025
Line 55:		Line 55:

	I have no words to say, but if you can reply feel free		I have no words to say, but if you can reply feel free

			==Disrupting sgWiki users==
			Hi,

			I had noticed the growing disruptive user editing in sgWiki, but unfortunately, I was given a "ban" by [[User:Kimminju\|@Kimminju]] for saying I abusing my admin right to disrupt the editing and should focus on sgWiki @ Miraheze. I seek your understanding that I will not be able to
			# delete any sgwiki Buses Main Page (except for the pages due for migration)
			# ban any user
			# revert/edit/correct/sync deployments pages

			Therefore, I will be focusing on proper data control and syncing to sgWiki @ Miraheze.

			Please wait for other admins to support your request.

			Thank you for your understanding.

			Regards

			[[User:Supernutorcrazy\|Supernutorcrazy]] ([[User talk:Supernutorcrazy\|talk]]) 20:57, 4 September 2025 (+08)

InquisitorViolator7533: /* Regarding images with watermark */ new section

2025-03-18T03:00:37Z

Regarding images with watermark: new section

← Older revision		Revision as of 11:00, 18 March 2025
Line 43:		Line 43:
	Regards,		Regards,
	svc135bsoe		svc135bsoe

			== Regarding images with watermark ==

			Hi, since you mentioned in the talk page of the Buses page that LTG welcomes non-commercial use of photos, it affects the infobox, which can be involved in the Google search results.

			And Flickr images does not have a fine line, even when uploading with credit mentioned in the link and adding an author next to a link might have a fine line of that.

			You can look here as if the file had a credited link:

			[[File:SBS8903T 48.jpg\|thumb\|centre\|300px]]

			I have no words to say, but if you can reply feel free

Svc135bsoe: /* 129A/B as part of BCEP */

2025-01-27T14:08:34Z

129A/B as part of BCEP

← Older revision		Revision as of 22:08, 27 January 2025
Line 39:		Line 39:
	Hi,		Hi,

	I noticed you removed 129A and 129B from the BCEP list. According to this LTA press release (https://www.lta.gov.sg/content/ltagov/en/newsroom/2024/12/news-releases/growing-singapore-s-bus-network-with-the-bus-connectivity-enhanc.html), 129A and B are indeed part of the BCEP. Hence, I apologise but will have to revert your edit. I hope you understand and will not take offence.		I noticed you removed 129A and 129B from the BCEP list. According to this LTA press release (https://www.lta.gov.sg/content/ltagov/en/newsroom/2024/12/news-releases/growing-singapore-s-bus-network-with-the-bus-connectivity-enhanc.html), 129A and B are indeed part of the BCEP. Hence, I apologise but will have to revert your edit. I hope you understand and will not take offence. :)

	~~Aside from that, thanks for helping me finish up the modification of interchanges and terminals listing~~. :)

	Regards,		Regards,
	svc135bsoe		svc135bsoe

Svc135bsoe: /* 129A/B as part of BCEP */

2025-01-27T14:07:49Z

129A/B as part of BCEP

← Older revision		Revision as of 22:07, 27 January 2025
Line 39:		Line 39:
	Hi,		Hi,

	I noticed you removed 129A and 129B from the BCEP list. According to this LTA press release (https://www.lta.gov.sg/content/ltagov/en/newsroom/2024/12/news-releases/growing-singapore-s-bus-network-with-the-bus-connectivity-enhanc.html), 129A and B are indeed part of the BCEP. Hence, I apologise but will have to revert your edit. I hope you understand and will not take offence. :)		I noticed you removed 129A and 129B from the BCEP list. According to this LTA press release (https://www.lta.gov.sg/content/ltagov/en/newsroom/2024/12/news-releases/growing-singapore-s-bus-network-with-the-bus-connectivity-enhanc.html), 129A and B are indeed part of the BCEP. Hence, I apologise but will have to revert your edit. I hope you understand and will not take offence.

			Aside from that, thanks for helping me finish up the modification of interchanges and terminals listing. :)

	Regards,		Regards,
	svc135bsoe		svc135bsoe

Svc135bsoe: /* 129A/B as part of BCEP */ new section

2025-01-27T14:06:55Z

129A/B as part of BCEP: new section

← Older revision		Revision as of 22:06, 27 January 2025
Line 34:		Line 34:

	Regards, Supernutorcrazy		Regards, Supernutorcrazy

			== 129A/B as part of BCEP ==

			Hi,

			I noticed you removed 129A and 129B from the BCEP list. According to this LTA press release (https://www.lta.gov.sg/content/ltagov/en/newsroom/2024/12/news-releases/growing-singapore-s-bus-network-with-the-bus-connectivity-enhanc.html), 129A and B are indeed part of the BCEP. Hence, I apologise but will have to revert your edit. I hope you understand and will not take offence. :)

			Regards,
			svc135bsoe

Supernutorcrazy: /* Opinion */

2025-01-25T06:42:07Z

Opinion

← Older revision		Revision as of 14:42, 25 January 2025
Line 19:		Line 19:
	Hi,		Hi,

	~~I would like to seek~~ your ~~opinion~~ on the ~~following~~ proposed changes:		Thank you for sharing your feedback on the proposed changes earlier. I am pleased to inform you that the bus spotting page has been launched, which I believe will assist editors in verifying deployment accuracy and enhancing the reliability of current deployment information.

	~~1. Launch~~ of ~~sgWiki Bus Spotting Page~~		To address concerns regarding potential false entries on the spotting page, I trust in the integrity of our editors to avoid posting hypothetical or inaccurate information. Additionally, I have implemented features such as Date/Time stamps and Editor attribution to reinforce accountability.
	~~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~~.		Regarding the subpages, I have launched the following: [[Scania K230UB (Euro IV) (Batch 2)]]. Deployment details have been transferred to the respective subpages.

	~~2. Use of Subpages for Bus Model Deployment~~		As a trial, I finalised the layout for the first subpage: [[Scania K230UB (Euro IV) (Batch 2)/1]], incorporating your valuable feedback.
	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:~~		Please confirm if the following criteria are met:
	~~# Volvo B9TL (Wright Eclipse Gemini 2) (Batch 2)/Page 1 – (Low Entry, SBS7700T – SBS7729L)~~		# Clear visibility and usability on mobile devices.
	~~# Volvo B9TL (Wright Eclipse Gemini 2) (Batch 2)/Page 2 – (Low Floor, SBS3000G – SBS3099Y)~~		# Ease of information references.
	# ~~Volvo B9TL (Wright Eclipse Gemini 2) (Batch 2)/Page 3 – (Low Floor, SBS3100B – SBS3199S)~~
	# ~~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:~~		If you have additional suggestions for improving the subpage layout, please do not hesitate to share your input. Thank you for your time and constructive feedback.

	~~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:~~
	~~# Registration No/Livery \| Operator/Current Deployment \| Former Deployment (Maintain status quo)~~
	~~# Batch \| Registration No/Livery \| Operator/Current Deployment \| Former Deployment (Merging of Batches, numerical order, maintain status quo)~~
	~~# 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		Regards, Supernutorcrazy

Supernutorcrazy at 08:01, 18 January 2025

2025-01-18T08:01:20Z

← Older revision		Revision as of 16:01, 18 January 2025
Line 15:		Line 15:

	Thanks.		Thanks.

			==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:
			# Volvo B9TL (Wright Eclipse Gemini 2) (Batch 2)/Page 1 – (Low Entry, SBS7700T – SBS7729L)
			# Volvo B9TL (Wright Eclipse Gemini 2) (Batch 2)/Page 2 – (Low Floor, SBS3000G – SBS3099Y)
			# Volvo B9TL (Wright Eclipse Gemini 2) (Batch 2)/Page 3 – (Low Floor, SBS3100B – SBS3199S)
			# 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:
			# Registration No/Livery \| Operator/Current Deployment \| Former Deployment (Maintain status quo)
			# Batch \| Registration No/Livery \| Operator/Current Deployment \| Former Deployment (Merging of Batches, numerical order, maintain status quo)
			# 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

SBS3720L at 07:08, 4 January 2025

2025-01-04T07:08:42Z

← Older revision		Revision as of 15:08, 4 January 2025
Line 3:		Line 3:

	Noted on your concern. I will think of another solution. If you have better solution, please do not hesitate to voice out. As the trial is to reduce the number of columns to make it less clutter, and yet maintain fleet registration still in numerical order, regardless of operators. One such initiative is the implementation of liveries within the registration number column.		Noted on your concern. I will think of another solution. If you have better solution, please do not hesitate to voice out. As the trial is to reduce the number of columns to make it less clutter, and yet maintain fleet registration still in numerical order, regardless of operators. One such initiative is the implementation of liveries within the registration number column.

			==RE: SWD or SKD==

			Hi there, I currently do not have any confirmation of said info. SKD was used because it was changed to SKD by someone else when I put as SWD, back when overnight parking started at Sengkang West in 2024.

			For a more accurate info, I suggest u check the onboard DDU of buses from Sengkang West.

			In any instance if it is SWD, there should be a function to change all at once. If there isn't, can copy and paste into Google docs before finding.

			Hope this helps.

			Thanks.

Supernutorcrazy: Created page with "==Reply== Hi TTEDC, Noted on your concern. I will think of another solution. If you have better solution, please do not hesitate to voice out. As the trial is to reduce the number of columns to make it less clutter, and yet maintain fleet registration still in numerical order, regardless of operators. One such initiative is the implementation of liveries within the registration number column."

2024-12-30T11:38:37Z

Created page with "==Reply== Hi TTEDC, Noted on your concern. I will think of another solution. If you have better solution, please do not hesitate to voice out. As the trial is to reduce the number of columns to make it less clutter, and yet maintain fleet registration still in numerical order, regardless of operators. One such initiative is the implementation of liveries within the registration number column."

New page

==Reply==
Hi TTEDC,

Noted on your concern. I will think of another solution. If you have better solution, please do not hesitate to voice out. As the trial is to reduce the number of columns to make it less clutter, and yet maintain fleet registration still in numerical order, regardless of operators. One such initiative is the implementation of liveries within the registration number column.