User talk:ScotXW

While I enjoyed playing S.T.A.L.K.E.R., I less enjoy Wikipedia:Stalking. User:ScotXW^t@lk 12:37, 22 June 2014 (UTC)[reply]

• Tschunk. Nice "job", "dog". User:ScotXW^t@lk 17:20, 12 July 2014 (UTC)[reply]

Yo! Please don't add this picture:

to articles about technologies not only related to GNU/Linux. This misleads people and shows them, that for example Pulse Audio works only in GNU/Linux when it works also in other systems, FreeBSD, NetBSD, Windows among them. Free software is not only GNU/Linux. Why the hell article about for example Qt have to be GNU/Linux-centric?! Cheers. --Uniwersalista (talk) 16:23, 21 August 2013 (UTC)[reply]

I beg your pardon? ScotXW (talk) 17:06, 21 August 2013 (UTC)[reply]

The diagram also shows stuff like Ethernet. Did you also conclude Ethernet only works with Linux? Msnicki (talk) 00:08, 22 August 2013 (UTC)[reply]

Uniwersalista, I think this diagram is a harmless addition to those articles. The captions in both clearly state "here is an example of (qt|pulse) being used in the context of Linux" which is completely true, and adds useful context. The same articles say, right at the top, compatible with bsd/linux/win/osx/whatever. Nothing misleading is going on here. Now, arguably, the particular diagram in question does not add much to the PulseAudio article... since it deals mostly with visual rather than auditory elements, and does not even cover e.g. HDMI video+audio streaming, but that can be corrected by cloning and then improving the SVG. To be blunt, if you do not want the *only* block-diagram in the qt article to show qt being utilized in a linux context, then do the work to make a bsd/osx block diagram, or a win9x/winNT block diagram, which show qt in those contexts. *That* would improve the qt article in particular, and wikipedia in general; don't discourage ScotXW from doing the same. 74.192.84.101 (talk) 21:52, 27 August 2013 (UTC)[reply]

Great work on the diagrams. I have some criticisms/corrections. Not sure if this is the right place to put them? If you would prefer to chat about them elsewhere, like on the talk-pages of the relevant article, let me know. Also, if you'd rather I just edit the diagrams myself, and then upload my suggested changes for review, that can prolly also happen (I have not used inkscape but have done some simple svg editing before). Again, just say what works best for you. 74.192.84.101 (talk) 21:52, 27 August 2013 (UTC)[reply]

In this file -- https://upload.wikimedia.org/wikipedia/commons/7/7b/Free_and_open-source-software_display_servers_and_UI_toolkits.svg

1. Typo , noveau ==> nouveau 74.192.84.101 (talk) 21:57, 28 August 2013 (UTC)[reply]

Yes.

2. Misrepresentation of current state (wikipedia is not a crystal ball), X-Server is the 'display server' as of 2013, whereas Wayland is the 'alternate display server'. It first shipped in FC17 of mid-2012, and won't even be the default for fedora until mid-2014 and FC21, says the Wayland article. That ignores non-fedora distros, including RHEL/centos/sciLinux from redhat themselves, as well as non-RPM distros like Ubuntu, which may *never* have wayland as the default display server. Strongly suggest that you put X-Server where it belongs, in the 'display server' box. Less strongly, recommend that you create a third category named something like 'upcoming display servers' that can include wayland for fedora and mir for ubuntu, since both of those choices are Sourceable Predictions From Notable Persons. Hmmm... it looks like you are already dividing the chart up into three sections, one for android, one for FutureUbuntuWithMir, and one generic section which is supposed to be GenericLinux but looks to me like FutureRedHat in many ways. Maybe you should have a four-section chart, with top-left GenericDesktopLinux (to include UbuntuPre2014 and FedoraPre2014 flavors) using X-Server, top-right AndroidMobileLinux, bottom-left RedHat2014+Linux documenting Wayland-related changes, and bottom-right Ubuntu2014+Linux documenting Mir-related changes? 74.192.84.101 (talk) 21:57, 28 August 2013 (UTC)[reply]

NAK. I am pretty sure, that no noteworthy changes are going to be made to the article or to the diagrams until 2016, because the people don't care. They don't care about Guantanamo and they sure don't care about the "Free desktop". I have no plans of keeping it up-to-date, so I simply depicted the stuff that is gonna be the standard. Debian, Kubuntu, Xubutu, mer: they all want systemd, pulseaudio and most definitely wayland.

Well, fair enough. I may try to create a modified version, now that I understand better what you are trying to convey here (see my comment below under #6). Do I just download the SVG, and open it in inkscape? Ubuntu 12.04.2 installed at the moment here. 74.192.84.101 (talk) 21:57, 28 August 2013 (UTC)[reply]

p.s. The_People c'est moi! I care about gitmo. I care about libre. But yes, I hear you, sometimes those qualities seem like rarities. Do not give up the fight.

3. Suggest adding some lines-and-arrows to the diagram, to show dataflows. From what I can gather, Qt can target Xlib or libGL or libwayland-client. Is there some way to cleanly make that clear in the diagram? There does not seem to be any stuff shown in this particular diagram at the moment that shows the libGL pathway, e.g. qt-to-libGL or cairo-to-libGL. Those will still exist under wayland, right? And they certainly exist now, although I'm not sure how often such pathways are utilized. Similar comments about SDL&maybeClutter-to-EGL, that pathway-option should be shown explicitly, with lines-and-arrows. 74.192.84.101 (talk) 21:57, 28 August 2013 (UTC)[reply]

NAK. This diagram is supposed to be an overview depicting pretty much everything available as of components of the free desktop (now and in the foreseeable future). If you want pathways, I suggest you create derivative diagrams for GNOME/KDE SC/etc only, there you'd have the additional space for pathways. There is no space here, it is already pretty crammed. But yes, pathways with even more details are good.

4. The large collection of system daemons looks extraneous to me. Sure, in some fashion I suppose that 'display servers & ui toolkits' depend on the low-level stuff like upower and NetworkManager... in the same sense that they depend on the bootloader and the BIOS, cause if you cannot even boot, you obviously cannot run gedit! Seriously, though, the daemons seem out of place. Removing some/many of them would declutter the diagram, and also give room for lines-n-arrows of suggestion#3, above. Did you intend for those particular daemons to be listed in this particular diagram, for some reason? 74.192.84.101 (talk) 21:57, 28 August 2013 (UTC)[reply]

NAK. The daemons are pretty much important, because a) many user are not aware that Network-Manager or PulseAudio are in fact primarily daemons, and they only see and interact with the GTK+/Qt surfaces for these daemons, and only by clicking some buttons. Utilizing the CLI exposes more functionality and also, makes the daemons interesting for non-GUI setups. E.g. OpenWrt uses PulseAudio, that is the PulseAudio-daemon! Instead of the NM they use something called netifd, but that would take too much space ;-) And b) because they represent the ongoing effort to combine resources. GNOME and KDE SC (and also the other DEs) all share this code. Especially KDE should learn to solve problems upstream instead of working around such problems inside of KDE...

I wasn't going to bring up TUI-based apps, like parted / mc / mutt / ncurses stuff, but in many ways that is another "ui toolkit" for the free desktop, or at least, the rescue-disks when the free desktop goes awry. If I make derivative diagrams, I may try adding those in. 74.192.84.101 (talk) 21:57, 28 August 2013 (UTC)[reply]

5. Not sure that lima/etna_viv/freedreno/tegra-re actually belong under wayland... as opposed to under android... they almost certainly don't belong under X-Server. Aren't those all android-only GPUs? Or is wayland intended to challenge libbionic and libEGL in the ARM-tablet market, not just X-Server in the x86_64-desktop market? 74.192.84.101 (talk) 21:57, 28 August 2013 (UTC)[reply]

They don't. These are just Linux kernel modules, like ath9k or Netfilter are. I want no pathways, but I do want the mention some Kernel modules there. So when somebody has look at File:Gallium3D_example_matrix.svg or File:Linux Graphics Stack 2013.svg, or at some diagram with more details he or she has a better chance to distinguish between stuff that belongs to kernel space and stuff that is in user space. He or she can also port info back to this diagram.

mer-based stuff like Sailfish OS will use lihybris and Android-drivers where there are no Linux drivers available, not only for graphics, but also for hardware like the GPS-receiver. And yes, they also use systemd and wayland on embedded systems.

Who is using wayland on embedded systems, and what systems? Surely not Tegra2, right? Is google planning on junking libbionic and switching to the 'same' wayland that will be found in RHEL9, for instance? (These are all honest questions... I had no idea anybody foresaw wayland as a useful system for tablet & smartfon devices.) Update, I did a little looking around before submitting my reply -- wayland can implement custom backend display drivers, and one has been created for RaspberryPi devices, see here [1]. I'd be *very* curious to know whether they used the Hermitage/Gottschlag/Mansell open source driver stuff, or just got a binary-blob-backend. This will give us a hint as to how libre the future under wayland is likely to be. 74.192.84.101 (talk) 21:57, 28 August 2013 (UTC)[reply]

1. Before Nokia lost its mind and turned to the evil, they paid people to play with X.Org-stuff to make it run better on smartphones. Jolla was founded by ex-Nokia employees.

2. Smartphones come with 512MB and more of DDR3 main memory and quad-core CPUs. That is **very** powerful hardware compared to 1992: i486 and 4MB of DRAM (fast page not EDO)

3. Wayland is **much** simpler then even X11 core protocol. And it performs **much** more better then X11! The LCA2013-Video by Daniel Stone explains it well enough. So yes, the same implementations of the Wayland protocol runs on Dekstop, Nettop, Tablets and Smartphones! The exact same it true for systemd. Only OpenWrt-folks do not run systemd: OpenWrt architecture because they don't have many processes and also, because procd runs better on only 32MIB of main memory. It also seems like procd lended many ideas from systemd.

6. Ought to add 'intel' to the kernel-mode-libdrm-gpu-driver listing, next to radeon & nouveau. 74.192.84.101 (talk) 21:57, 28 August 2013 (UTC)[reply]

ACK. Indeed I forgot to mention the free and open-source Intel drivers, even after watching Keith Packard (who "does not care for anything else" and is heavily involved in DRI 1,2 and 3)

Many of my comments above were based on an incorrect assumption. You said above: "This diagram is supposed to be an overview depicting pretty much everything available as of components of the free desktop." But the filename is simply Free_and_open-source-software_display_servers_and_UI_toolkits , which is what confused me. Suggest changing the filename to something like this -- Free_and_open-source-software_components_of_the_graphical_desktop ... that way, including PulseAudio and systemd makes perfect sense. 74.192.84.101 (talk) 21:57, 28 August 2013 (UTC)[reply]

