The post before you leave the room

The instinct arrives fast: a speaker says something sharp, a slide lands well, and the phone is out before the applause finishes. Posting your own take on a session, on your own account, while you're still in the room, is now just a normal part of attending a conference — and it's also the one piece of conference etiquette nobody hands you a rule for. The organizer's own camera has a release form behind it somewhere. Your own post doesn't, and the judgment calls it needs are entirely yours to make, in the thirty seconds between a good line and the next agenda item.

Your reaction is yours. A quote belongs to whoever said it

“This session changed how I think about X” is your own observation and needs nobody's permission. Pulling a specific line from a specific speaker and posting it as a quote is a different act, and it carries an obligation back to them: get the wording close to right, attribute it to the person who said it, and keep the surrounding context intact rather than trimming a careful caveat off the end because the shorter version reads better. The same fairness a trade reporter owes a source applies here even though you're not press — you're just the one with a phone already in hand.

What a regulator says in a session isn't yours to amplify

A regulator speaking at a conference is often working carefully within what they're allowed to say publicly, and an offhand aside caught on camera and posted out of context can travel further and read very differently than it did live in the room. The hedge words in a regulator's prepared remarks are there on purpose; an unscripted comment during Q&A deserves at least as much caution before it becomes a quoted post with your name attached to posting it. When in doubt, this is a case for describing the substance of what was discussed rather than quoting the specific phrasing.

Checking before you post, not after

A slide with unreleased data, a product still under regulatory review, a partner's name mentioned in passing — these show up in sessions more often than most posting instincts account for, and a screenshot posts just as easily as a paraphrase. The honest check is simple: would this still be fine to have posted if the speaker or their employer saw it an hour later? If the answer isn't an easy yes, it's worth a second look before it goes up, not a deletion request after. Most employers in regulated industries already have an external-communications or social-media policy that covers exactly this; a conference is the situation it was written for, not an exception to it.

What it's actually good for

None of this is an argument against posting at all — done well, it's one of the more useful habits a conference produces. A short, honest reaction to a session, posted the same day, reaches colleagues who couldn't make the trip and starts conversations the hallway track itself doesn't reach. The posts worth writing are usually the simplest ones: what you learned, in your own words, with your own name on it — not a race to be first with someone else's.