lflage/wiki-talks huggingface dataset:
Talk:SyQuest Technology

message: This product line section was wrong in at least one place. I didn't know the details of much of the rest of this so I didn't want to tamper with it, nor did I have a websource other than this bs being mirrored across 50 other websites (such as answers.com, allexperts.com, reference.com, etc.), but there was some incorrect information and I can confirm that SyQuest made two different SQ200 models, one a cartridge and one an external drive housing the SQ5200C, which is also backwards compatible to the SQ200 44mb cartridge. This unit SyQuest made had a 200mb native capacity drives in desktop SCSI cases with the model number SQ200 on the bottom tag, on a second dealer tag, they said "200 MB C" on the front of the drive itself, and the bare drive inside is a SQ5200C. I know this because I have nine identical units. They are not 10mb nor MFM. SQ200 External drives have a 200mb capacity, hence the name!
I noted this weeks before, no one fixed it, so I researched and made the needed changes myself.— Preceding unsigned comment added by 208.127.100.174 (talk) 22:15, 15 August 2009 (UTC)
thread_title: Incorrect Model Information Here

message: Anyone got a shot of the disk with something more international to indicate scale? A metric ruler perhaps? I assume that's a US coin of some sort, but not being a USian I can only make a rough estimate of how big the coin is - not very helpful.  —Preceding unsigned comment added by Worldwidewookie (talk • contribs) 13:19, 20 October 2009 (UTC)
thread_title: Scale indicator not very useful

message: This is not a candidate for speedy deletion. The criteria nominator suggested reads:
:G11. Unambiguous advertising or promotion.
:Pages that are exclusively promotional, and would need to be fundamentally rewritten to become encyclopedic. Note: An article about a company or a product which describes its subject from a neutral point of view does not qualify for this criterion. "Promotion" does not necessarily mean commercial promotion: anything can be promoted, including a person, a non-commercial organisation, a point of view, etc.
This is a company that was a significant player in the early years of personal computers and so is of historical significance. As the article says, it is no longer in business so it is hard to see what is being promoted. Furthermore the last paragraph is quite critical of the company: "A significant reason for the losses was due to quality issues with a series of products, including the SparQ Drive and SyJet drives, that caused a large number of the drives to malfunction within just a few months of initial operation. ..." This is consistent with a neutral point of view article, but not with advertising. While I started the article, more than 35 editors have contributed to it, again, not consistent with a promotional piece. If you still think deletion is appropriate, AfD is the appropriate forum.--agr (talk) 00:34, 24 August 2012 (UTC)
thread_title:  Not speedy
Talk:Stateless protocol

message: * I suggest to change "WWW server" to "HTTP server". This sharpens the comparison to the FTP server as both acryonyms are protocols. Plus the term "WWW server" is a fuzzier and possibly dated term. VdHamer (talk) 21:31, 1 November 2008 (UTC)
thread_title:  Opening heading 

message: can you give us a description of the motivation for your recent edits. Things are reworded but it is not clear to me this an improvement or just changes. There are no edit summaries to help me. ~Kvng (talk) 15:38, 21 May 2021 (UTC)
thread_title:  Recent changes by [[Maggyero]]
Talk:SP/k

message: The SP/k compiler we used in high school (1978ish) had an incredibly annoying "feature" in that it would try to fix compile errors and carry on, leading to cascading errors caused by the fixes.  A simple typo in a variable name could cause dozens of cascaded errors. -- Paul T  —Preceding unsigned comment added by 165.170.128.66 (talk) 18:56, 13 November 2007 (UTC)
replies: text: I think you're remembering the Cornell PL/C compiler.  RossPatterson (talk) 13:25, 8 January 2010 (UTC)
Talk:Slot A

message: The picture shown as example in this picture shows a motherboard with dead capacitors. I don't find that a good idea to be posted. Better use a picture without broken components...
89.13.104.71 (talk) 14:39, 30 April 2009 (UTC)
replies: text: I think we should keep the current picture for now, until someone else gets a new picture. I do agree that it isn't a good idea to have a picture with broken components being used for this purpose. Racecar56 (talk) 23:31, 23 November 2009 (UTC)
thread_title:  Bad example picture? 

message: — Preceding unsigned comment added by 108.4.232.242 (talk) 23:11, 7 September 2019 (UTC)
replies: text: Link updated
Jsn.sherman (talk) 12:57, 17 October 2022 (UTC)
thread_title:  Reference is a dead link.
Talk:Slot 2