In this file -- https://en.wikipedia.org/wiki/File:Gallium3D_vs_DRI_graphics_driver_model.svg

1. Suggest changing 'Gallium3D device driver' into something like 'Gallium3D-compliant driver' , and maybe giving the names of some major targets (r600/nc50/i965/etc). As I understand it, there is no actual "gallium driver" but merely the interface-spec, which says that e.g. the r600 driver must present a specific gallium3d-tracker-interface to the upstream mesa-opengl-implementation-library, and also that is must present a specific gallium3d-winsys-interface to the libdrm stuff in the kernel. Is this right? 74.192.84.101 (talk) 21:57, 28 August 2013 (UTC)[reply]

ACK. Technically it would be correct to speak of Gallium3D-complient device driver. NAK. Because I already created a Gallium3D-Matrix: File:Gallium3D_example_matrix.svg; Please do note how crucial it is to be able to distinguish between Kernel space and Userspace when looking at gaphics drivers. This diagram: File:Linux_Graphics_Stack_2013.svg mentions at least Wayland, but it lacks Gallium3D!!! Would definitely be a nice to have!

Actually, for my own understanding, as well as for improving wikipedia, I'm currently trying to figure out the difference between the "graphics drivers" on Linux. There appears to be the DIX/DDX layer (the xserver-xorg-video driver) which nowadays has maybe been replaced by the MesaStateTracker layer(?), the Gallium3D layer (translates from GLSL to TGSI ... and maybe from TGSI into R600G?), and the libDRM layer (which talks 'directly' to the GPU hardware). I'd like to know, at some reasonably detailed level, what each of these 'boxes' is supposed to accomplish. I'd also like to compare that to the proprietary-binary-blobs, which don't seem to use *any* of that infrastructure -- yet they still internally provide an openGL implementation [4.4 rather than 3.1 albeit], and get from the X-server to kernelspace (somehow), and drive the GPU hardware (somehow). But first I'm just trying to grok how the open-source ones currently work, which is apparently not such an easy task. 74.192.84.101 (talk) 21:57, 28 August 2013 (UTC)[reply]

2. Along the same lines, I think it would help if the 'drm' box on the bottom right mentioned specifics (libdrm-radeon / libdrm-nouveau / libdrm-intel). 74.192.84.101 (talk) 21:57, 28 August 2013 (UTC)[reply]

Yes, it would indeed help. And e.g. the Debian repos only contain these three: [2] Nothing else. Do you know why?

Although I do not 'know' why I think I can speculate on why: older DDX/DRI2 drivers for matrox/3dfx/whatever were pre-DRM, and there are no libdrm kernel-mode drivers being implemented for the old hardware (and the companies themselves have disappeared in favor of the triumvirate of nvidia/amdNeeAti/intel ... at least on the desktop). By contrast, companies that are making new GPU hardware at the moment (adreno/tegra/friends) do get libdrm implemented for their stuff. As for other semi-modern ways of accessing the display, like the vesa-framebuffer drivers and such (there is also radeonfb and many more), those don't use libdrm because the talk to the GPU via x86 BIOS calls, "invented" back in 1987 when DOS was king. Your diagram is mostly about the graphics&toolkit stuff when the system is fully booted, but there are some weird things that happen during the grub bootloader stage, and the plymouth bootscreen, and so on. 74.192.84.101 (talk) 21:57, 28 August 2013 (UTC)[reply]

3. What about the kernel-mode 'dri' box on the righthand side? Is there still DirectRenderingInfrastructure stuff in the kernel, that is actually used by r600 and similar gallium-compliant drivers? 74.192.84.101 (talk) 21:57, 28 August 2013 (UTC)[reply]

I do not know for sure how Gallium3D-complient drivers communicate with the hardware! I am pretty sure, it is via the DRM. But the DRM is hardware specific...

My limited understanding is this: the gallium3d layer converts GLSL subprograms into somewhat-generic TGSI, and then the kernel-mode hardware-specific-driver compiles that TGSI into a binary form which is specific for the target GPU vertex-shader/geometry-shader/pixel-shader units, before passing it along to the GPU hardware. Communication with the GPU hardware is done via the PCI-e bus, for discrete GPUs at least: there are some areas in dram which are mapped to the vram, not just for the framebuffer-data containing pixels, but also for the various registers/shaders/etc that are used to configure and setup the GPU. I'm very fuzzy on the details, though, and this info might be outdated. 74.192.84.101 (talk) 21:57, 28 August 2013 (UTC)[reply]

4. Along the same lines, does the 'drm' box on the *lefthand* side belong? I was under the impression that the older DRI2/DDX drivers did not need/use libdrm. Am I wrong? 74.192.84.101 (talk) 21:57, 28 August 2013 (UTC)[reply]

I do not know, but yes, there were a couple of implementations for X graphics drivers!!!

X11R5 : one DDX per system, used OS-Specific kernel interfaces also supported non TCP/IP network protocols (decnet,...)

XFree86 2 & 3: one DDX for all systems with os-support layer, direct hw access to VGA cards, avoiding complex kernel interfaces for video card support

XFree86 4: added the OS-independant modules loader

X.Org 7 started removing support for older, non POSIX, non TCP-IP systems (VMS, DECnet, OS/2,..)

Remove direct hw access (KMS, DRI2)

And I will rather spend time working on Wayland/DRI3/Gallium3D then on X11! My current system is running X.Org Server, but I can hardly wait to get rid of the geriatric X :-)

Watch this Video: http://www.youtube.com/watch?v=cQoQE_HDG8g and you will understand why! We have 2013, if nobody has bothered to document X better until now, I sure as hell won't. ;-)

I think perhaps Heinlein said it best: by the time you understand some technology reasonably well, it is already obsolete. (He added, luckily you normally learn a thing or two from all your trouble with the old technology, things which can be applied to the new situation... or we'd still be living in the trees.) I skipped the video, but I went through the Feb'13 slides[3]. Here is more recent Jul'13 info from the same[4] folks[5]. In particular, I note that every wayland system will include an embedded X.org Xserver, for backwards compatibility with existing X-client-apps. Furthermore, the future-is-wayland is far from confirmed, as you can see from this reply[6] by Eric Griffith (one of the main wayland folks apparently) in the forums. 74.192.84.101 (talk) 21:57, 28 August 2013 (UTC)[reply]

Point being, may I continue to gently suggest that your diagram does not really have NPOV as regards wayland vs X11, and is suffering from a mild case of WP:CRYSTAL. The current free desktop is X, and in the foreseeable future (now through 2015 or even 2020), even should wayland become ubiquitous somewhere under the hood, and mir disappear, many *apps* will still be X clients. Depending on what nvidia et al decide to do, see eric-link, and how well nouveau keeps up, and how important android/tegra/adreno/powervr/etc become, the diagram as it is now might turn out to be wrong. Better to stick with what we know, and mark things that are still in the future as *being* in the future. Hard to do that without cluttering the diagram too much, or growing it to 6000x6000 pixels.  :-) I'll give making a derivative a shot when I have some more time, though. 74.192.84.101 (talk) 21:57, 28 August 2013 (UTC)[reply]

Also, KMS is not in your diagrams at the moment, right? Is is still a wrapper around libdrm? Or is it older than that, and only worked with DRI2 drivers? (which are still present of course) 74.192.84.101 (talk) 21:57, 28 August 2013 (UTC)[reply]

5. In the big usermode 'dri' box are there any current examples? Some of the open source intel drivers are still non-gallium, methinks, so maybe list their names. 74.192.84.101 (talk) 21:57, 28 August 2013 (UTC)[reply]

AFAIK Intel is not going to write Gallium3D-drivers! Intel-guys write and support only DRI-drivers. Other people took the code and ported it to Gallium3D. The Matrix depicts the idea behind Gallium3D pretty good, I hope, but actually we do not have a Direct3D 10/11 tracker! There is a Direct3D 9 tracker, which boosts performance with Wine a great deal. Don't know how much performance we loose by implementing more and more Interfaces though...! Additionally we also loose some of the possibilities of the hardware... because the hardware driver is written for the hardware, but is only allowed to talk over the WinSys-Interface.

I'm curious about the intel-drivers-ported-to-gallium3d, for my own system. Do you have a link, or a keywork-hints, for where I can find that stuff? 74.192.84.101 (talk) 21:57, 28 August 2013 (UTC)[reply]

I think X has harmed the entire Free Desktop very much. No, only by reading Wikipedia-articles you do not and will not see that fact. It took people like Keith Packard (excluded out of XFree86, founded X.Org) to allow this fracking protocol-kraken to be replaced, and also Companies willing to pay developers real money to get something that could compete with the iPhone... They worked on X.Org and did a lot of good things to it, but Wayland will be the actual thing. As a user you won't notice the transition, but developers will! We are definitely getting there. Question is: why did it take so long to get there? Cannot be lack of dedication. Who decided to not touch the X11-core?

The same is true for OpenGL! OpenGL was superior to Direct3D and could have stayed superior, but it didn't! Also, Mesa only supports OpenGL 3.2, whereas OpenGL 4.2 is available! Thanks to Mac OS and Valve OpenGL could start to matter a lot more. Developers claim that is is easier to develop for OpenGL and then port to DirectX. However, Games are rather developed for Consoles, and drivers are rather being written for Android! Too late for a Desktop Linux Spring?

I just stumbled over something: Freedreno: I think this drm-freedreno is a DRM-Kernel module for the Adrenos. And he says, he additionally has "a libdrm branch with libdrm_freedreno for userspace updated to work on top of either this driver or the downstream android kgsl+fbdev drivers.

1. DRM is hardware specific,
2. libDRM here File:Linux_Graphics_Stack_2013.svg could be the DRI-driver here File:Gallium3D_vs_DRI_graphics_driver_model.svg. So Gallium3D takes userland libDRM-nouveau and splits it up into three chunks of code, and adds code for the Galliudm3D Tracker Interface and for the Gallium3D WinSys Interface (File:Gallium3D_example_matrix.svg). It still requires a Kernel-module to talk to the hardware, and this is the DRM, which is also hardware specific.
3. I'd like to know, how libDRM talks to lib-mesa-glx / lib-mesa-dri!
4. Also, I think, the userland-part of the drivers talk to the DRM (a Kernel module) by implementing the glibc. While the userland-drivers for Android do the same by implementing libbionic. Thus libhybris will translate bionic-calls to glibc calls, making it possible to use those drivers with cooler Linux-based systems than Android ;-).

