BetaWiki:Community portal

adding language parameter to the infobox windows build

it will become easier to know the languages. 51.15.78.38 10:38, 24 June 2023 (UTC)

Support

1. per myself. 51.15.78.38 10:38, 24 June 2023 (UTC)
2. I support this. Same feature is available for TheCollectionBook. But I doubt it's going to be accepted. This was requested a few times, and it was ignored. — Preceding unsigned comment added by 94.121.82.195 (talk • contribs)

Oppose

1. Unnecessary - Most internal beta builds are only available in a single language and if other languages are available, they will be mentioned on the respective build page. Public beta builds are available in basically every single language supported by Microsoft, so mentioning available languages on the respective build page is also unnecessary. NaraInsider1694 (talk) 12:12, 24 June 2023 (UTC)

   Also, most non-English builds of Windows, especially before Windows 8, are only official Beta/CTP/Preview/RTM builds and not internal ones. - Bob2204 Click here to begin. Or here. Talk - 16:18, 24 June 2023 (UTC)

   This https://betawiki.net/wiki/Windows_10_build_18327.1, it's not an official build. However it's available for many languages. — Preceding unsigned comment added by 94.121.82.195 (talk • contribs)

   Do you seriously think that everyone who visit this wiki like reading long paragraphs? — Preceding unsigned comment added by 94.121.82.195 (talk • contribs)

   Read again. I only have said "most, especially before Windows 8". The Technical/Insider Preview thing changed many things, as they no longer release Preview/Beta/Alpha builds, but only multiple "Insider Previews", which can reach up to around 30 Insider Previews per version before a new version becomes released. - Bob2204 Click here to begin. Or here. Talk - 14:38, 25 June 2023 (UTC)

   Understood. — Preceding unsigned comment added by 94.121.82.195 (talk • contribs)

2. That's not how it works. Every build is compiled in all of the 23 base languages and all available SKUs. I oppose this simply because it would clutter the infobox, especially on Insider previews because they are indeed released in those base languages. --217.131.99.140 07:44, 29 June 2023 (UTC)

   Not every is compiled in all languages. Some builds are only compiled for specific languages. Also what will you say about unleaked, shared or betas before Windows 7? — Preceding unsigned comment added by 94.120.197.130 (talk • contribs)

   Simple: We never know what Microsoft did to their builds and if they're compiled in all languages or not. New languages were gradually added over time, so we need to remind ourselves of the past. Also, don't use {{Unsigned}} to sign your comments, use ~~~~. NaraInsider1694 (talk) 14:21, 4 July 2023 (UTC)

   It's already impossible to know which languages are available in builds. But he said Every build is compiled in all of the 23 base languages, which is definitely false. Otherwise we would have the builds 4074 in German or 5048 in French. The list goes on. 94.120.197.130 (talk) 14:29, 4 July 2023 (UTC)

3. Putting information to the infobox is a double-edged sword, it might make the information more discoverable but it also makes it more cluttered that it needs to be. Not to mention the relationship between SKUs, architectures and languages, since builds rarely are available in all listed combinations. A better approach would be a table like done for Windows 11 build 22000.1. --Ryuzaki (talk | contribs) 07:39, 29 June 2023 (UTC)

   Like in 2296.1 page? — Preceding unsigned comment added by 94.120.197.130 (talk • contribs)

Changing recommended resolution images to 1,920 × 1,080

Literally every single build of Windows 11 use it for some reason, so I guess why not do it on other builds. 37.120.213.238 11:36, 2 July 2023 (UTC)

I guess 1366 x 768 or 1400 x 900 would be better. 1920 x 1080 is too large. —— Preceding SIGNED comment added by Someone200 {{ talk • contribs • email me }} | 23:36, 3 July 2023 (UTC)

The guidelines don't actually recommend a single resolution, they only say it should be period appropriate but at least 1024x768, unless the OS doesn't support that resolution. — Preceding unsigned comment added by Ryuzaki (talk • contribs)

Support

1. 37.120.213.238 11:36, 2 July 2023 (UTC)

