The Peptide CommonsEst. May 2024
Independent. We sell nothing and are affiliated with no manufacturer or pharmacy. Every moderation action is logged in public
Data & Tools · Datasets · continued

Coming back to: A community side-effect dataset, with its response rate and biases posts 91–102

This is a continuation of a long topic, addressed by post number rather than by page. Start at post 1 · go to the accepted answer.

RV
r.villalobosTL2 Moderator5 Jul 2026#91

Community-collected datasets: some members have compiled datasets from their own experience and shared them. They are self-reported, unblinded, and therefore limited as evidence. But they show real patterns that people experience.

20 likes 23d
HF
h.ferrariTL2 Moderator7 Jul 2026#92

I disagree with the reply above, and I think the disagreement is substantive rather than terminological.

The distinction being drawn does not survive when you look at the published data for this specific question. I would be glad to be shown wrong on this, because the version I am arguing against is more convenient.

8 likes 21d
RF
r.friskTL2 Moderator9 Jul 2026#93

Worth separating two things that post #89 runs together.

Reproducibility: if sharing data, include enough context (compound, dose, timeframe, method) that someone reading it understands what it represents.

2 likes 19d
LA
l.aguirreTL2 Moderator11 Jul 2026#94
m.mwangi, post #29: Using data in discussions: datasets are useful as reference points when someone claims something unusual. "I have not seen that reported in the data" is different from "that is impossible", but data gives you something to say. Go to post

Privacy: if contributing data, only share data you are comfortable making permanent and public. Once posted, data is persistent.

0 likes in reply to #29 17d
FF
f.fenwickTL3Regular13 Jul 2026#95

Combining data from different sources: datasets from this site are not directly comparable to published trials because the populations are different. They are worth reading separately, not merged together.

27 likes 15d
AP
ar.petrovTL2 Moderator15 Jul 2026#96

Picking up post #93: that is the part I would want checked first.

Bias toward positive outcomes: datasets collected by members are biased toward people who found the compounds useful. People who did not respond do not return. People who had bad outcomes might have left the community.

13 likes 13d
K
KForsbergTL2Member17 Jul 2026#97
n.bridgewater, post #62: Combining data from different sources: datasets from this site are not directly comparable to published trials because the populations are different. They are worth reading separately, not merged together. Go to post

Temporal bias: older data in a dataset might reflect conditions (supplier, formulation, context) that have changed. Newer data is more current.

4 likes in reply to #62 11d
SH
s.hartmannTL2 Moderator19 Jul 2026 · edited#98
sleep_log, post #41: Thank you for the correction. I have edited my earlier post with a note rather than silently, so the thread still makes sense to read. The error was mine and it was the kind that comes from remembering a figure instead of looking it up. Go to post

Using data in discussions: datasets are useful as reference points when someone claims something unusual. "I have not seen that reported in the data" is different from "that is impossible", but data gives you something to say.

0 likes in reply to #41 9d
DI
diluent_indexTL1Member21 Jul 2026#99
h.frisk, post #19: I read post #17 twice before replying, because I had assumed the opposite. Combining data from different sources: datasets from this site are not directly comparable to published trials because the populations are different. They are worth reading separately, not merged together. Go to post

I read post #97 twice before replying, because I had assumed the opposite.

Limitations of datasets: all community-collected data has limitations. The population is self-selected (people in this community are not representative of all people using these compounds). Reporting bias is real (remarkable outcomes get reported; mundane outcomes do not).

9 likes in reply to #19 7d
ON
o.nybergTL2 Moderator23 Jul 2026#100

This follows post #97 rather than contradicting it.

Collection methods: ask how the data were collected. Longitudinal tracking over months is stronger than retrospective recall. Prospective measurement (done while experiencing something) is stronger than memory afterward.

2 likes 5d
MM
maintenance_modeTL3Regular24 Jul 2026#101

Bias toward positive outcomes: datasets collected by members are biased toward people who found the compounds useful. People who did not respond do not return. People who had bad outcomes might have left the community.

0 likes 3d
AP
au.pereiraTL2 Moderator26 Jul 2026#102

post #101 is right about the mechanism and I think understates the practical bit.

I disagree with the reply above, and I think the disagreement is substantive rather than terminological.

The distinction being drawn does not survive when you look at the published data for this specific question. I would be glad to be shown wrong on this, because the version I am arguing against is more convenient.

23 likes 2d

Suggested topics

TopicParticipantsRepliesViewsActivity
About the Datasets category
Community-collected datasets, their collection methods, and their limitations. This post is a community wiki: any member at trust level 3 or above can edit it, and every edit is recorded with its author and a…
BNOFSVPSAA+6 11 42k 12mo
Whether an aggregate is worth publishing at all: a disputed topic — does this still hold?
Whether an aggregate is worth publishing at all: a disputed topic — does this still hold? I have a specific reason for asking rather than idle curiosity, and the context is below. I would like to understand…
BDHFBWIBOF+14 18 3.4k 2mo
Cleaning a self-reported dataset and what you throw away — what changed since
Posting this under the heading it deserves: Cleaning a self-reported dataset and what you throw away — what changed since Everything below is what sits behind that. Posting the method first, because I know…
HMSCPW 2 2k 1h
Whether an aggregate is worth publishing at all: a disputed topic
On the subject in the title: Whether an aggregate is worth publishing at all: a disputed topic Working notes rather than a conclusion. I would like to understand what this number means before I repeat it…
PEGLIGHNMD+20 24 18k 13mo
Contributing data without breaching anyone's privacy — what changed since
On the subject in the title: Contributing data without breaching anyone's privacy — what changed since Working notes rather than a conclusion. A documentation question rather than an analytical one. I have a…
RIMSBJ 2 58k 17mo

Related topics — sharing the tags observational data, site feedback, data table

TopicParticipantsRepliesViewsActivity
Impurity thresholds: where the common numbers come from
Impurity thresholds: where the common numbers come from — setting out what I have, and where I think it stops being reliable. A documentation question rather than an analytical one. I have a certificate in…
MRDNLAPOBP+11 15 825 2d
Area percent versus weight percent: the confusion that causes most arguments
Posting this under the heading it deserves: Area percent versus weight percent: the confusion that causes most arguments Everything below is what sits behind that. Posting the method first, because I know…
ADSVCDFNAD+10 14 2.1k 2mo
Tag proliferation and whether we should prune
On the subject in the title: Tag proliferation and whether we should prune Working notes rather than a conclusion. Process question about how this site works. I have read the guidelines and the trust-level…
ALADAW 2 11k 11mo
[2026 update] Why 99.2% and 97.8% on the same lot can both be correct
Why 99.2% and 97.8% on the same lot can both be correct — that is the question, and I have not found it answered plainly anywhere I have looked. I would like to understand what this number means before I…
BBWSZDSTD+1 5 719 2d
A friction point in the promotion workflow
A friction point in the promotion workflow — setting out what I have, and where I think it stops being reliable. Nominating something for promotion into the documentation commons. The topic in question keeps…
FPWPSAFNCA+4 8 491 11mo