Yes, from what I can tell Freedreno is definitely an open-source reverse-engineering project for the Adreno GPU. There are similar projects for the ARM Mali GPU (lima), the vivante GPU (etna_viva), the nVidia Tegra GPU (tegra-re), and so on. Most of these GPUs are not used in desktops, but only in tablets and such, which means they tend to run Android. Broadcom makes the Videocore GPU, as used in RaspberryPi. See here[7]. Just like with nvidiaBlob-vs-nouveau GPU and amdBlob-vs-radeon GPU on the desktop, there are also binary-blob drivers for all these tablet GPU options. Intel desktops are the exception; not sure about their Atom-based GPUs, though. Only lima is performance-competitive at the moment, from what I can grok. 74.192.84.101 (talk) 21:57, 28 August 2013 (UTC)[reply]

For ages I have been looking for diagrams and overviews of the Linux desktop stack. I've read plenty of overviews about the Linux server stack already; the so called LAMP stack, Linux+Apache+MySQL+PHP (PHP or Perl or Python). Those diagrams you created are really very very useful work. Viele danke :-) Maybe I'll find some time to improve one or two diagrams, or to add an MS Windows + KDE stack diagram for the Qt article. I immediately saved some of your diagrams to my harddrive and added it to my personal notes about Linux. Paulus/laudaka Laudaka's talk page 07:02, 31 August 2013 (UTC)[reply]

You are welcome. ScotXW (talk) 20:30, 1 September 2013 (UTC)[reply]

Linux_kernel_input_output SVG

1. propertys ==>> properties 74.192.84.101 (talk) 17:44, 1 September 2013 (UTC)[reply]

2. other 'screen' types to mention are DLP-based projectors (portable-powerpoint to movie-theater-size), plus maybe OLED smartphones/signage 74.192.84.101 (talk) 17:44, 1 September 2013 (UTC)[reply]

3A. the framebuffer (which is either in sdram or vram depending on gpu type) is on the 'righthand' side of the gpu next to drm/kms/gem...

Yeah, I actually did not plan to bother with such details, hence I called the box for IC-based hardware a black box, looked at the framebuffer, which is in main memory for APUs by the way, because I specifically looked at the video output. Sound is missing completely, for OUTPUT and for INPUT.

3B. ...and the physical output-connectors and their associated asic-chips (hdmi/dp/dvi/ldvs/vga/ntsc) are on the 'lefthand' side of the gpu, to drive the screen. 74.192.84.101 (talk) 17:44, 1 September 2013 (UTC)[reply]

I had them in, I think they're still there on some layer made invisible, as Interfaces between IC-hardware and "Human-Sense"-Hardware.

4. strongly suggest removing sata ctrlr, it does not play a role in the user-input chain (nor the graphics-output chain)... storage & caching is another good-sized universe: doing it properly would need to cover sdram/L1/L2/L3/L4, vram/texture/L1/L2, cmos/nvram/vbios, mfm/ide/scsi/sata hdd w/ dram cache in 3.5"/2.5"/1.8" forms, sata/msata/pcie ssd w/ dram cache, hybrid hdd+ssd, floppy 8"/5.25"/3.5", cf/sd/usd/sdhc/sdxc/memstick/mmc/etc, usbkeys, usb/fwire/esata/tbolt hdds&ssds, umpteen kinds of tape-drives, SANs, NASs... and that's not even talking about storage *protocols* and cloud services and other software-ish portions of the storage world. This diagram should be about human-generated input, and human-visible output, not about generic "I/O" subsystems. 74.192.84.101 (talk) 17:44, 1 September 2013 (UTC)[reply]

5. one thing not in your diagram is human-visible output sent to printers... back in the 1960s, the teletype output *was* the visual display. I think we're safe in omitting it from your diagram, though, because nowadays you pretty much always see printed output on a screen of some sort first, and then optionally print it. 74.192.84.101 (talk) 17:44, 1 September 2013 (UTC)[reply]

6. optional, since the stick-figure is fine by me :-) but methinks wikimedia prolly has some stock photos of "generic humans" you could use (1 student + 1 bizSuit?) 74.192.84.101 (talk) 17:44, 1 September 2013 (UTC)[reply]

7. although not typical, an interesting corner-case that might be worth adding to the diagram: audio text-to-speech software (which feeds hw spkrs/hdfons) for visually impaired folks, or just 'looking' at your eReader while driving your car 74.192.84.101 (talk) 17:44, 1 September 2013 (UTC)[reply]

This little experiment] by John Carmack inspired me to do the this diagram. Keys are the USB polling rate (when you have no USB harddisk attached to the same USB master doing some file transfers...!!!), the processing time, and then the display properties.

The display properties CRT vs. TFT vs. OLED are important because they can significantly increase response-delay. The text for this requires some space.

IC-Hardware-Black-Box. Leave it a black box and either remove SATA or add more stuff to the black-box

IC-Hardware-Structure: It could be interesting to change the black box into something with a structure, like here File:Linux_Graphics_Stack_2013.svg but with even more details. Everything runs on the CPU in the main memory, and accesses ALL the rest of the IC-Hardware through the CPU and main memory through register/memory mapping with or without the help of device drivers. Everything? Not quite, e.g. the [Marvell Libertas] runs an RTOS on a extra ARM9 + 96kB of separate RAM. Ubicom CPUs also have some parts of the bootloader run all the time, the Broadcom SMP stuff is also weird, and their VideoCore even more. Not sure about Qualcomm Hexagon and the Texas Instruments stuff.

Interfaces: Between Human Brain and Hardware-Hardware are the: Human-Senses. Some de:Piktogramms would be cool. Between Hardware-Hardware and IC-Hardware is the stuff you mentioned: CGA, VGA, DVI, HDMI, DiplayPort, LVDS, USB, FireWire, SerialPort, Game port, etc. Interfaces are everywhere, let's not make a big deal out of them, but let's do mention them. I like picograms and logos, because they are quickly to recognize visually.

Software: The Linux kernel is the only thing I personally care about, because that is that runs my entire hardware devices: PC, Router, Phone. At least mentioning evdev is a given, so people at least know what component to search for, when looking at Keyboard, Mouse, Gamepad, ... INPUT. I would audaciously call this general knowledge. Alternatives (for/in the Linux kernel...) should there be any, should be added, and also maybe even more details. The graphics part is obviously wrong, because I simply put KMS (Linux kernel), Graphics Execution Manager and Direct Rendering Manager there, though only ONE of them actually draws into the buffer, AFAIK. Actually which one? The diagram also omits the fact, that Wayland clients will also be able to draw into "a" buffer directly via EGL and Wayland compositors also do stuff buffer content, and do buffer-flip via the KMS.

Hello, ScotXW. I am afraid that the direction of arrow 2 is not correct. So does arrow 3. 128.221.224.62 (talk) 05:51, 21 September 2013 (UTC)[reply]

I just update the scheme, now it should be correct, thank you. ScotXW (talk) 09:37, 24 September 2013 (UTC)[reply]

Congratulations on making such an impact on Linux articles. Impressed. I left a message for you about this edit Talk:Lennart_Poettering#Sources_and_quotefarm. Regards Widefox; talk 13:52, 16 October 2013 (UTC)[reply]

Thanks. But these are just the fruits of procrastination ScotXW (talk) 14:42, 16 October 2013 (UTC)[reply]

Hello there! I'd really appreciate if you'd be more polite in your edit comments, taking this one as a reference. I'd say my work here isn't deserved to be simply called playing. Thank you. -- Dsimic (talk) 14:01, 17 October 2013 (UTC)[reply]

Obviously there is quite some work in progress. I do appreciate spelling and grammar corrections and even more so good ideas. ScotXW (talk) 14:04, 17 October 2013 (UTC)[reply]

Well, I'd say we're on the same page — we both want to make Wikipedia better, especially its Linux coverage. For the beginning, would you like me to rewrite the heading section on Linux for embedded systems? It really requires a rewrite, if you agree. -- Dsimic (talk) 14:10, 17 October 2013 (UTC)[reply]

You do not need my or anybody else's permission. Just do. I'll change or revert your changes, like you mine or anybody else's. ;-)

1. The entire article Linux for embedded systems requires a different direction (i.e. Linux OSes (plural) for networking equipment, machine control, industrial automation, navigation equipment and medical instruments etc.)

2. And yes, I agree, the introduction could be way better. The entire article could. ScotXW (talk) 14:16, 17 October 2013 (UTC)[reply]

I agree there's no need for technical permissions, but then again, it's much better to reach an agreement / consensus before making some bigger changes. It should be easier and better in a long run... Team work and stuff. :)

Also, I agree that the Linux for embedded systems article should be different and much better, and there's a ton of stuff not even mentioned there — just as you above listed the categories of embedded devices. Ok, for the beginning I'll go ahead and rewrite the heading section there.

Btw, would you maybe consider creating a graph for the OpenWrt article by chance? You're really good at that, and having a nice graph there would be really good — and it could be also used for the Linux for embedded systems article. I've removed a too general "Linux overview" graph from the OpenWrt article, as it was more confusing than explanatory. Hope you agree.

-- Dsimic (talk) 14:29, 17 October 2013 (UTC)[reply]

Using that diagram was a conscious decision. Its name is Linux ubiquity. I want to show readers of the OpenWrt article, that the same Linux kernel is employed on their desktop computer or their smartphone, on several LAMP servers and (modified) on some of the worlds fastest supercomputers and vice-versa. But yes, for complete retards, it could be confusing. Also please note, that AFAIK OpenWrt contains Xfce, used by Ben NanoNote.

Before bothering to create a diagram for OpenWrt only, I'd rather bother to document OpenWrt Buildroot. Also, as can be seen e.g. here: [8] the only relevant difference between a desktop computer and Android-devices is the fact the latter has a touchscreen as its only HID. I see no advantage in Android operating a Smart TV over, say Debian. This is my technical assessment not my opinion. Wikipedia articles should present and describe the underlying software architecture of things much more often and much more thoroughly than it does. It should bother less with consensuses of mere opinions of (more or less ;-)) random passersby. Because of that crap, people with the knowledge and comprehension don't bother to write text in the Wikipedia any longer. ScotXW (talk) 14:53, 17 October 2013 (UTC)[reply]

Sorry for my delayed response, I was busy rewriting the Btrfs#Cloning section. :)

