Talk:LXQt

Latest comment: 1 year ago by Ahunt in topic Longterm vandalism

lxqt.org edit

  • webpage is not working anymore on 2017-11-21. -- user:tothaa — Preceding unsigned comment added by 212.96.59.240 (talk) 18:12, 21 November 2017 (UTC)Reply
  • I modified with adding www. prefix, so now it is working for me. -- user:tothaa
Corrected to https://lxqt.org/ - Ahunt (talk) 03:02, 22 November 2017 (UTC)Reply

Longterm vandalism edit

User:Ahunt stop it! 89.12.182.12 (talk) 00:25, 15 December 2022 (UTC)Reply

You are attempting to introduce nonconstructive table formatting changes and I have reverted them as per WP:BRD. This is not vandalism. You need to read WP:CIVIL and WP:AGF and apologize. You also need to stop edit warring to get your own way and make a case here for the changes, if you think they are justified, and try to gain a consensus. - Ahunt (talk) 00:30, 15 December 2022 (UTC)Reply
Ahunt, it is you who does that. |+ is the standard syntax. You come up with unconstructive colspan-usage. Just stop it. You have no consensus in the Wikipedia community to diverge from the standard syntax. You are failing WP:CIVIL. Why are you messing around here? 89.12.182.12 (talk) 00:36, 15 December 2022 (UTC)Reply
Sorry but you are not correct. That edit you cited in your edit summary https://en.wikipedia.org/w/index.php?title=LXQt&diff=971478578&oldid=971472307 was me reverting a bunch of unconstructive IP edits in 2020 and restoring the page to the way it was before. It is not my table formatting. The table's introduction dates to an IP addition in 2017: https://en.wikipedia.org/w/index.php?title=LXQt&oldid=806085024 and the current table format was introduced by User:Renamed user 9872075196 https://en.wikipedia.org/w/index.php?title=LXQt&oldid=906770085 in 2019. If you had checked the edit history properly before making accusations you would know that. Now, given those facts, if you have some case to make, other than making wild and inaccurate accusations, then please do make it. - Ahunt (talk) 01:01, 15 December 2022 (UTC)Reply