message: This article states that Socket 370 replaced Slot 2. Socket 370 is a desktop socket, so didn't Socket 603/604 replace Slot 2? Racecar56 (talk) 00:09, 24 November 2009 (UTC)

message: This article is, as far as I can tell, full of inaccuracies, and as it's so short, it might warrant a rewrite...
* AFAIK, all Pentium II Xeons and Pentium III Xeons are Slot 2
* Deschutes is solely a Pentium II, not a Pentium III, even if they are based on the P6 microarchitecture
* Intel sold CPUs with full-speed on-die L2 on Slot 1 - I believe the reason for the additional contacts in Slot 2 was to enable 4-way SMP, not the cache
* I can't quickly find evidence of Tualatin Xeons ever existing
* Using a reference to spell out that you meant kibibyes when you said kilobytes is, uh.
Honestly I'd rewrite it myself right now, but haven't dug deep enough into proper first-party sources yet. Bhtooefr (talk) 14:45, 28 December 2021 (UTC)
thread_title:  Rewrite may be needed
Talk:SISAL

message: References the page VAL, intending to describe http://hopl.murdoch.edu.au/showlanguage.prx?exp=876 (Value-oriented Algorithmic Language), but instead this page is about some kind of metro rail technology.
Should also probably reference http://sisal.sourceforge.net/
72.134.27.172 04:11, 28 May 2007 (UTC)
thread_title:  VAL link a bad idea
Talk:Anthony Nicholls (actor)

message: I've removed the tag since I've added / updated the biographical citations. To all editors: Please remember that all claims need WP:RS citing, and that biographical claims in particular need concrete, quality cites. The fact that neither the British Film Institute nor The Encyclopedia of British Film give any name for Nicholls other than "Anthony Nicholls" suggests that the removed name may not be accurate.
Please note that Wikipedia disallows the wikia IMDb, in which anyone can write anything, as a reference citation. --Tenebrae (talk) 23:38, 28 November 2017 (UTC)
thread_title: Bio cite tag
Talk:Security Account Manager

message: The article states that Windows can be configured to disable LM hashes, but there is no mention of how this would be done. Therefore, a link to Microsoft's Knowledge Base where this is explained in detail  could prove useful.  —Preceding unsigned comment added by 78.34.139.156 (talk) 21:56, 27 June 2009 (UTC)
thread_title:  Disable LM hashes 

message: I came here because I was looking for the registry location of the SAM. Unfortunately it's not mentioned. --193.134.254.25 (talk) 15:04, 22 November 2012 (UTC)
thread_title:  Registry Location 

message: Multiple tools do exist for the purpose of cracking these hashes, perhaps most notably  BackTrack, specifically the Jack the Ripper (I think that's the name) utility. Flashgamer001 (talk) 23:49, 19 December 2012 (UTC)
thread_title:  Related Attacks section 

message: "Only recently, Microsoft released a utility called LockSmith, which is part of MSDart. MSDart is not freely available to end-users, however."
How recently? Can this be dated please? 195.188.200.14 (talk) 09:43, 2 September 2013 (UTC)
thread_title:  "Only recently"
Talk:Recursive data type

message: The theory part of this article is unfortunately rich in technical notation and jargon without
references within Wikipedia or citations of references.  It would be a significant task
to fill in Wikipedia with appropriate information, but it would be very desirable to
refer to external sources.
This subject is outside my real competence, but it looks like John Mitchell's book
"Foundations for Programming Languages" would be a reasonable reference for some
of the concepts and notation including the μ operator.
Hopefully someone with more competence can help fill out this topic to be more
helpful to less knowledgeable readers.
Crisperdue (talk) 19:09, 19 May 2017 (UTC)

message: I propose merging with Inductive type. I've started a discussion on that talk page. siddharthist (talk) 00:20, 18 January 2018 (UTC)
replies: text: There are differences. The article Inductive type correctly emphasizes on structural recursion. While here, we have directed graphs as data, the graph of inductive types' data is restricted to terminating relations, i.e. acyclic and without infinite chains. -- Cobalt pen (talk) 09:45, 19 October 2020 (UTC)

text: The main difference between inductive and recursive data types is the latter admit contravariance in their definition. This is unfortunately not discussed at all. 128.237.82.2 (talk) 00:57, 21 October 2021 (UTC)
thread_title:  Merge
Talk:Longmeadow High School

message: Nice start. Try adding infobox or history. Pictures would be good. Referencing? Victuallers 08:22, 27 April 2007 (UTC)
thread_title: Assess

message: In the last revision I edited, I found duplicate named references, i.e. references sharing the same name, but not having the same content. Please check them, as I am not able to fix them automatically :) 
* "ww" :
** Get The Feeling:  Masacksic 1988, Vol. 32.
** Scholastic Aptitude Test
** MCAS Scores
DumZiBoT (talk) 19:42, 12 August 2008 (UTC)
thread_title:  Bot report : Found duplicate references ! 
Talk:Radio Resource Control