You're totally right about the low numbers of people doing real contributions to Wikipedia. By saying "real", I mean the same as you described above — hard-core stuff that brings true new values to Wikipedia. It's really great to have everything written in formal language, polished and everything — but that's good only if there is the real stuff underneath. I mean, polishing is a great thing, but you've got to have a lump of steel in order to chrome it, right? :)

Btrfs article is a good example — the amount of real content available there is not that high, and many times in form of brief notes only — instead of thorough and up-to-date explanations. I'll try to improve that article soon. :)

I agree that, in the example you provided, Android has no real advantages over Debian or any other general-purpose Linux distribution. It's all just about the fuss how Android is great, gorgeous, yummy and such buzztalk. It's no better than CentOS (or maybe is even worse), for example, just if someone known what's he or she doing.

Just as you said, consensus is a great thing, but it depends on the involved parties. How do we know who's taking part in a "committee" discussing towards a consensus? :)

Regarding the OpenWrt article, I'll see to extend it soon so buildroot is also covered. Also, I'll think how to integrate the general Linux overview graph better into the article.

-- Dsimic (talk) 17:29, 17 October 2013 (UTC)[reply]

Hi. Thank you for your recent edits. Wikipedia appreciates your help. We noticed though that when you edited Linux adoption, you added a link pointing to the disambiguation page Amazon (check to confirm | fix with Dab solver). Such links are almost always unintended, since a disambiguation page is merely a list of "Did you mean..." article titles. Read the FAQ • Join us at the DPL WikiProject.

It's OK to remove this message. Also, to stop receiving these messages, follow these opt-out instructions. Thanks, DPL bot (talk) 09:09, 4 November 2013 (UTC)[reply]

Hi ScotXW!

If you are the same ScotXW who is editing Hungarian WP, then I have a special offer to you. I scooped up a rather big en-hu dictionary and there's an experimental firefox plugin for quick word and phrase translations. If you wish to try it, then drop me a mail (try this). BR, Pkunk (talk) 22:21, 5 November 2013 (UTC)[reply]

Hi Scott! I also have offer for you. I see you are interested in linux, free software, virtualization and cloud computing. I share this area of interest with you and the topic deserves a better documentation on wikipedia, so if you want to put some content on the hungarian wiki, you can contact me directly and I will do it for you. Deal? :) --K0zka (talk) 18:01, 6 November 2013 (UTC)[reply]

Hmm, I don't know. I've heard that one should not trust a bunch of "Hungarian Barbarians". ScotXW (talk) 21:02, 27 February 2014 (UTC)[reply]

ok, you know what works better for you --K0zka (talk) 14:58, 19 June 2014 (UTC)[reply]

Template:Linux layers has been nominated for deletion. You are invited to comment on the discussion at the template's entry on the Templates for discussion page. The Banner talk 22:50, 6 November 2013 (UTC)[reply]

I'm really impressed with your Diagram explanning the LAMPP architecture in bottom(low) level.

Thank you.

But for an intro to novice, beginners, I feel this might be cause confusion to them, as they new to field as this is more elobrative. Is that specific reason why removed the

from the LAMPP Software Bundle page? It serves as a quick intro to the bundle system. Kesavan (talk) 13:42, 24 December 2013 (UTC)[reply]

No, but because of the Firefox icon. There are much more Browsers available, e.g. Uzbl, Midori, Rekonq, Konqueror, or Web. ScotXW (talk) 12:29, 16 February 2014 (UTC)[reply]

Hi ScottXW. User:kevjonesin here.

A modest request ... Please add an explanation regarding the change from "Enlightenment (window manager)" to "Enlightenment (software)" to the article's current talk page. I backtracked and eventually found your edit summary but a talk page entry would be more readily discoverable and would allow room for both a more detailed explanation for the change and for one's fellow editors to respond to such.

Perhaps in the future as a courtesy one might consider making a talk page entry first and then allow a window-of-opportunity for other editors to weigh in on 'whether' and 'what' to rename the article.

Thanks for your time and attention,
--Kevjonesin (talk) 01:38, 17 February 2014 (UTC)[reply]

The changes are justified in the edit summary. ScotXW (talk) 19:13, 27 February 2014 (UTC)[reply]

Hello. Today you added a couple of references in Wayland (display server protocol). The first about randr extension to Weston: that's only a proposal, and probably it's not going to be accepted (see the replies in wayland-devel). The second (libinput), I think is better suited to "Weston" section than "Compatibility with X" section (because X.Org server internally using libinput has nothing to do with the compability with X protocol applications; remember: X Window System is the specification, X.Org Server is one of several implementations of such specification). --JavierCantero (talk) 19:02, 27 February 2014 (UTC)[reply]

Ah, my mistake. But, damn'it, Javier, you can't be fast enough in this software business.

Also, when can I start playing Civ5 natively on my Linux box? As far as I understand, Wayland (and DRI and all the other stuff that came so late to Linux because of X11) should make things more performant and seriously clean up the code base. That means less people are required. The means, the other people could now do other stuff, stuff that would motivate Sid Meyer to port Civ5 to Linux single-handedly. ScotXW (talk) 19:13, 27 February 2014 (UTC)[reply]

I'm afraid that Civ5 or any other game will be ported to OpenGL (over X or Wayland, really it doesn't matter) when their owners think there is profit in the Linux market. :-/ --JavierCantero (talk) 20:57, 27 February 2014 (UTC)[reply]

Updated. -j.eng (talk) 02:15, 28 February 2014 (UTC)[reply]

Hi.

I think you need to help me understand because the more I look at the edits that you did to {{Virtualization products}}, the less I understand what you did to it and the more reason to revert it all.

• First, emulators: Is emulator not another name for hypervisor? If yes, then why a separate section? If no, then what is it doing in the {{Virtualization products}} in the first place?
• Same goes with OS-level virtualization: Hypervisors do that; so why having a separate OS-level virtualization? Then again, when something is part of an OS, it is not a product.

Look, if you want to create a template that categorizes virtualization techniques vs. virtualization products, you are free to make your own template. But I am not sure if that was what you intended to do either. So, could you please clarify what I am looking at?

Best regards,
Codename Lisa (talk) 10:55, 22 March 2014 (UTC)[reply]

Oh, that template is not my work:

* First: I would not create anything with "product" in it. That is the Wikipedia, not the WikiMarketing. That template already existed.

* Second, I'd like to tidy up a little bit, so I parked several articles in that template, with the questionable name.

* Third, the article hypervisor distinguished between "bare metal" and "hosted" hypervirors, though it would also be rather be more interesting to distinguish between microkernelized and "full OS" hypervisors. Maybe I am going to add this classification, I haven't got to it so far. Do you want to do that, because of your expertise?

* 4th: the article Operating system–level virtualization already exists, and it explains things..., so why not link to it?

* oh an 5th: calling edits "good faith" edits does make you appear smarter only to a certain type of people... User:ScotXW^t@lk 11:05, 22 March 2014 (UTC)[reply]

Hi again

1. Yes, that's true; in fact I know who made it. ;) But "product" is not a word to avoid. It is a neutral word that means something is "produced". I even used it in a Featured Article and none of the reviewers minded.
2. I guess that's exactly why I am here.
3. Mutually exclusive categorization is okay, but cross-categorization only brings confusion for our target audience: Those who do not understand where the stuff overlaps.
4. Because using it in the context of the template makes no sense. It is a technique, not a mutually exclusive genre of virtualization software. For example, Hyper-V is a bare metal hypervisor that uses operating system–level virtualization (Enlightened I/O) in Windows Server 2012. The link to Hyper-V must at the same time be in both categories.
5. Oh, I know. But then, put yourself in my shoes: I reverted your edits only because I perceived them as confusing, per WP:BRD, while I was certain that your edits were done with the intention to help. Which one of the three buttons must I choose?

Best regards,

Codename Lisa (talk) 12:56, 22 March 2014 (UTC)[reply]

# I din't suggest to avoid the work "product", I am simply no interested in working on this level. Due to laziness and time constraint I did it in this case...!

# Ok.

# I didn't say mutually exclusive categorization wasn't ok, I simply hinted that a different classification is missing!

# Yes, I should have rather created a new template simply called {{Virtualization}} and there not bother with all the wonderful "products" but rather the underlying technologies. I should have done that in the first place. BTW, isn't it odd, that such a template does not exist, but there is one for all some of the wonderful products out there? I am against deleting such attempts, but is sad. Wikipedia is for explaining stuff and not for marketing purposes... well, deleting it, won't bring quality authors back to the Wikipedia, will it?

# Oh, sorry, I can't put myself in your shoes. And as my edits should prove, I am clearly somebody who has no interested in advertising or spreading FUD. User:ScotXW^t@lk 13:23, 22 March 2014 (UTC)[reply]

Hi. Your answers brings us a lot closer to a consensus. That's great. I have no problem with classifying the hypervisors in more than one categories: A native vs. hosted and a technique-based (emulators, OS-level, etc.) Of course, all of these are subcategories of hosted hypervisors, regardless of whether they are part of the supervisor or under it. (They are not above it.) We can also rename the template {{Virtualization software}} if you wish. But the reason I chose "Virtualization product" is because with this name, it can accommodate hardware and services as well. Best regards, Codename Lisa (talk) 17:52, 24 March 2014 (UTC)[reply]

Here is what I come up with: User:ScotXW/Template:Virtualization User:ScotXW^t@lk 14:23, 22 March 2014 (UTC)[reply]

Ouch! A very bad idea. You are allowed to make it, without doubt, but such a name means things can come into it that you do not like. Its function and classification might change so dramatically that the reason you made it might become irrelevant. Best regards, Codename Lisa (talk) 17:52, 24 March 2014 (UTC)[reply]

From By Ulrich Gräf at Sun GmbH, in ze German language, IMO one the best explanations of "Virtualization" in the entire Internet:

• http://www.youtube.com/watch?v=1s9Se65efes
• http://www.youtube.com/watch?v=9R8H00EkQ-g
• http://www.youtube.com/watch?v=oZwnr3mQTfg
• a sniffy article can be found: http://wiki.ubuntuusers.de/Virtualisierung

Still way better, than the article Virtualization or ze article de:Virtualisierung (Informatik), though the English article is completely shit, as it explains squat. User:ScotXW^t@lk 11:20, 22 March 2014 (UTC)[reply]

Hi. I will study these when I went home. Company firewall has blocked access to YouTube. Best regards, Codename Lisa (talk) 12:56, 22 March 2014 (UTC)[reply]