Oppose

1. Most old hardware and older versions of Windows do not support such a ridiculously high resolution. Due to DPI scaling being a hit-or-miss on older OSes, the contents of the screenshots will also be too small, requiring the reader to click on the image to better view the screenshot. NaraInsider1694 (talk) 11:40, 2 July 2023 (UTC)

   Then why do Windows 11 builds do it then? I only requested this all because of Windows 11 images. 37.120.213.238 11:43, 2 July 2023 (UTC)

   Newer versions of Windows are better suited for high-resolution displays, also blame the uploader for using that resolution. NaraInsider1694 (talk) 11:46, 2 July 2023 (UTC)

   OH okay. Anyways, does 1,366 × 768 count as a "ridiculously" higher resolution? This is the alternative to 1,920 × 1,080, I guess. 37.120.213.238 11:52, 2 July 2023 (UTC)

   I don't think it counts, since it's basically 1024 × 768, but wider. NaraInsider1694 (talk) 12:18, 2 July 2023 (UTC)

   I think we should only use 1920x1080 for win10 and win11 builds, and the problem is that there are a lot of Windows 10 builds that currently use 1024x768, which for Windows 10's time period is rather low. - Upseguest (talk)

winmain in 2009/2010

There is a very odd thing I found out about winmain in the time period between builds 7232 (Win7) and 7700 (Win8). While 7232 already features the final Harmony wallpaper, 7700 oddly reused the betta fish one. The 7700 page said that it can be implied that this build was formed from a Win7 RC build. I really doubt this, because it's also possible that they just reverted this wallpaper thing for Win8/future winmain development. (At least the betta fish was used until Microsoft started the Technical Preview/Insider Program.) - Bob2204 Click here to begin. Or here. Talk - 23:29, 3 July 2023 (UTC)

Page Previews

This wiki needs page previews feature. —— This newly signed comment was added by Lazytown Sportacus (LazytownSpo4015) • Talk page • 14:03, 4 July 2023 (UTC)

Support

1. Per myself. —— This newly signed comment was added by Lazytown Sportacus (LazytownSpo4015) • Talk page • 14:03, 4 July 2023 (UTC)
2. I was so used to this exact feature on Wikipedia and it allows you to view pages without actually navigating to the specific page. When I first joined this wiki, I actually wondered why page previews aren't supported. NaraInsider1694 (talk) 14:12, 4 July 2023 (UTC)
3. This is a really convenient feature. I also wonder why they haven't been implemented yet. BetaReporter (talk) 17:27, 4 July 2023 (UTC)

Move Insider Preview update pages to their respective build pages

This is a (probably abandoned) proposal made by Xeno. I reopened this because the final decision hasn't been made, and I feel like the servicing pipelines updates are cluttering up the pages.

If this reach 15+ support, I'll do it. It will take a long time though. (as always, please consider providing a reason if support/oppose as it helps me understand your opinion.)

—— Preceding SIGNED comment added by Someone200 {{ talk • contribs • email me }} | 14:23, 3 August 2023 (UTC)

The consensus was to carry that out, not sure why this needs another vote. --Ryuzaki (talk | contribs) 14:33, 3 August 2023 (UTC)

Purge all non-Windows related content (reopen)

This is a reopen of my version of a proposal by orbitron that was abandoned, because apparently the aforementioned proposals aren't being passed through.