message: What are the UE and eNB? I see no definitions or links in this article. 189.241.59.7 (talk) 22:02, 12 February 2020 (UTC)
replies: text: Another one: 'radio reconfiguration'. Arlo James Barnes 09:04, 16 March 2024 (UTC)
thread_title:  Definitions?
Talk:Partial-response maximum-likelihood

message: Is this pretty much the same as Automatic Gain Control in a TV set? , 2010-01-13 15:14:51‎
: To me it looks more like (expressing it in simple terms) DC blocking - removing the DC component of an AC signal. You really have to read the linked paper to see all that's going on, though.  Jeh (talk) 02:58, 4 February 2012 (UTC)
thread_title:  Questions
Talk:Portable Standard Lisp

message: I'm going to change all "was" to "is" right now. I'm using PSL, both in my personal software development, and for other purposes here and there.  Our department now and then buy updated versions of stand-alone PSL (from ZIB = "Konrad-Zuse-Zentrum für Informationstechnik Berlin").  More importantly: The most common implementation of Reduce is also provided by ZIB and programmed in PSL (even if I believe there is a CSL implementation around, somewhere); and Reduce is not just a veteran among the CASes, but actually is used, and has new packages added now and then.  Of course, Reduce programmers often employ the underlying Standard lisp by means of the RLisp (a.k.a. "symbolic mode") interface; but not entirely so; and anyhow, the developers at ZIB of course do continue to programme in PSL.
As to its ungainlyness, I personally disagree, since I do prefer the Standard Lisp variants; but the main reason I prefer PSL is its comparatively small size and high speed performance.  However, I've mainly compared it with Common lisp, which might be unfair; as a "committe language" Common has both the advantage and disadvantage of having a very large number of additional functionality.  In any case, my personal preferences are not that important (and besides, some of my colleagues who have tested both are of a very different opinion); but I'll anyhow try to modify the criticism from the present absolute statements to expressions of opinions.
Personally, I think that the largest trouble with the whole Standard lisp family is, that there seems to be no free version of it.  Of course, this may be argued both ways: Possibly there are several free Common lisps around, mainly since many more people liked that dialect.JoergenB (talk) 17:27, 21 December 2007 (UTC)
thread_title:  "was"?
Talk:Rampuri

message: Wow this article is ugly.
Maybe some cleanup from an expert? —The preceding unsigned comment was added by Gsusnake (talk • contribs).
:Thank you for your suggestion. When you feel an article needs improvement, please feel free to make those changes.  Wikipedia is a wiki, so anyone can edit almost any article by simply following the Edit this page link at the top. The Wikipedia community encourages you to be bold in updating pages. Don't worry too much about making honest mistakes — they're likely to be found and corrected quickly. If you're not sure how editing works, check out how to edit a page, or use the sandbox to try out your editing skills.  New contributors are always welcome. You don't even need to log in (although there are many reasons why you might want to).   -- I've taken care of some of the more glaring idiocies. Don't have to be an expert, just have to not be a complete retard. Search4Lancer 01:37, 9 May 2007 (UTC)
Talk:Out-of-band

message: This article is a rather short one to begin with; if one were to split it into two separate articles accessible via a disambiguation page, someone is just going to label the articles as "stubs" (unless someone can substantially increase the length of the article(s)) and they'll inevitably get merged back into one.
Does this make sense or am I alone on this??  I'm not sure how to "officially" suggest that the banner at the top of the article page suggessting it be split into two or more articles be removed, but if I'm not the only one who feels this way then I'll look into it.
Do let me know; if nobody posts anything regarding it in the next few days then I'll begin the process of having that banner removed.
Schaea (talk) 10:51, 11 December 2007 (UTC)
thread_title:  Splitting article 