Hello there! Regarding deletion of the "Unified hierarchy" section in cgroups article, please don't get me wrong – I totally appreciate your work here, but the content of that section is simply not good enough. It talks too much about general things, without providing what actually should be provided – the description of the cgroups' unified hierarchy. Having so much "fluff" would be acceptable, but only for a section that's about five times longer than what you've provided.

Once again, please don't get me wrong, and I hope you agree. Of course, I'm more than open for further discussion. — Dsimic (talk | contribs) 03:21, 24 March 2014 (UTC)[reply]

As most of my work here, it is work-in-progress and not fire-and-forget. If you keep deleting it, it'll never grow lager. User:ScotXW^t@lk 11:04, 24 March 2014 (UTC)[reply]

Understood, but can't you build it a bit further before spitting it out, so to speak? By the way, the whole cgroups article has been around for a while, and it hasn't grown that much – it isn't something that attracts a wide audience itching to expand sections. — Dsimic (talk | contribs) 14:23, 24 March 2014 (UTC)[reply]

Yes yes, I agree, it needs more "substance" to quote Kissinger, and doing work regarding it in some user-space won't make it better. Also, development was just picked up again, by Hejun Teo et al. Major changes like the mentioned unified hierarchy is underway. So devel is work-in-progress and so is the article. User:ScotXW^t@lk 14:28, 24 March 2014 (UTC)[reply]

On the other hand, and according to WP:NOTNEWS, we should either wait for things to reach their production stages, or wait until there are reliable sources available. Hope you agree. — Dsimic (talk | contribs) 17:38, 24 March 2014 (UTC)[reply]

The sources I quoted are as reliable as they can get... User:ScotXW^t@lk 17:38, 24 March 2014 (UTC)[reply]

No doubt about that, but there isn't enough "meat". :) — Dsimic (talk | contribs) 17:41, 24 March 2014 (UTC)[reply]

Heck, just noticed that this section provides zero references. Please stop re-adding it until it provides more of the usable content. — Dsimic (talk | contribs) 02:21, 25 March 2014 (UTC)[reply]

Here's something that might be a good solution – I'll try to provide more content for that section, merging it with what you've already provided and restoring it all together. Hope you agree. — Dsimic (talk | contribs) 06:58, 25 March 2014 (UTC)[reply]

Sure, go ahead. User:ScotXW^t@lk 10:48, 25 March 2014 (UTC)[reply]

Thank you, and sorry for the delay. I'll do that in the next day or two. — Dsimic (talk | contribs) 06:25, 27 March 2014 (UTC)[reply]

Once again, sorry for the delay; got a bit distracted. — Dsimic (talk | contribs) 05:21, 1 April 2014 (UTC)[reply]

No problem, I fixed it. User:ScotXW^t@lk 10:31, 7 April 2014 (UTC)[reply]

Sorry, but I have to note that you're far away from being polite. Why did you have to write the following in your edit comment?

'in case you are not capable of "contributing"'

It hurts my feelings, while I bet you're not smarter or more knowledgeable than me. If you wanted to ping me about this, what was reasonable, this talk page was the place for that. — Dsimic (talk | contribs) 04:15, 8 April 2014 (UTC)[reply]

Let us both contribute text, and then work on that text. Let us not delete and remove stuff, if its not that bad. We already agreed it was fluffy. And I also told you, its WIP, i.e. I am on it. User:ScotXW^t@lk 09:50, 9 April 2014 (UTC)[reply]

Ok, I'll add some more content and edit that section a bit, and you can take it from there. — Dsimic (talk | contribs) 16:49, 9 April 2014 (UTC)[reply]

Hi Scot, just wondering what this edit was about? Samwalton9 (talk) 13:00, 25 March 2014 (UTC)[reply]

Oh that. Oculus sent their "Joker" to make a funny presentation about the implications of VR... and I felt the urge to share the "take aways" from that particular presentation. I guess they can be removed again from the article. User:ScotXW^t@lk 13:08, 25 March 2014 (UTC)[reply]

Hi Scot, I suggest you have a read of WP:UPNOT; particularly regarding excessive unrelated content. Sam Walton (talk) 22:24, 27 March 2014 (UTC)[reply]

I just did Sam: "User pages are pages in the User and User talk namespaces, and are useful for organizing and aiding the work users do on Wikipedia". Anything else? User:ScotXW^t@lk 10:20, 28 March 2014 (UTC)[reply]

Just thought the parts about "Writings, information, discussions, and activities not closely related to Wikipedia's goals" probably applied to the writings regarding your opinions on 'crippleware' located on your userpage. Sam Walton (talk) 17:07, 28 March 2014 (UTC)[reply]

I'd like to also point out that your "Wikipedia Deletion Heros" are a personal attack and don't help anyone. Sam Walton (talk) 18:15, 10 April 2014 (UTC)[reply]

How so? It helps in that patterns could be determined. Ye know, in case somebody targets the work of somebody particular, or a particular group of articles. Could be articles related to software in general, or articles related to races, language, you name it. Isn't there some tool for such cases? User:ScotXW^t@lk 18:19, 10 April 2014 (UTC)[reply]

A discussion is taking place as to whether the article GNOME Maps is suitable for inclusion in Wikipedia according to Wikipedia's policies and guidelines or whether it should be deleted.

The article will be discussed at Wikipedia:Articles for deletion/GNOME Maps until a consensus is reached, and anyone is welcome to contribute to the discussion. The nomination will explain the policies and guidelines which are of concern. The discussion focuses on high-quality evidence and our policies and guidelines.

Users may edit the article during the discussion, including to improve the article to address concerns raised in the discussion. However, do not remove the article-for-deletion notice from the top of the article. QVVERTYVS (hm?) 17:05, 28 March 2014 (UTC)[reply]

As a recent and major contributor to this template you may want to add something to this discussion on reducing the size of this template. - Ahunt (talk) 10:36, 31 March 2014 (UTC)[reply]

A tag has been placed on Klavaro, requesting that it be speedily deleted from Wikipedia. This has been done under the criteria for speedy deletion, because the page seems to be unambiguous advertising that only promotes a company, product, group, service or person and would need to be fundamentally rewritten in order to become an acceptable page. Please read the general criteria for speedy deletion, particularly item G11, as well as the guidelines on spam.

If you can indicate why the subject of this page is not blatant advertising, . Clicking that button will take you to the talk page where you will find a pre-formatted place for you to explain why you believe the page should not be deleted. You can also visit the page's talk page directly to give your reasons, but be aware that once tagged for speedy deletion, if the page meets the criterion, it may be deleted without delay. You are welcome to edit the page to fix this problem, but please do not remove the speedy deletion tag yourself. As well as removing promotional phrasing, it helps to add factual encyclopaedic information to the page, and add citations from independent reliable sources to ensure that the page will be verifiable. Feel free to leave a note on my talk page if you have any questions about this. LordFixit (talk) 15:51, 15 April 2014 (UTC)[reply]

The article Klavaro has been proposed for deletion because of the following concern:

Does not meet WP:GNG

While all constructive contributions to Wikipedia are appreciated, content or articles may be deleted for any of several reasons.

You may prevent the proposed deletion by removing the {{proposed deletion/dated}} notice, but please explain why in your edit summary or on the article's talk page.

Please consider improving the article to address the issues raised. Removing {{proposed deletion/dated}} will stop the proposed deletion process, but other deletion processes exist. In particular, the speedy deletion process can result in deletion without discussion, and articles for deletion allows discussion to reach consensus for deletion. LordFixit (talk) 13:31, 19 April 2014 (UTC)[reply]

Category:Linux Foundation silver members, which you created, has been nominated for possible deletion, merging, or renaming. If you would like to participate in the discussion, you are invited to add your comments at the category's entry on the Categories for discussion page. Thank you. Thomas.W ^talk 16:17, 7 May 2014 (UTC)[reply]

Category:Linux Foundation gold members, which you created, has been nominated for possible deletion, merging, or renaming. If you would like to participate in the discussion, you are invited to add your comments at the category's entry on the Categories for discussion page. Thank you. Thomas.W ^talk 16:18, 7 May 2014 (UTC)[reply]

Category:Linux Foundation platinum members, which you created, has been nominated for possible deletion, merging, or renaming. If you would like to participate in the discussion, you are invited to add your comments at the category's entry on the Categories for discussion page. Thank you. Thomas.W ^talk 16:19, 7 May 2014 (UTC)[reply]

Hello. I noticed that you added my user name to a "wall of shame" on your user page, a list of users who among other things have nominated pages you created for deletion, so I thought I'd point you to WP:UP#POLEMIC, a list of things users are not allowed to have on their user page. Where you will find that "Material that can be viewed as attacking other editors, including the recording of perceived flaws" can not be posted on user pages. So I very strongly suggest you remove that list ASAP. Thomas.W ^talk 16:49, 7 May 2014 (UTC)[reply]

Hello, I noticed that your user subpage at User:ScotXW may not meet Wikipedia's user page guideline. If you believe that your user page does not violate our guideline, please leave a note on this page. Alternatively you may add {{Db-userreq}} to the top of the page in question and an administrator will delete it, or you can simply edit the page so that it meets Wikipedia's user page guideline. It has been politely pointed out to you twice, by two different users, on your talk page that having a "wall of shame" on your user page, naming and shaming other editors, is against the rules here on WP; but since you have chosen not to act on it you now get a more formal warning. Thomas.W ^talk 07:17, 9 May 2014 (UTC)[reply]

Many things ridiculous ...; I will never take people like you seriously. User:ScotXW^t@lk 08:45, 9 May 2014 (UTC)[reply]

Hello, I'm BracketBot. I have automatically detected that your edit to CAN may have broken the syntax by modifying 1 "[]"s. If you have, don't worry: just edit the page again to fix it. If I misunderstood what happened, or if you have any questions, you can leave a message on my operator's talk page.

List of unpaired brackets remaining on the page:

• * [CAN bus]], controller area network bus, a type of microcontroller bus

It's OK to remove this message. Also, to stop receiving these messages, follow these opt-out instructions. Thanks, BracketBot (talk) 09:35, 27 May 2014 (UTC)[reply]

There is currently a discussion at Wikipedia:Administrators' noticeboard/Incidents regarding an issue with which you may have been involved. Thank you. Thomas.W ^talk 09:15, 9 May 2014 (UTC)[reply]

I have removed this list from your userpage under WP:POLEMIC, since you do not appear willing to do so. Please do not use your userpage for inappropriate purposes like this. Yunshui ^雲_水 09:28, 9 May 2014 (UTC)[reply]

