BetaWiki:Community portal/Archive 2

How do we list periodical releases?
Because, as we know, Microsoft will now release Windows versions in a gradual system, but now the Threshold Wave 2 and Redstone builds are listed on the Windows 10 page. Should we do like BA and make separate pages for Windows:10:TH2 and Windows:10:RS1? Tau Ceti ~  Windows 10 in 640K!  01:05, 13 June 2016 (BST)

Support

 * 1)  Tau Ceti  ~  Windows 10 in 640K!  04:15, 7 August 2016 (BST)

Discussion
PASSED

Fork
It appears there is a fork of BetaWiki made at Wikia, because here there are apparently 'too many spammers'. Essentially, all the pages are copied from BetaWiki. I don't like this idea, as it just spreads everyone out and leads to less activity here. Tau Ceti ~  Windows 10 in 640K!  09:27, 5 March 2017 (GMT)
 * UPDATE: Also, BillyHatcher2012 is the head admin. (Tau Ceti)

Yeah, but don't bother with it, keep editing here instead. There are many pages missing on that "fork" also. Also, I don't think staff members here would agree with it(don't ask, but hounsell promoted me to an admin again), nor do I. --Ovctvct (talk) 12:03, 5 March 2017 (GMT)
 * I'm not surprised if this is Billy's work. He's probably going to use it for all the fake builds he made. Tau Ceti  ~  Windows 10 in 640K!  09:45, 6 March 2017 (GMT)
 * Idle hands are the devil's playgrou­nd. Just let them operate their cheap wiki. --AlphaBeta (talk) 00:00, 24 March 2017 (GMT)

"BetaWiki hub"
We should probably make a new main page that would link people to the various topics covered on BetaWiki.

My initial concept is the following:



I am putting this concept there so we can discuss making BetaWiki great again. Would love to hear your opinion and suggestions. --AlphaBeta (talk) 18:04, 24 March 2017 (GMT)


 * Excellent. First featured article: Windows:1:DR5. Tau Ceti  ~  Windows 10 in 640K!  23:25, 24 March 2017 (GMT)
 * I plan to start with featuring a beta for a month, as the wiki doesn't really have a lot of articles that we could show off. When that improves, I have no problem with weekly featured betas. --89.29.80.194 08:55, 25 March 2017 (GMT)

Revamping the article naming system
In the last weeks I've been thinking a lot about radically revamping the article naming guidelines, which currently use semicolons to delimitate the operating system name, its version and the build. This system worked great for Windows when there was a major release every 2 years, i.e.:.

This system does not adapt well to the constant updates to Windows 10 flowing from Microsoft in the last two years. Do we consider each update as a separate OS version? Or do we treat them as Service Packs? What about these special server releases that have an NT buildtag as well as a build number of their own? Which one do we use?

The current Infoboxes partially depend on the current naming system. Meanwhile it is nice to have an automatic system, it doesn't save the editor an enormous amount of time as compared to filling the basic information to the template manually, not mentioning the fact the system always struggled with strange names like.

What replacement do I propose? I propose getting rid of the semicolons and relax the naming guidelines a little bit, but still keep a system. Let me first present my suggestion of how would my new system work with the 9431 I mentioned above: 1. Windows 8.1 build 9431 2. Windows 8.1 build 9431 (winmain_bluemp)

Windows 8.1 Preview 6.3.9431.0.winmain_bluemp.130615-1214 9431.0.winmain_bluemp.130615-1214 Windows:8.1:9431:winmain_bluemp

Let's take a look at the first two lines and ignore the rest for now. The basic idea is that the final name that's displayed within the OS gets combined with the magic word "build" and the build number + the revision number if it's not equal to 0 (#1). Obviously that would work as long as there aren't several known builds sharing the same build number. This is where we need to specify the build lab and the suggested way is to mention it in a bracket (#2). Of course, there can even become a situation when we cover two builds with the same number, from the same lab, but with a different build time, which we should solve on an individual basis. I think can count such cases using the fingers of my hand.

Well and how does that fix the Windows 10 problem? We would call them all Windows 10. After all, they're not really different from the original July 2015 RTW. The build article would mention the update it belongs to. By removing the semicolon system it won't look so much out of order. Another issue that this new system would fix is early OS/2, which has different Microsoft and IBM editions. Currently the vendor is mentioned in the middle of a build article name, I believe it should get the prominent place in the front of the article name. We are going to solve that later.

The Proposal
Some guidelines that would govern codenames should be probably added as well, would be nice to search for  and land instantly on. Currently the preferred article comes last in the results.
 * 1) As long as BetaWiki knows about just one build with a said build number + revision, the article would receive a name according to example #1 above. To maintain some degree of consistency, example #2 should redirect to example #1.
 * 2) If BetaWiki knows about two builds with a said build number but from differing labs, the individual build articles would receive their names in accordance with example #2. A disambiguation will reside on a name formed according to example #1.
 * 3) If the build has got an official name, we should redirect it to the main article. Windows 10 Insider Preview redirects to main Windows 10 article.
 * 4) The full buildtag, both including and not including the major and minor version must redirect to the main article. 1175.1's schizophrenia is solved by 1175.1 redirecting to 4.0.1175.1 which would be a disambiguation. Buildtag conflicts between NT and 9x should be solved by disambiguations.
 * 5) The old-fashioned name should redirect to the new article name for compatibility reasons for already existing articles.
 * 6) Windows 1.x, 2.x and early NT 3.1 should be solved on an individual basis. We can't use build numbers when they don't have any.