message: That little bit about confusing "out-of-band" with "out-of-bounds" and C functions that return -1 is stupid. Did someone write that just to accumulate more edits or something? I don't know why someone would confuse the two, but even if that's a common misunderstanding, a return value of -1 is not "out of bounds" (which usually refers to array boundaries) so the whole connection is tenuous at best.  —Preceding unsigned comment added by 131.107.0.102 (talk) 17:20, 13 January 2010 (UTC)
thread_title:  Out of bounds? 

message: In the article the following sentence appears without further explanation: "This added layer of security prevents the likelihood of hackers and malware from compromising access to the complete authentication process, however, this method of authenticating a user is known to be vulnerable to man-in-the-middle (MITM) attacks." Any hints as to the vulnerability?  — Preceding unsigned comment added by 24.179.25.119 (talk) 18:09, 18 February 2013 (UTC)
thread_title:  OOB is vulnerable?
Talk:OS/390

message: Not sure "basically" inspires confidence and I'm not sure the statement with it is accurate. Martin Packer 17:02, 3 October 2007 (UTC)
thread_title: [untitled]

message: After a big edit of MVS I concluded that the whole set of articles about IBM mainframe operating systems from System/360 onwards needed to be re-structured to  minimise overlap and to make clearer the evolutionary relationships between these operating systems (notably in memory management, which is historically a major distinguishing feature). There is already some support for this proposal. Please add comments at Talk: MVS. Philcha 23:56, 20 October 2007 (UTC)
thread_title: Restructure of articles about IBM mainframe operating systems

message: As part of the proposed restructure of articles on IBM mainframe operating systems (above), I've rewritten Job Control Language to: cover IBM's DOS/360 and its descendants as well as OS/360 and its descendants; focus more on the facilities and flavour of the 2 JCLs rather than on details of  some statement types and some of their options. Please comment in Talk: Job Control Language. I'd be particulary grateful for more info on DOS/360 and its descendants, especially after 1980 - I only used DOS JCL a handful of times, and only in the late 1970s.
The rewrite does not currently take account of Truthanado's point in Talk: Job Control Language about use of "JCL" by computer suppliers other than IBM, which may entail further restructuring of articles about JCLs. Philcha 00:31, 21 October 2007 (UTC)
thread_title: Rewrite of [[Job Control Language]] in progress

message: The article has a DFP link that redirects to HSM, an unrelated component of DFSMS. Either someone should write a DFSMSdfp article or the link should be changed to text. Shmuel (Seymour J.) Metz Username:Chatul (talk) 19:00, 4 June 2013 (UTC)
thread_title:  There are no DFP or DFSMS articles to link to
Talk:Occurs check

message: I replaced the dangling link "logical variable" by a link into "First-order logic#Terms" in introduction section.
I have suggestions regarding the following points of the article:
* In section "Algorithm", the shown algorithm does not provide much new insight as it just defines "occurscheck(x,t)" by "x occurs in t". I'd suggest to omit the algorithm box. Alternatively, a recursive Prolog (or Ml) definition of the predicate (or boolean function) that test whether x occurs in t could be given.
* The goal of syntactic unification in general should be restated in this article. Thereafter, it'd be easier to explain that e.g. X=f(X) has no solution among finite terms, but has one among infinite terms. I'll try to draw a picture showing the introduction of a cycle in this case, if occurs check is omitted.
:::Meanwhile, I added an example picture; resulting in a poor overall page layout, however. If the picture shall be kept, somebody should improve the page layout. Jochen Burghardt (talk) 23:02, 15 May 2013 (UTC)

message: There is a funny error in the statement on complexity of unification without occur check.  The error has been there in many Prolog manuals for more than 30 years.  The following statement (now at the page) is plainly incorrect.
By not performing the occurs check, the worst case complexity of unifying a term t_1 with term t_2 is reduced from
O(\text{size}(t_1)+\text{size}(t_2))
to
O(\text{min}(\text{size}(t_1),\text{size}(t_2)));
It implies that arbitrarily big terms can be compared in constant time, by unifying  eq(t1,t2) with eq(X,X).
I am going to change it by adding "in many cases", and abandoning the reference to a Prolog manual:
--Wlodr (talk) 20:17, 24 October 2015 (UTC)
thread_title:  complexity without occur check
Talk:ObjVlisp