Basically, most non-Windows stuff on the wiki, except macOS, iOS, DOS, and OS/2, gets literally no activity besides one or two users. Most pages covering Linux are too short and hardly contain any notable information (and no, bugs don't count as notable). The new features and changes present in each distro version are also not covered properly and the pages only contain the image of the desktop or the home screen, which is not enough for a good article.

While the original proposal focused on all non-Windows content, I wanted to only focus on free-and-open-source OSes (such as Linux, BSD, and Haiku), Android, non-preinstalled web browsers (such as Google Chrome, Mozilla Firefox, Opera, and Netscape) and other less important OSes. For free-and-open source OSes and Android, they have been moved to a dedicated wiki that focused on these OSes. For non-preinstalled web browsers, there are already Wikipedia pages for these browsers. I hope this makes BetaWiki a much cleaner site and live up to its name. NaraInsider1694 (talk) 14:40, 3 August 2023 (UTC)

The proposal was archived because it was dead with no clear consensus. Not sure what makes you think reopening it immediately after it got archived will reach a different result. --Ryuzaki (talk | contribs) 16:48, 3 August 2023 (UTC)

OK, I understand. I did not know that proposals would be archived if it was dead with no clear consensus. I first thought reopening my proposal would bring up attention to the two proposals I mentioned above, so I'm sorry for the mistake I made. NaraInsider1694 (talk) 23:11, 3 August 2023 (UTC)

Moving all GitHub issue related builds to a separate page

I think that most of the Windows 10/11 pages are being cluttered with GitHub issue pages. Since these builds doesn't have a proper buildtag (only build number), I think they should be moved to a separate instead of being purged. Some of them could cause confusions because its build number is identical to another one.

—— Preceding SIGNED comment added by Someone200 {{ talk • contribs • email me }} | 03:15, 6 August 2023 (UTC)

Support

1. Per myself. —— Preceding SIGNED comment added by Someone200 {{ talk • contribs • email me }} | 03:15, 6 August 2023 (UTC)
2. Welp, this should also be done for servicing pipeline update builds. NaraInsider1694 (talk) 03:21, 6 August 2023 (UTC)
3. We should also do that for builds mentionned in SSUComp_KB*******.xml and Desktop_neutral_Forward_*****.****.***************.******-****.CompDB.xml files PikaaxYT (talk) 10:27, 11 August 2023 (UTC)

Adding downloads of the builds in their infoboxes (CLOSED)

Or at least adding an information on where to download the builds — Preceding unsigned comment added by PikaaxYT (talk • contribs)

I closed the request because download links would violate the guidelines — Preceding unsigned comment added by PikaaxYT (talk • contribs)

Support

1. PikaaxYT

Oppose

1. See BW:Guidelines § Legal. Jurta (talk • contribs) 19:52, 10 August 2023 (UTC)
2. We are most certainly NOT providing download links to these builds on the wiki. The wiki is intended to be a knowledge base for these builds. Find the builds yourself. The Windows build FAQ page points out that archive.org and WinWorld are good starting points to find most builds. Although, be careful as there are fake builds out there. It is very easy to find these builds anyways. WindowsGuy2021 2:59, 10 August 2023 (UTC)

Purge Linux and Android content

here we go again...

Most Linux distributions in BetaWiki are not notable, and by "not notable" I mean most of the articles talking about a Linux distro are too short, low quality, and hardly contain any useful or notable information. The Android articles are a good example of this, since they are made of an infobox, a lead sentence, a list of changes (or builds), and that's it. The information necessary for a knowledge base, such as the development history, features, and the overall aspects of a Linux distro, is also missing from the aforementioned articles. Other websites did a much better job at documenting these distros since they are not Windows-centric, unlike BetaWiki. NaraInsider1694 (talk) 09:10, 22 August 2023 (UTC)

discord server invite link

i'm trying to rejoin the BW discord, but it says the link is expired. Has the server been deleted or is it a dead invite? — Preceding unsigned comment added by Grafality (talk • contribs)

It's a dead invite. NaraInsider1694 (talk) 05:33, 16 September 2023 (UTC)

if it is a dead invite, then why wouldn't I rejoin BW Discord server? Also I'm sorry for my past actions while I'm in the server. —— This newly signed comment was added by Lazytown Sportacus (LazytownSpo4015) • Talk page • 08:57, 16 September 2023 (UTC)

I hate to tell you this, but you have been banned from the BW Discord server. NaraInsider1694 (talk) 08:59, 16 September 2023 (UTC)

"if it is a dead invite, then why wouldn't I rejoin BW Discord server?" Precisely because it was a dead invite? It is fixed now though. --Ryuzaki (talk | contribs) 09:46, 16 September 2023 (UTC)