• If I can expand on that a bit: We don't allow lists like this because it can be a source of disagreement and arguments. Wikipedia is a collaborative environment, and we try to promote a collegiate atmosphere. Lists like this look like an "enemies list", and often are. We don't want to encourage grudges or lists that might appear to be hateful. We are all human, there will always be those whom we strongly disagree or we simply have a very different perspective about what is "notable" and what isn't. The whole idea of a community is we each have a voice and agree to go along with what most people want, but almost always, someone will disagree with your ideas. Enemy lists are divisive and don't really help in building the encyclopedia. Also note that in this case, the removal was just a reminder, not a sanction. Dennis Brown | 2¢ | WER 13:14, 9 May 2014 (UTC)[reply]

Your recent editing history at Template:Firewall software shows that you are currently engaged in an edit war. Being involved in an edit war can result in your being blocked from editing—especially if you violate the three-revert rule, which states that an editor must not perform more than three reverts on a single page within a 24-hour period. Undoing another editor's work—whether in whole or in part, whether involving the same or different material each time—counts as a revert. Also keep in mind that while violating the three-revert rule often leads to a block, you can still be blocked for edit warring—even if you don't violate the three-revert rule—should your behavior indicate that you intend to continue reverting repeatedly.

To avoid being blocked, instead of reverting please consider using the article's talk page to work toward making a version that represents consensus among editors. See BRD for how this is done. You can post a request for help at a relevant noticeboard or seek dispute resolution. In some cases, you may wish to request temporary page protection.
So far I've counted three reverts within 24 hours. A fourth revert in that time period may result in a block. Minima© (talk) 10:44, 17 May 2014 (UTC)[reply]

Policy is very clear on this. From WP:UP: "Users should generally not maintain in public view negative information related to others without very good reason. Negative evidence, laundry lists of wrongs, collations of diffs and criticisms related to problems, etc., should be removed, blanked, or kept privately (i.e., not on the wiki) if they will not be imminently used, and the same once no longer needed." You are not permitted to "keep track of the people whom I see as disruptive" on-wiki. By all means keep a file on your computer listing your enemies, nemeses and anyone who's ever slighted you or looked at you funny, but do not do so here. Yunshui ^雲_水 07:06, 20 May 2014 (UTC)[reply]

I am aware that I could keep such a list written with a pen on a paper... The point is, to be able to klick on the user's contribution, to see if they continue to behave that have, i.e. they are vandals. And, in case somebody would stumble over that list in the corner (do you want me to make a screenshot, maybe to show you the difference between a simple list and a real wall of shame?), other could have a look as well. Or maybe its really just me.... However, my argument is, and that is a proven fact, that what the Wikipedia users (please note: not people, persons or individuals) have done, is NOT negative. They did it, and got away with it. Ergo, it is something good, not something negative. Ergo, the rule you quote, does not apply, judge. Sorry, you seem to act as a judge, so let me address you correctly. And please, do obey "the rules". They have not done something negative, oh no, they did right. Also, it is not a wall of shame. Its a "list". The positive and constructive contributions, that's the hero stands for. We could agree on another denominations, something with almost barn-star grade users or similar. Do you have a suggestion? I am the bad person here. The vandal. By all means, put me on a list.

Oh, kudos to the Wikipedia bureaucracy, the un-convoluted, strait forward and clear cut rules, but see yourself Bird and Fortune: George Parr, Home Office Minister on YouTube User:ScotXW^t@lk 10:53, 20 May 2014 (UTC)[reply]

You have specifically stated that you keep a list on your userpage of users whom you consider disruptive, and that you regularly check their contributions for anything that you could report as vandalism (a form of harassment). As I and other users have pointed out to you, this is not acceptable behaviour in a collaborative editing environment, and is specifically prohibited by the community's rules. Much as I dislike having to make alterations to other editors' userpages I am removing the list for a third time; kindly do not restore it. Yunshui ^雲_水 13:11, 20 May 2014 (UTC)[reply]

Let me add this: If you are working on an ANI or ARB report, then a working draft is considered acceptable. Same if you are working with a user (good or bad) for a short term issue (a few weeks max), say to show they are using stealth vandalism to change scores in sports articles, etc. A short term project that requires it and you can point to the specific issue. If you are just making a list for posterity, then it isn't. I keep a few links offline (Yahoo notepad is handy for this), although most of those are just informative or seldom needed but hard to find links, and some funny stuff. A few would be problematic here as being negative, which is why I don't keep any of them here at wikipedia, for the same reason your list was deleted. The community says it doesn't want the lists here, our jobs is just to do the bidding of the community, by enforcing that clearly stated desire. That rule applies to you the same as it applies to me. Dennis Brown | 2¢ | WER 18:28, 20 May 2014 (UTC)[reply]

(talk page stalker) Yeah, nobody should be above the rules. ScotXW, if you disagree with the rules (what's perfectly fine), it's always possible to go to appropriate talk pages and try to get those rules changed. — Dsimic (talk | contribs) 06:30, 21 May 2014 (UTC)[reply]

There are rules, which I understand why they were put up in the first place. And there are the ones, which I deem "convoluted". I understand there is a rule "bla bla bla, but I don't understand the argument behind this rule. So, it shames me to say, that I do not give a fuck about this rule. You may force me to obey it, but I think I'd rather leave, then be governed by rules, I do not understand. Add to this rule, the whole very convoluted Wikipedia bureaucracy and something like Kafka's The Trial comes to mind. Other have repeatedly publicly opposed this condition, the CCC comes to mind, with arguments that do make sense. I am simply just another unhappy (ex-)wikipedia contributor. I left long time ago, and came back to find the same shit again. User:ScotXW^t@lk 07:30, 21 May 2014 (UTC)[reply]

Regarding this particular rule, it's similar to why spraying "Joe is a fuc*in' idiot" on a wall doesn't solve any issues. If you go and write that on a wall, it's only going to make Joe angry and even more of an idiot – nothing gets better. On the other hand, if you sit down with Joe and try to discuss and find a solution for the issue which makes you think of Joe as an idiot, that has a potential for making things better. Of course, there are always quite a few cases for which all of the discussion yields nothing. — Dsimic (talk | contribs) 08:05, 21 May 2014 (UTC)[reply]

Just that it ain't. I didn't write "idiot". I didn't write "wall of shame". I just assembled a (rather very small) list of people who delete articles (or propose articles for deletion). Articles I invested time and energy to write. If you thing, people who invest so much energy to delete such work are a bunch of morons or imbeciles, well, that is your opinion. I just put up a simply list in the corner of my user page. Amazing, what kind of attention this draws, ain't it. So much time and energy for shit. For nothing. While actual text, get's deleted. Wow. I highly doubt the consensus behind such "efforts". User:ScotXW^t@lk 09:28, 21 May 2014 (UTC)[reply]

You're twisting it again. Anyway, every system has a set of its own rules, in the end that's how the whole world works. Until the rules are changed, they're here for us to play by them – and to challenge and adjust them through discussion. — Dsimic (talk | contribs) 10:06, 21 May 2014 (UTC)[reply]

If you insist... User:ScotXW^t@lk 10:07, 21 May 2014 (UTC)[reply]

It isn't me pushing anything. That's how Wikipedia works, as simple as that. — Dsimic (talk | contribs) 10:12, 21 May 2014 (UTC)[reply]

There is currently a discussion at Wikipedia:Administrators' noticeboard/Incidents regarding an issue with which you may have been involved. The thread is ScottXW and his "deletion heros". Thank you. Yunshui ^雲_水 08:29, 21 May 2014 (UTC)[reply]

Hi. Thank you for your recent edits. Wikipedia appreciates your help. We noticed though that when you edited Political particularism, you added a link pointing to the disambiguation page Particularism (check to confirm | fix with Dab solver). Such links are almost always unintended, since a disambiguation page is merely a list of "Did you mean..." article titles. Read the FAQ • Join us at the DPL WikiProject.

It's OK to remove this message. Also, to stop receiving these messages, follow these opt-out instructions. Thanks, DPL bot (talk) 08:55, 21 May 2014 (UTC)[reply]

Scot, you've been here a while, given a lot of good contribs and have recently found some problems with the POLEMIC list and now Wikipedia:Sockpuppet investigations/ScotXW. If that is you, now would be a good time to go to that case and fess up. If not, then CU will clear it up pretty quick. I'm not sure what to make of it, which is why I filed the case instead of assume and block. You are at a crossroads here. It really isn't required that you agree with every policy. I'm an admin and there are plenty I disagree with. I have a banner on my user page to that effect now. But I have no choice to work within the system until I can change the things I don't like. Or just accept those that I can't change. Think about it, most of the time, policy is pretty meaningless, we just add facts and sources and go about our merry little way without giving them a second thought, but they are still there because tens of thousands of people edit Wikipedia regularly and it would be a madhouse without some basic "rules". More importantly, we have to apply the rules to everyone equally: you, me, everyone. I genuinely fear that you are on a bad road right now and hope you will rethink your methods.

It is fine to think a policy is stupid, but we need people to more or less follow it anyway. If you think I'm a flaming idiot, that is fine too, just don't say it onwiki. Not because it will hurt my feelings (it won't, trust me) but because it fosters a negative environment. Different policy, but same idea. Policy enforcement is like that, it isn't always about that specific event, it is about equity in how we treat everyone. Some polemic lists are worse than others, but we have to disallow all of them. This whole thing isn't about singling you out, no matter how much it might seem that way. It is about treating you exactly the same as everyone else. Dennis Brown | 2¢ | WER 15:19, 22 May 2014 (UTC)[reply]

An editor has asked for a discussion to address the redirect NoFlo. Since you had some involvement with the NoFlo redirect, you might want to participate in the redirect discussion if you have not already done so. — Dmitrij D. Czarkoff (talk•track) 11:59, 24 May 2014 (UTC)[reply]

Category:Heterogeneous System Architecture, which you created, has been nominated for possible deletion, merging, or renaming. If you would like to participate in the discussion, you are invited to add your comments at the category's entry on the Categories for discussion page. Thank you. QVVERTYVS (hm?) 10:47, 29 May 2014 (UTC)[reply]

Hi. Thank you for your recent edits. Wikipedia appreciates your help. We noticed though that when you edited List of Linux supported computer architectures, you added a link pointing to the disambiguation page Processor (check to confirm | fix with Dab solver). Such links are almost always unintended, since a disambiguation page is merely a list of "Did you mean..." article titles. Read the FAQ • Join us at the DPL WikiProject.

It's OK to remove this message. Also, to stop receiving these messages, follow these opt-out instructions. Thanks, DPL bot (talk) 08:57, 2 June 2014 (UTC)[reply]

You are invited to join the discussion at Template talk:3D software#Classification added on 2 June 2014. Thanks. Codename Lisa (talk) 11:22, 2 June 2014 (UTC)[reply]

Since you continue to respond our messages about edits with impolite personal attacks, I am giving you your last warning. You are engaged with three editors in a dispute and are refusing to adhere to WP:BRD. If you continue to do so, you will be reported to WP:ANI.

Best regards,
Codename Lisa (talk) 12:43, 2 June 2014 (UTC)[reply]

WP:AN3 would be the best venue to report this kind of behaviour. Regards — Martin (MSGJ · talk) 13:12, 2 June 2014 (UTC)[reply]

Your recent editing history at Template:3D software shows that you are currently engaged in an edit war. Being involved in an edit war can result in your being blocked from editing—especially if you violate the three-revert rule, which states that an editor must not perform more than three reverts on a single page within a 24-hour period. Undoing another editor's work—whether in whole or in part, whether involving the same or different material each time—counts as a revert. Also keep in mind that while violating the three-revert rule often leads to a block, you can still be blocked for edit warring—even if you don't violate the three-revert rule—should your behavior indicate that you intend to continue reverting repeatedly.

To avoid being blocked, instead of reverting please consider using the article's talk page to work toward making a version that represents consensus among editors. See BRD for how this is done. You can post a request for help at a relevant noticeboard or seek dispute resolution. In some cases, you may wish to request temporary page protection. --Guy Macon (talk) 18:21, 2 June 2014 (UTC)[reply]

Hello, I'm BracketBot. I have automatically detected that your edit to Direct Rendering Manager may have broken the syntax by modifying 2 "[]"s and 1 "<>"s. If you have, don't worry: just edit the page again to fix it. If I misunderstood what happened, or if you have any questions, you can leave a message on my operator's talk page.

List of unpaired brackets remaining on the page:

• arbitrary (scattered) subset of the system's RAM pages are accessible to the GPU.<ref>{{cite web <url=http://lwn.net/Articles/257417/ |title=Memory management for graphics processors |work=[[LWN.
• 257417/ |title=Memory management for graphics processors |work=[[LWN.net]] |date=2007-11-06]]}}</ref>