message: , thanks for undeleting this, but I have to question your decision to tag it with . I don't believe that "Wikipedia's notability guidelines for products and services" are relevant to this article, since as far as I am aware ObjVlisp was never a commercially available product, it was a university research project. As such, "notability guidelines for products and services" are inapplicable. I'd suggest the key notability criteria for academic research are discussion in publications respected in the particular academic discipline (such as journals or conference proceedings), including both papers directly discussing the research, and the number of times those papers are later cited. SJK (talk) 11:08, 15 April 2016 (UTC)
replies: text: I might add that I am inclined to agree with this. If there is a set of notability guidelines for academic research projects and similar articles, it would be a bit more apropos than to judge the article based merely on the criteria used for commercial products. H.dryad (talk) 12:48, 15 April 2016 (UTC)
replies: text: The particular variety of "notability" tag is not that significant; the WP:General notability guideline is the criterion in any case. I have removed the tag as I think the article is now adequately referenced. JohnCD (talk) 11:14, 18 April 2016 (UTC)
thread_title:  Notability tag
Talk:OBJ (programming language)

message: This quotation comes from the cited source:
"The OBJ languages are broad spectrum algebraic programming and specification languages."
Modern functional programming languages are derivation of specification languages.
It is wrong to say that OBJ is a family of programming languages. It is a family of formal specification languages. 
Although they may be used to generate target code, the main goal is to prove correctness.
This article should be extended and make clear the difference with declarative programming languages.  — Preceding unsigned comment added by 189.140.217.137 (talk) 16:05, 6 March 2012 (UTC)
thread_title:  What is OBJ? an specification or programming language?
Talk:MOS Technology 65xx

message: I propose that this short article is merged into the much more complete MOS Technologies 6502 article as a replacement for the one sentence leading its Variations and derivatives section.  Unlike the 6502 page, this hasn't had much added to it over the years and probably only gets traffic as is the lead for the  navbox. KelleyCook (talk) 19:33, 15 August 2023 (UTC)
replies: text: Makes sense to me. Dhrm77 (talk) 11:03, 16 August 2023 (UTC)

text: Good idea. This separate article isn't worth it.--ToaneeM (talk) 15:28, 16 August 2023 (UTC)
thread_title:  Merge Proposal
Talk:Media Gateway Control Protocol (MGCP)

message: This article should discuss the overall architectural concepts of MGCP and Megaco, the two implementations.
Megaco and MGCP articles are now renamed consistently. Wikilinks should just use the common acronyms Megaco (or MEGACO) and MGCP, except for navigation templates of course, which should use the actual full article title. Kbrose (talk) 20:22, 24 February 2009 (UTC)
thread_title: Article title

message: User:Thumperward has been interfering with editing and revising the set of pages and redirects of Media Gateway Control Protocol without explanations by reverting page moves and redirects, and now by speedy deletion attempts. Kbrose (talk) 20:43, 25 February 2009 (UTC)
replies: text: This was to correct the cut-and-paste page move error you made in splitting the page. The current titles are definitely sub-optimal as well, but that can be dealt with later. Chris Cunningham (not at work) - talk 20:54, 25 February 2009 (UTC)
replies: text:  The history has now been moved into the correct branch of the article. Chris Cunningham (not at work) - talk 09:42, 26 February 2009 (UTC)
thread_title: Recent move

message: This is a duplicate article. Google knows all! Family Guy Guy (talk) 04:02, 3 April 2011 (UTC)
thread_title:  Duplicate Article
Talk:Leland Stowe

message: Stumbled across this because he's linked on Chilcotin District as one of the "main" authors of that  region, althogh FWIU it's only Carusoe of Lonesome Lake in which he wrote about the Chilcotin Country; which for other Chilcotin-area authors I'd add :Category:Chilcotin Country but not sure what to do here, as the book isn't even mentioned....Skookum1 08:55, 27 April 2007 (UTC)
replies: text: RE the above and geographic/heritage site articles pending, please see Talk:List_of_World_Heritage_Sites_in_the_Americas#Ralph_Edwards.2C_Lonesome_Lake_.26_Trumpeter_Swans.Skookum1 (talk) 03:07, 29 March 2009 (UTC)
thread_title: his book on Ralph Edwards

message: I have commenced a tidy-up of the Bibliography section:
* Cite templates will be used where possible.
* I prefer capitalization and punctuation to follow the standard cataloguing rules in AACR2 and RDA, rather than "title case".
* Links to potentially unreliable digitised copies may be removed. 
This is a work in progress; feel free to continue. Sunwin1960 (talk) 10:22, 8 January 2023 (UTC)
thread_title:  Bibliography