BetaWiki is currently under maintenance. We apologize for any inconvenience caused.
- I can, that's for sure, however there is a problem with the naming, because Mac OS X. We can't include it in the MacOS namespace, but we also can't make it a namespace on its own. Have you got something on mind by chance? --AlphaBeta (talk) 19:56, 4 November 2014 (GMT)
- No I can't, that really seems black-or-white. What would YOU say? Tau Ceti (talk) 06:54, 5 November 2014 (GMT)
- On the links I have added it's a sub-namespace: Mac:OS:X Tau Ceti (talk) 06:47, 7 November 2014 (GMT)
Transferred from the old Rules page
Stating that the sky is blue
Seriously, why are we mentioning Tor and what not, we're just giving script kiddies ideas. Frankly, I think the ruleset is very pedantic and can be simplified by stating that topics such as banning are subject to admin discretion. User99672 (talk) 21:02, 31 January 2015 (GMT)
- Absolutely wrong. BA's rules also mention you mustn't use proxies, BTW, and no, it will be too late for them when they want to vandalise BetaWiki. --Ovctvct (talk) 21:04, 31 January 2015 (GMT)
- That was not what I was suggesting. Furthermore, that is a base rate fallacy, to assume what their capabilities are. BA's rules are not BetaWiki's rules. BA's rules are also not a golden standard; and it doesn't mean it's right. I'm not suggesting any particular site is right, but BA is not the gospel. User99672 (talk) 21:08, 31 January 2015 (GMT)
- BetaArchive, though, is not a wiki. The point of a wiki is that everyone can edit, as long as it doesn't go to vandalism. If people edit over a proxy, it's their own thing. They don't want the admins (and the whole world if they're not registered) to see their IP address, so why should we force them to show it? --AlphaBeta (talk) 21:22, 31 January 2015 (GMT)
- Let me also remind you that just because you disagree with my opinion does not invalidate mine. Nothing we are discussing in this thread is based in factual knowledge, and therefore should not be dismissed as 'wrong', but rather acknowledged as a difference of opinion. I expect better from the staff than to be shut out for not having the same viewpoint. After all, this is a collaborative effort, and does not revolve around any single person. User99672 (talk) 22:39, 31 January 2015 (GMT)
- I realize it's been a while, but I wanted to point this out: [] Administrators from other sites have come to understand the reality of telling people how to misbehave. I was right all along and Wikipedia has vindicated me. I'm glad we don't have spam-artists for administrators here any more. User99672 (talk) 23:39, 10 May 2015 (BST)
Distributing software [betas], keys, and cracks via BetaWiki
In re. to this page: []; there really should be a policy about this. This is a wiki and not a distribution point...as well, someone (namely rightsholders or trolls) could very easily endanger the wiki by reporting this...I would strongly recommend not allowing such content here... User99672 (talk) 17:31, 3 March 2015 (GMT)
- Indeed, wikis are intended to be an information source, not a download tracker. Keys though should be allowed, as long as they are not for final versions in which case it'd be warez. --AlphaBeta (talk) 17:36, 3 March 2015 (GMT)
A Guide To Taking Proper Screenshots
I've noticed recently that people are taking a mix of screenshots of different qualities, or with mistakes in the picture. In light of this, here are some recommendations I suggest (and that I've established on articles I've edited). The easiest way to see them is by screenshots themselves. Note that these guidelines only apply in the case that a build is documentable (you have the real build, and not using shots from a third-party source outside your control). -Foxlet (talk)
Screenshots should be "clean" (no extraneous borders outside the video area) and scaled to their true size. If possible, use the Windows screenshot feature (Print Src, Snipping Tool) to take pictures of the desktop, or use the screenshot feature if using a hypervisor/emulator. For "Full Screen" shots, if a cursor is present, it should be isolated in a corner of the background if possible (to show unique features of the cursor). All screenshots should be lossless (JPEG is not acceptable).
Each main article usually requires three components: the Desktop, the About window, and (sometimes) the Logo. In most cases, a Windows article only needs the first two. "Full Screen" shots (such as for the Desktop and Start Menu) should be 1024x768 in 16-bit color at minimum, unless the subject in question does not support such a video mode (for example, 1024x768 in 256 colors is fine for Windows 3.1 and Microsoft Chicago).
Desktop shots should be void of any extra windows, it should represent the state of the system when it is completely idle without any running programs. In the case that the OS shows a tool or special graphic (such as a welcome screen), that is known as a "First Boot" shot, and is separate from the Desktop shot.
Each article also contains a Gallery, where other associated shots are contained. Additional full screen shots belong here, such as the "Demo" (which shows off particularly unique features of a build). The remaining shots are usually those of programs unique to a build. Those shots should be cropped to the size of the program's window (including transparency and window shadows if such effects are present).
I suggest that there should be a rule for screenshots for that if widescreen didn't exist back then, you shouldn't take screens in widescreen. (That's 16:9, 16:10, etc., etc., etc.) --LilShootDawg (talk) 14:10, 14 January 2019 (GMT)