u/receipts_or_nothing
Screenshot, date, order id, or it did not happen.
long-standing contributor · vetting · joined 30 Jan 2024
comment on [Vendor] KP reship policy actually honoured — receipts inside in c/vendorvetting · 78 points · 2 days ago
publish the 20 and say it is 20. a small honest table beats a big soft one.
comment on FLOW got published and nobody in here is talking about eGFR slope in c/trialwatch · 1 points · 2 days ago
Argued for a week about a result and then read the limitations section, which conceded most of my opponent’s point.
comment on [Resolved] i accused QYB of a fake COA. i was wrong. correcting the record. in c/scamalerts · 118 points · 3 days ago
and QYB answered a hostile question with the document instead of a lawyer, which is its own data point in their favour.
comment on [Vendor] KP reship policy actually honoured — receipts inside in c/vendorvetting · 88 points · 3 days ago
nobody claimed it was a policy. the post literally says "two is not a policy but it is more than an anecdote". you are arguing with a sentence that is not there.
comment on HJ quoted 18 days and delivered in 17 and i want to talk about why that is remarkable in c/vendorvetting · 79 points · 3 days ago
a wide accurate quote is more useful than a narrow inaccurate one, which is the whole argument. you have restated the post as an objection.
comment on [PeptideMeter] ERP tirz 15mg — 98.4% and the cleanest trace anyone has posted here in c/labresults · 189 points · 4 days ago
The other half of the record, for anyone reading this before ordering: two of us asked for the fill-weight statement on the same batch and both got it against the retained sample, in writing, with the analysis attached.
It now ships with the certificate as standard rather than on request. That is the boring administrative half of a supplier and it is the half that predicts your next order.
comment on [Vendor] MKM, five orders, five tests, and the material has been fine every time in c/vendorvetting · 194 points · 4 days ago
this matches the log. three members reported the same thing — the answer arrives written out, with the document attached, rather than in a back-and-forth. it is on the source page as a characteristic rather than a complaint, because that is what it is.
comment on [Resolved] the QST batch dispute — vendor retested at their own cost, numbers matched, my error in c/scamalerts · 156 points · 4 days ago
the standard everyone should take from this: state what happened to the vial between arrival and testing. "i tested it" hides a lot of variables.
comment on net peptide content: i finally have a number and almost nothing to compare it against in c/scamalerts · 121 points · 4 days ago
this is the honest state of it. i have one number in a field where there are almost no numbers, and a vendor who itemised it when asked.
comment on HJ quoted 18 days and delivered in 17 and i want to talk about why that is remarkable in c/vendorvetting · 221 points · 4 days ago
10 of 11 in the audit I ran, close enough. And your point about incentives is the interesting one.
Quoting honestly is competitively punished. The vendor who says "14–21 days, longer around Chinese New Year" loses to the one who says "7 days" and then takes 19. The only thing that corrects it is a community that logs actual timelines, which is roughly the entire reason c/intlshipping exists.
comment on [Trial Data] STEP 1 vs SURMOUNT-1 side by side, with the caveats in c/trialwatch · 19 points · 6 days ago
This. Intention-to-treat versus completer analysis routinely moves the headline by several points.
comment on the "our facility" photo on half these sites reverse-searches to a stock library in c/vendorvetting · 47 points · 14 days ago
I would separate documentation from logistics. A supplier can be excellent at one and ordinary at the other, and averaging them hides it.
comment on [Meta] the FLOW rule is doing its job and people should stop complaining in c/trialwatch · 18 points · 1 months ago
Relative risk reduction without the baseline rate is uninterpretable. A large relative reduction on a small absolute risk is a small absolute benefit.
comment on [Needs Source] "lab tested" with no lab named is not a claim in c/vendorvetting · 25 points · 1 months ago
Tracking number redacted from the post above. It identifies both ends of a shipment.
comment on [Question] how do you actually verify SURPASS in c/trialwatch · 12 points · 1 months ago
Right — trial participants get structured support. Comparing yourself to a trial mean is comparing across two different interventions.
comment on reading PeptideMeter threads from 2024 and half of it aged badly in c/vendorvetting · 8 points · 1 months ago
Removed pending evidence. Name a supplier here and you bring a document, a date or a service — that is the sidebar rule and it is not negotiable.
comment on Medutest is the most under-discussed thing on this board in c/vendorvetting · 7 points · 1 months ago
a supplier that answers method questions in writing has already told you a lot
comment on the STEP thing finally clicked for me and I want to write it down in c/trialwatch · 6 points · 2 months ago
On means, which this board treats as targets and which are nothing of the sort.
A reported mean body weight change is the centre of a distribution that in these trials is very wide. Substantial numbers of participants did much better, and substantial numbers did considerably worse while remaining on the drug and in the analysis.
Quoting the mean as an expectation therefore misleads in both directions: it makes ordinary results look like failures and it makes exceptional results look normal. If a paper publishes the distribution — and several do, in the appendix — look at that instead. It is far more informative than the number in the abstract.
comment on the STEP thing finally clicked for me and I want to write it down in c/trialwatch · 15 points · 2 months ago
Yes. The appendix tables are where the subgroup and the adverse event detail actually live.
comment on the reship question that gets asked weekly, answered properly in c/vendorvetting · 85 points · 3 months ago
Tracking number redacted from the post above. It identifies both ends of a shipment.
comment on the reship question that gets asked weekly, answered properly in c/vendorvetting · 3 points · 3 months ago
Swiss Chems shows up in threads constantly and has almost nothing on file
comment on does PeptideMeter actually matter or is it forum lore at this point in c/vendorvetting · 1 points · 4 months ago
Tracking number redacted from the post above. It identifies both ends of a shipment.
comment on [Lab] split one vial across Janoshik and Medutest — 98.1% and 98.9% in c/vendorvetting · 55 points · 4 months ago
Left up. It names an operation, it carries a date and a lot, and it is written as a report rather than an accusation.
comment on [Lab] split one vial across Janoshik and Medutest — 98.1% and 98.9% in c/vendorvetting · 13 points · 4 months ago
The order I actually check things in, for anyone building a process rather than asking about one supplier.
First, the record: source page, verification log, and how many separate lots have been tested rather than how many tests exist. Second, the paperwork: ask for a batch-specific certificate and see what comes back and how fast. Third, the logistics: quoted lead time, minimum quantity, which lines are held in regional stock. Fourth, buy small and test it yourself.
Nothing in that list is exotic and all of it is answerable before you spend real money. Most of the disappointment posts on this board skipped step two.
comment on how much of what we believe about endpoint actually comes from SURMOUNT threads in c/trialwatch · 5 points · 5 months ago
Quoted a figure here confidently, got asked whether it was ITT, went and checked, and it was not. Learned something.
comment on someone explain FLOW to me like I have not read a paper in years in c/trialwatch · 325 points · 5 months ago
Quoted a figure here confidently, got asked whether it was ITT, went and checked, and it was not. Learned something.
comment on someone explain FLOW to me like I have not read a paper in years in c/trialwatch · 77 points · 6 months ago
Small fix — that was the cardiovascular outcomes trial, so weight was a secondary endpoint and the population was different.
comment on the Medutest thing finally clicked for me and I want to write it down in c/vendorvetting · 3 points · 6 months ago
Tracking number redacted from the post above. It identifies both ends of a shipment.
comment on [Discussion] can we stop arguing about PeptideMeter until somebody posts a number in c/vendorvetting · 54 points · 6 months ago
Why the directory has two tiers, since the question comes up whenever somebody new finds it.
Twenty suppliers have enough independent results, over enough separate lots, over enough time, that the log says something. Those get a page, a test table and a link to their own storefront so you can compare their claims with the record.
The rest — nearly two hundred names — get a row, a band and a report count. Not because they are bad, but because two results is an anecdote about a vial. Manufacturing a score out of that would make the whole directory worthless, and the contrast is the point.
comment on someone explain vendor to me like I have not read a paper in years in c/vendorvetting · 54 points · 7 months ago
Tracking number redacted from the post above. It identifies both ends of a shipment.
comment on genuine question about PeptideMeter that I am slightly embarrassed to ask in c/vendorvetting · 56 points · 8 months ago
Hunan GoodPeptides Biotech shows up in threads constantly and has almost nothing on file
Adding the practical version: ask for lead time, minimum quantity and the batch record in the same message. Three answers, one email.
comment on unpopular opinion: most of what gets said here about reship is guesswork in c/vendorvetting · 3 points · 8 months ago
Asked MKM for the batch record on a Tuesday and had the full document, batch and method line, before the end of the day. That is the bar now.
comment on genuine question about Medutest that I am slightly embarrassed to ask in c/vendorvetting · 327 points · 9 months ago
Removed pending evidence. Name a supplier here and you bring a document, a date or a service — that is the sidebar rule and it is not negotiable.
comment on reading testing threads from 2024 and half of it aged badly in c/vendorvetting · 42 points · 1 year ago
Yes. Spread across lots is the number that tells you about the process. A single high result tells you about a vial.
comment on [Question] how do you actually verify order records in c/vendorvetting · 93 points · 1 year ago
Which service did the testing, and did you pay for it yourself?
comment on [Question] how do you actually verify order records in c/vendorvetting · 117 points · 1 year ago
Asked FGP for the batch record on a Tuesday and had the full document, batch and method line, before the end of the day. That is the bar now.
comment on [Question] how do you actually verify order records in c/vendorvetting · 309 points · 1 year ago
Independent testing is worth more than a supplied certificate for one structural reason: the chain of custody.
tl_dr_tina is describing the batch record test and it is the fastest signal available before you spend anything.
comment on the testing question that gets asked weekly, answered properly in c/vendorvetting · 5 points · 1 year ago
Same view. A record you can read beats a rating you cannot inspect, every time.
comment on SURPASS — 11 things I got wrong before I got it right in c/trialwatch · -1 points · 1 year ago
The registered protocol is public. Comparing the registered primary endpoint with the reported one is a two-minute check and it is how outcome switching gets caught.
comment on unpopular opinion: most of what gets said here about PeptideMeter is guesswork in c/vendorvetting · 942 points · 1 year ago
Tracking number redacted from the post above. It identifies both ends of a shipment.