User talk:Alphabetlorefan1: Difference between revisions

From SgWiki
Jump to navigation Jump to search
 
(33 intermediate revisions by 6 users not shown)
Line 14: Line 14:
[[File:SG5023P 21.jpg|thumb|centre|250px]]
[[File:SG5023P 21.jpg|thumb|centre|250px]]


== SBS8215X, SBS8217R & SBS8218M ==
==Bus Redeployments (TBC)==
Note: This is a section where I have spotted buses that it's redeployed to another service as seen 2 or 3 times by suspect. I cant confirm it either yet until I have spotted it again. Editors can also help me with this, even if it is confirmed, leave a reply here. Thanks. Here are the suspected redeployments:


Hi, Sorry about this for I put AWBDR because I do observed that got several buses layup about few days or a week before the actual deregistration date. I will take note of the observation first before putting AWBDR next time. Thanks.
*SMB1376U - GBDEP 188 > GBDEP 61 (SMB1376U was spotted 4 times on a same slot since 26 March, spotted it again yesterday, but its still suspected)
*SG3357P - GBDEP 970 > GBDEP 188 (KIV other SG335x BYDs are out of 970. Some of these buses also redeployed to 188 or another svc, like SG3353A)
===Others===
* '''Suspected crossover from 35 to 7 (35x7 Crossover)''': Can someone help me check if the 35x7 crossover exist? Because today I saw one bus of the same rego on 35 and 7. Likely, SG6169X, I spotted the bus on 35 around 1pm at Bedok Interchange and later when I was at Dhoby Ghaut at 7pm, SG6169X is now on 7 heading towards Bedok. I know this bus rego perms 168, to replace one of the 35 perm, but help me verify if this crossover exists. It's highly suspected


Noted.
==Disrupting sgWiki users==
Regards,
Hi,


[[User:CurryGreenLine|CurryGreenLine]] ([[User talk:CurryGreenLine|talk]] 17:20, 5 June 2025 (+08)
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


==Sync of Bus Fleet Rule==
Therefore, I will be focusing on proper data control and syncing to sgWiki @ Miraheze.
Hi,


Please refer to this: [[SgWiki:Guidebook/sgWiki_Buses]]. The rule in enforced since early 2010s, and was governed by Apex-LW'21 and SMB315C. Punishment awarded is as followed:
Please wait for other admins to support your request.
*Apex-LW'21: Perma Ban
*SMB315C: Perma Ban
*Supernutorcrazy: Warning Point


Please do not accuse me as I am just enforcing the legacy rule. Like you mention, I do not have the right to repel this rule, but can streamline it to make it easier (reduces the number of pages to edit).
Thank you for your understanding.


Regards
Regards


[[User:Supernutorcrazy|Supernutorcrazy]] ([[User talk:Supernutorcrazy|talk]]) 17:50, 9 June 2025 (+08)
[[User:Supernutorcrazy|Supernutorcrazy]] ([[User talk:Supernutorcrazy|talk]]) 20:58, 4 September 2025 (+08)


== Table ==
== Growing number of advertising accounts with unsafe links ==
Was just testing out if its feasible to display the former fleet. Would be nice to display them if we had more information. If anything you may go ahead and take down the former fleet section. I'm fine with that too.


== Autoblock ID #32164 ==
Hi,


While I cannot edit, here are some things that are updated as of 27 Jun 2025 which will be edited at a later date:
Do I just remove the unsafe link from the userpage or all the content like what you did?

Latest revision as of 19:46, 27 April 2026

About Me

Hey, its Alphabetlorefan1. If you have any questions or any necessary stuff, you can leave it here until I respond. But wait, before you leave a message here, read this first:

  1. No spamming
  2. Be respectful to me
  3. Do not type any nonsense messages
  4. If I did not reply to your message, that means I am busy
  5. Don't troll me

Do take note that I will be deleting messages after 2 weeks.

Thanks

Bus Redeployments (TBC)

Note: This is a section where I have spotted buses that it's redeployed to another service as seen 2 or 3 times by suspect. I cant confirm it either yet until I have spotted it again. Editors can also help me with this, even if it is confirmed, leave a reply here. Thanks. Here are the suspected redeployments:

  • SMB1376U - GBDEP 188 > GBDEP 61 (SMB1376U was spotted 4 times on a same slot since 26 March, spotted it again yesterday, but its still suspected)
  • SG3357P - GBDEP 970 > GBDEP 188 (KIV other SG335x BYDs are out of 970. Some of these buses also redeployed to 188 or another svc, like SG3353A)

Others

  • Suspected crossover from 35 to 7 (35x7 Crossover): Can someone help me check if the 35x7 crossover exist? Because today I saw one bus of the same rego on 35 and 7. Likely, SG6169X, I spotted the bus on 35 around 1pm at Bedok Interchange and later when I was at Dhoby Ghaut at 7pm, SG6169X is now on 7 heading towards Bedok. I know this bus rego perms 168, to replace one of the 35 perm, but help me verify if this crossover exists. It's highly suspected

Disrupting sgWiki users

Hi,

I had noticed the growing disruptive user editing in sgWiki, but unfortunately, I was given a "ban" by @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

  1. delete any sgwiki Buses Main Page (except for the pages due for migration)
  2. ban any user
  3. 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

Supernutorcrazy (talk) 20:58, 4 September 2025 (+08)

Growing number of advertising accounts with unsafe links

Hi,

Do I just remove the unsafe link from the userpage or all the content like what you did?