It's OK to remove this message. Also, to stop receiving these messages, follow these opt-out instructions. Thanks, BracketBot (talk) 14:44, 6 June 2014 (UTC)[reply]

Hello, I'm BracketBot. I have automatically detected that your edit to PCB (software) may have broken the syntax by modifying 1 "()"s. If you have, don't worry: just edit the page again to fix it. If I misunderstood what happened, or if you have any questions, you can leave a message on my operator's talk page.

List of unpaired brackets remaining on the page:

• | operating system = [[Unix-like]] ([[Berkeley Software Distribution|BSDs]], [[Linux]], [[Solaris (operating system)|Solaris]], {{

It's OK to remove this message. Also, to stop receiving these messages, follow these opt-out instructions. Thanks, BracketBot (talk) 10:34, 10 June 2014 (UTC)[reply]

Hello, I'm BracketBot. I have automatically detected that your edit to Cinnamon (software) may have broken the syntax by modifying 1 "()"s. If you have, don't worry: just edit the page again to fix it. If I misunderstood what happened, or if you have any questions, you can leave a message on my operator's talk page.

List of unpaired brackets remaining on the page:

• | genre = {{ubl|[[Desktop environment]]|initially [[Graphical shell]])}}

It's OK to remove this message. Also, to stop receiving these messages, follow these opt-out instructions. Thanks, BracketBot (talk) 11:00, 14 June 2014 (UTC)[reply]

Hello, I'm BracketBot. I have automatically detected that your edit to AMD Accelerated Processing Unit may have broken the syntax by modifying 1 "()"s. If you have, don't worry: just edit the page again to fix it. If I misunderstood what happened, or if you have any questions, you can leave a message on my operator's talk page.

List of unpaired brackets remaining on the page:

• * GPU: [[Graphics Core Next]]-based with 192–512 shader processors (branded "AMD Radeon R4 graphics", (800&nbsp;MHz over the 600&nbsp;MHz of "R3" graphics),

It's OK to remove this message. Also, to stop receiving these messages, follow these opt-out instructions. Thanks, BracketBot (talk) 08:44, 23 June 2014 (UTC)[reply]

Hello, I'm BracketBot. I have automatically detected that your edit to Vivante Corporation may have broken the syntax by modifying 1 "[]"s. If you have, don't worry: just edit the page again to fix it. If I misunderstood what happened, or if you have any questions, you can leave a message on my operator's talk page.

List of unpaired brackets remaining on the page:

• the [[GNU General Public License]] (GPL), instead of maintaining this a proprietary blob. The free [[Gallium3D]-style device driver <code>etna_viv</code> has surpassed Vivante's own proprietary user-

It's OK to remove this message. Also, to stop receiving these messages, follow these opt-out instructions. Thanks, BracketBot (talk) 07:44, 24 June 2014 (UTC)[reply]

Hello, I'm BracketBot. I have automatically detected that your edit to X.Org Server may have broken the syntax by modifying 1 "{}"s. If you have, don't worry: just edit the page again to fix it. If I misunderstood what happened, or if you have any questions, you can leave a message on my operator's talk page.

List of unpaired brackets remaining on the page:

• Glamor requires a 3D driver with shader support.<ref>{{cite web |url=http://xorg.freedesktop.org/wiki/RadeonFeature/ |title=Radeon Feature Matrix |work=[[

It's OK to remove this message. Also, to stop receiving these messages, follow these opt-out instructions. Thanks, BracketBot (talk) 19:40, 24 June 2014 (UTC)[reply]

Hello, I'm BracketBot. I have automatically detected that your edit to Graphics Execution Manager may have broken the syntax by modifying 1 "()"s. If you have, don't worry: just edit the page again to fix it. If I misunderstood what happened, or if you have any questions, you can leave a message on my operator's talk page.

List of unpaired brackets remaining on the page:

• [[evdev]] is to the INPUT what the GEM is to the OUTPUT. Many applications require the entire loop (INPUT-PROCESSING-OUPUT to have minimal [[Latency (engineering)|latency]]
• devices such as Keyboard, Mouse, Touch-Pad, etc. The data is passed to the [[Display server]] (e.g. the [[X.Org Server]] or some [[Wayland compositor]] only to be passed further to the wayland

It's OK to remove this message. Also, to stop receiving these messages, follow these opt-out instructions. Thanks, BracketBot (talk) 17:36, 25 June 2014 (UTC)[reply]

Hello, I'm BracketBot. I have automatically detected that your edit to Look and feel may have broken the syntax by modifying 1 "()"s. If you have, don't worry: just edit the page again to fix it. If I misunderstood what happened, or if you have any questions, you can leave a message on my operator's talk page.

List of unpaired brackets remaining on the page:

• or by completely defining their own. This specialization can go from [[Skin (computing)|skinning]] (that only deals with the look, or visual appearance of the [[Graphical control element (software)|

It's OK to remove this message. Also, to stop receiving these messages, follow these opt-out instructions. Thanks, BracketBot (talk) 14:43, 29 June 2014 (UTC)[reply]

I just wanted to thank you for your work on the OpenEMR wikipedia page. Bradygmiller (talk) 20:13, 8 June 2014 (UTC)[reply]

Hi. Thank you for your recent edits. Wikipedia appreciates your help. We noticed though that when you edited Tachyon (software), you added a link pointing to the disambiguation page Render (check to confirm | fix with Dab solver). Such links are almost always unintended, since a disambiguation page is merely a list of "Did you mean..." article titles. Read the FAQ • Join us at the DPL WikiProject.

It's OK to remove this message. Also, to stop receiving these messages, follow these opt-out instructions. Thanks, DPL bot (talk) 08:50, 9 June 2014 (UTC)[reply]

Your recent editing history at GNOME Shell shows that you are currently engaged in an edit war. Being involved in an edit war can result in your being blocked from editing—especially if you violate the three-revert rule, which states that an editor must not perform more than three reverts on a single page within a 24-hour period. Undoing another editor's work—whether in whole or in part, whether involving the same or different material each time—counts as a revert. Also keep in mind that while violating the three-revert rule often leads to a block, you can still be blocked for edit warring—even if you don't violate the three-revert rule—should your behavior indicate that you intend to continue reverting repeatedly.

To avoid being blocked, instead of reverting please consider using the article's talk page to work toward making a version that represents consensus among editors. See BRD for how this is done. You can post a request for help at a relevant noticeboard or seek dispute resolution. In some cases, you may wish to request temporary page protection. Aoidh (talk) 17:24, 14 June 2014 (UTC)[reply]

Undoing another editor's "work"? What "work" do you mean? It is the other way around. ... User:ScotXW^t@lk 19:14, 14 June 2014 (UTC)[reply]

Please read WP:EW if you're unclear what that means, but this is an edit (e.g. the "work"), and repeatedly undoing that without getting a consensus for your edit is edit warring, and if you continue you may be blocked from editing to prevent further edit warring. - Aoidh (talk) 02:09, 15 June 2014 (UTC)[reply]

Sorry, I do not see the "work", the addition, the plus. I see just crap. I very seldomly undo the work of somebody else, it rather that somebody undid my work, addition, plus, and I undid that. Don't you know me by now? Dude, if you were the King of Jamaica, I wouldn't give a damn about your stuff, unless I see a sense in it. A meaning. An argument. And you are, obviously too stupid to present arguments. Maybe somebody should take over, who is entitle to do more, that just crap. User:ScotXW^t@lk 08:51, 15 June 2014 (UTC)[reply]

Hello. This message is being sent to inform you that there is currently a discussion involving you at Wikipedia:Administrators' noticeboard/Edit warring regarding a possible violation of Wikipedia's policy on edit warring. The thread is Wikipedia:Administrators' noticeboard/Edit warring#User:ScotXW reported by User:Czarkoff (Result: ). Thank you. — Dmitrij D. Czarkoff (talk•track) 09:30, 15 June 2014 (UTC)[reply]

You have been blocked from editing for a period of 48 hours for edit warring, reverting against consensus, and personal attacks, as you did at GNOME Shell. Once the block has expired, you are welcome to make useful contributions. If you think there are good reasons why you should be unblocked, you may appeal this block by adding the following text below this notice: {{unblock|reason=Your reason here ~~~~}}. However, you should read the guide to appealing blocks first.  Bbb23 (talk) 14:02, 15 June 2014 (UTC)[reply]

Category:Graphviz, which you created, has been nominated for possible deletion, merging, or renaming. If you would like to participate in the discussion, you are invited to add your comments at the category's entry on the Categories for discussion page. Thank you. QVVERTYVS (hm?) 13:59, 16 June 2014 (UTC)[reply]

Hi. Thank you for your recent edits. Wikipedia appreciates your help. We noticed though that when you edited Processor register, you added a link pointing to the disambiguation page Processor (check to confirm | fix with Dab solver). Such links are almost always unintended, since a disambiguation page is merely a list of "Did you mean..." article titles. Read the FAQ • Join us at the DPL WikiProject.

It's OK to remove this message. Also, to stop receiving these messages, follow these opt-out instructions. Thanks, DPL bot (talk) 08:54, 27 June 2014 (UTC)[reply]

There's an incident report about you at ANI. I think you'll know what it's about. QVVERTYVS (hm?) 14:21, 29 June 2014 (UTC)[reply]

Yes, thanks. User:ScotXW^t@lk 14:22, 29 June 2014 (UTC)[reply]

Hello, I'm BracketBot. I have automatically detected that your edit to GeForce 200 series may have broken the syntax by modifying 1 "{}"s. If you have, don't worry: just edit the page again to fix it. If I misunderstood what happened, or if you have any questions, you can leave a message on my operator's talk page.

List of unpaired brackets remaining on the page:

• {Main|Tesla (microarchitecture)}}

It's OK to remove this message. Also, to stop receiving these messages, follow these opt-out instructions. Thanks, BracketBot (talk) 23:34, 1 July 2014 (UTC)[reply]

Hello, I'm BracketBot. I have automatically detected that your edit to Radeon HD 7000 Series may have broken the syntax by modifying 1 "{}"s. If you have, don't worry: just edit the page again to fix it. If I misunderstood what happened, or if you have any questions, you can leave a message on my operator's talk page.

List of unpaired brackets remaining on the page:

• pdf?raw=true |title=AMD GCN microarchitecture – whitepaper |work=[[Advanced Micro Devices|AMD]]}}</ref> The new implementation of SIMD requires considerably more transistors than the old one of

It's OK to remove this message. Also, to stop receiving these messages, follow these opt-out instructions. Thanks, BracketBot (talk) 00:56, 2 July 2014 (UTC)[reply]

Hello, I'm BracketBot. I have automatically detected that your edit to Snapdragon (system on chip) may have broken the syntax by modifying 1 "()"s. If you have, don't worry: just edit the page again to fix it. If I misunderstood what happened, or if you have any questions, you can leave a message on my operator's talk page.

List of unpaired brackets remaining on the page:

• 7783/qualcomms-snapdragon-801-msm8974ac-the-new-32bit-flagship-until-805] Qualcomm's Snapdragon 801]</ref>
• * support for triple-band (i.e. [[IEEE 802.11]], [[IEEE 802.15]] (Bluetooth) and [[IEEE 802.11ad]] (60GHz).

It's OK to remove this message. Also, to stop receiving these messages, follow these opt-out instructions. Thanks, BracketBot (talk) 12:15, 3 July 2014 (UTC)[reply]

Hello, I'm BracketBot. I have automatically detected that your edit to ZYpp may have broken the syntax by modifying 2 "{}"s. If you have, don't worry: just edit the page again to fix it. If I misunderstood what happened, or if you have any questions, you can leave a message on my operator's talk page.

List of unpaired brackets remaining on the page:

• dependency solver. libsolv is being written and distributed under the [[Revised BSD License]].<ref>{{cite web |url=https://github.com/openSUSE/libsolv |title=libsolv on github</ref>

It's OK to remove this message. Also, to stop receiving these messages, follow these opt-out instructions. Thanks, BracketBot (talk) 02:11, 4 July 2014 (UTC)[reply]

Hello, I'm BracketBot. I have automatically detected that your edit to List of AMD Accelerated Processing Unit microprocessors may have broken the syntax by modifying 2 "[]"s. If you have, don't worry: just edit the page again to fix it. If I misunderstood what happened, or if you have any questions, you can leave a message on my operator's talk page.

List of unpaired brackets remaining on the page:

• amp;nbsp;MHz || 720&nbsp;MHz || DDR3-1600 || rowspan="7" | 35&nbsp;W || Socket FS1|FS1r2]] || Q1 2013 || AM5150DEC23HL

It's OK to remove this message. Also, to stop receiving these messages, follow these opt-out instructions. Thanks, BracketBot (talk) 12:11, 4 July 2014 (UTC)[reply]

Hello, I'm BracketBot. I have automatically detected that your edit to Radeon may have broken the syntax by modifying 2 "{}"s. If you have, don't worry: just edit the page again to fix it. If I misunderstood what happened, or if you have any questions, you can leave a message on my operator's talk page.

It's OK to remove this message. Also, to stop receiving these messages, follow these opt-out instructions. Thanks, BracketBot (talk) 10:19, 6 July 2014 (UTC)[reply]

Hello, I'm BracketBot. I have automatically detected that your edit to AMD TrueAudio may have broken the syntax by modifying 1 "{}"s. If you have, don't worry: just edit the page again to fix it. If I misunderstood what happened, or if you have any questions, you can leave a message on my operator's talk page.

List of unpaired brackets remaining on the page:

• and Mantle Technologies with Thief |work=[[AnandTech]] |date=2014-03-18 |accessdate=2014-07-06}}</ref>

It's OK to remove this message. Also, to stop receiving these messages, follow these opt-out instructions. Thanks, BracketBot (talk) 19:12, 6 July 2014 (UTC)[reply]

Hello, I'm BracketBot. I have automatically detected that your edit to AMD TrueAudio may have broken the syntax by modifying 1 "[]"s. If you have, don't worry: just edit the page again to fix it. If I misunderstood what happened, or if you have any questions, you can leave a message on my operator's talk page.

List of unpaired brackets remaining on the page:

• There is an audio plug-in for [[Audiokinetic]]]'s [[Audiokinetic Wwise|Wwise]] (Wave Works Interactive Sound Engine) to off-load computation to

It's OK to remove this message. Also, to stop receiving these messages, follow these opt-out instructions. Thanks, BracketBot (talk) 08:05, 7 July 2014 (UTC)[reply]

Hello, I'm BracketBot. I have automatically detected that your edit to Sylpheed may have broken the syntax by modifying 1 "{}"s. If you have, don't worry: just edit the page again to fix it. If I misunderstood what happened, or if you have any questions, you can leave a message on my operator's talk page.

List of unpaired brackets remaining on the page:

• {GTK}}

It's OK to remove this message. Also, to stop receiving these messages, follow these opt-out instructions. Thanks, BracketBot (talk) 16:00, 8 July 2014 (UTC)[reply]

Hello, I'm BracketBot. I have automatically detected that your edit to Claws Mail may have broken the syntax by modifying 1 "{}"s. If you have, don't worry: just edit the page again to fix it. If I misunderstood what happened, or if you have any questions, you can leave a message on my operator's talk page.

List of unpaired brackets remaining on the page:

• {GTK}}

It's OK to remove this message. Also, to stop receiving these messages, follow these opt-out instructions. Thanks, BracketBot (talk) 16:01, 8 July 2014 (UTC)[reply]

Hello, I'm BracketBot. I have automatically detected that your edit to Audacious (software) may have broken the syntax by modifying 1 "{}"s. If you have, don't worry: just edit the page again to fix it. If I misunderstood what happened, or if you have any questions, you can leave a message on my operator's talk page.

List of unpaired brackets remaining on the page:

• {GTK}}

It's OK to remove this message. Also, to stop receiving these messages, follow these opt-out instructions. Thanks, BracketBot (talk) 16:09, 8 July 2014 (UTC)[reply]

Hello, I'm BracketBot. I have automatically detected that your edit to HyperZ may have broken the syntax by modifying 1 "{}"s. If you have, don't worry: just edit the page again to fix it. If I misunderstood what happened, or if you have any questions, you can leave a message on my operator's talk page.

List of unpaired brackets remaining on the page:

• Radeon 9700 and HyperZ III |publisher=[[Tom's Hardware]] |date=2002-07-18 |accessdate=2014-07-09}}</ref> was used in [[Radeon R300]]-based cards and '''HyperZ HD''' arrived with the [[Radeon R420]]-

It's OK to remove this message. Also, to stop receiving these messages, follow these opt-out instructions. Thanks, BracketBot (talk) 19:46, 9 July 2014 (UTC)[reply]

Hello, I'm BracketBot. I have automatically detected that your edit to OpenAL may have broken the syntax by modifying 1 "()"s. If you have, don't worry: just edit the page again to fix it. If I misunderstood what happened, or if you have any questions, you can leave a message on my operator's talk page.

List of unpaired brackets remaining on the page:

• as [[Environmental Audio Extensions|EAX]] and [[A3D]]). OpenAL can add realism to a game by simulating [[Acoustic attenuation|attenuation]] (degradation
• url=http://aros-exec.org/modules/newbb/viewtopic.php?post_id=33758 |title=OpenAL/alut/ogg/vorbis [Forum - Development (General) |publisher=AROS-Exec |date= |accessdate=2013-06-16}}</ref>

It's OK to remove this message. Also, to stop receiving these messages, follow these opt-out instructions. Thanks, BracketBot (talk) 14:45, 10 July 2014 (UTC)[reply]

Hello, I'm BracketBot. I have automatically detected that your edit to Pipelight may have broken the syntax by modifying 2 "{}"s. If you have, don't worry: just edit the page again to fix it. If I misunderstood what happened, or if you have any questions, you can leave a message on my operator's talk page.

List of unpaired brackets remaining on the page:

• {{software

It's OK to remove this message. Also, to stop receiving these messages, follow these opt-out instructions. Thanks, BracketBot (talk) 19:51, 13 July 2014 (UTC)[reply]

Hi. Thank you for your recent edits. Wikipedia appreciates your help. We noticed though that you've added some links pointing to disambiguation pages. Such links are almost always unintended, since a disambiguation page is merely a list of "Did you mean..." article titles. Read the FAQ • Join us at the DPL WikiProject.

Linux kernel

added a link pointing to Andrew Morton

Multi-monitor

added a link pointing to Matrix

It's OK to remove this message. Also, to stop receiving these messages, follow these opt-out instructions. Thanks, DPL bot (talk) 08:57, 4 July 2014 (UTC)[reply]