I hope I expressed my mind well enough, now it's your turn to hate me for this. --AlphaBeta (talk) 23:34, 18 April 2017 (BST)

Support

 * 1) I agree with this. --Ovctvct (talk)
 * 2) This is actually a very sane proposal, and I agree with this as well. I did have a few doubts about post-RTM builds, but these were cleared up elsewhere. Recycle.bin (talk) 19:09, 22 April 2017 (BST)
 * 3) Done.  Tau Ceti  ~  Windows 10 in 640K!  01:26, 25 April 2017 (BST)

Broken gallery in articles
In a lot of pages the gallery is broken because it should be like this:

or it will be broken. Anyone who finds such an article please try to fix it. Thanks. --Ovctvct (talk)


 * Will do. -LilShootDawg (talk) 19:15, 3 October 2017 (BST)

We got a wiki copying us
This wiki only has one user who does nothing but completely copys and paste content of this wiki and only seems to be a fork out of this wiki. It also says that this wiki is bad and that all users use that wiki. I do have a FANDOM/Wikia account and thus can request action to staff of FANDOM. Should I take action against this because unlike other copys of wikis, this one seems to be up to date.

BF10 (talk) 00:04, 11 October 2017 (BST)


 * We already know about it, see Community_portal, and no, there's not much we can do about it, just ignore it. --Ovctvct (talk)
 * If you can report it to the Wikia staff, please do. --AlphaBeta (talk) 17:47, 15 October 2017 (BST)
 * I just realized on BillyHatcher2012's page (Raffine2014) he has RTM & Beta keys. There no RTM keys just ovctvct's keys copy-pasted. (Also, he/she (Not sure if it's a boy or girl) thinks the automated response is a real person.) LilShootDawg (talk) 20:01, 26 October 2017 (BST)
 * Wonder if he checks this wiki anymore or if he's ip banned. LilShootDawg (talk) 20:03, 26 October 2017 (BST)
 * He's only blocked, meaning he can't edit, but he could still visit, and he uses a dynamic IP so a ban won't be too effective. Also http://osesbeta.wikia.com/wiki/User_blog:Raffine2014/Closing_Operating_System_Beta,_etc._Wiki looks like it will get closed tomorrow. --Ovctvct (talk)
 * He blocked me for saying "Hi BH2012 (BillyHatcher2012) A.K.A. AyamiOoruri29 A.K.A. Raffine2014." and this is what I get when I see i'm able to comment.
 * "You cannot add a comment to the article.
 * Your user name or IP address has been blocked.
 * The block was made by 165.138.70.5.
 * Reason given: Spamming links to external sites: I know you're spammer, it is ovctvct or alphabeta. please get out on my wiki.
 * Start of block: 11:50, August 18, 2017
 * Expiry of block: infinity
 * Intended blockee:
 * Block ID: #6
 * Current IP address: 165.138.70.5
 * You can contact 165.138.70.5 or another administrator to discuss the block. Please include all details in the above box in any queries you make." WTF!? I didn't post a LINK! LilShootDawg (talk) 15:47, 27 October 2017 (BST)
 * Yep, looks like he is trying to block us in attempt to escape getting the wiki deleted. Looks like the wiki is nothing more than a joke and if it is not gone tomorrow, I have contacted Wikia Staff for major action. Even if he blocks me, that doesn't stop me from contacting Wikia Staff for copying a wiki. BF10 (talk) 16:33, 27 October 2017 (BST)
 * Seriously saying I'm a spammer and I posted one message. THE REASON SAID SPAMMING LINKS TO EXTERNAL SITES! Admin Abuse at it's finest. LilShootDawg (talk) 15:17, 30 October 2017 (GMT)
 * Turns out he didn't close the wiki today. Instead he will lock it from editing. I'm sure that he is still trying to keep it open. I also got a response, which was nothing more than "contact the admin on community.wikia.com or go here" BF10 (talk) 18:37, 28 October 2017 (BST)
 * Contact the admin. Nuff said. LilShootDawg (talk) 12:53, 30 October 2017 (GMT)
 * "The User creator of AlphaBeta." The USER CREATOR of AlphaBeta. So someone created AlphaBeta. Does this person know english? LilShootDawg (talk) 15:20, 30 October 2017 (GMT)
 * Also she (She's a she) copied stuff from BAWiki and BW (BetaWiki) including the Hall of Shame for some reason because basically everything that she types should be there. LilShootDawg (talk) 16:10, 30 October 2017 (GMT)
 * Wonder if she checks the communtiy portal? If so than Hi! LilShootDawg (talk) 19:04, 31 October 2017 (GMT)

Check icons
I found 2 unused icons for programs in Windows 1.0 Development Release 5. I already put them up in the article. LilShootDawg (talk) 14:29, 19 December 2017 (GMT)
 * We need to check icons. LilShootDawg (talk) 14:29, 19 December 2017 (GMT)

An error
I noticed an error. Earlier the website had broken links, and broken text. Like temporary text for translation. Now i'ts ok.
 * Also, I can't upload images anymore. If I try to upload I get "The file you uploaded seems to be empty. This might be due to a typo in the filename. Please check whether you really want to upload this file." Seems to be an error with MediaWiki or one of this wikis components. I am not the admin or creator so I need someone to deal with this. BF10 (talk) 20:48, 30 December 2017 (GMT)

BAN HIM
HE DELETES PAGES AND CALLS HIMSELF SOMEONE FROM MICROSOFT. HIS : MICROSOFT LEGAL REPRESENTATIVE.

BAN HIM.

Don't worry. I have already fired him.--192.241.163.23 08:55, 8 February 2018 (GMT)

who are you?

I am a public relations manager from Microsoft. --192.241.163.23 09:07, 8 February 2018 (GMT)

Ok. Do you know some cancelled projects? I have no info about you.

"Microsoft Legal Representative threatens BetaWiki: Only to be fired miuntes later"LEL
 * Ok, this IP battle is getting strange. I have no idea why they are doing this even though they can salt it all over on WinWorldPC or real BetaArchive. I will hope Oct or Alpha bans him and the IP adresses he is using to evade bans. This really wants to make me get temporary rights to ban these vandals until he never comes back. He is not a real Microsoft employee and likely a sock of Langham or BillyHatcher. BF10 (talk) 13:04, 8 February 2018 (GMT)
 * Unfortunately this person uses a whole new IP every time so there is no way to really ban him, all we could do is to contact his ISP or something. --Ovctvct (talk) 14:34, 8 February 2018 (GMT)