As a suggestion, could we stick to either first or second p…

replied to some time ago:

As a suggestion, could we stick to either first or second person for those sections and links. ie: either "to me" and "for me" or "to you" and "for you". One of each just adds cognitive load.

500 chars / 20 lines max · use #hashtags, @mentions and more

😀😃😄😁😆😅😂🤣😊😇🙂🙃😉😌😍🥰😘😋😛😜🤪🤨🧐🤓😎🤩🥳😏😒😞😔😟😕🙁☹️😣😖😫😩🥺😢😭😤😠😡🤬🤯😳🥵🥶😱😨😰😥😓🤗🤔🫣🤭🫢🤫🤥😶😐😑😬🙄😯😦😧😮😲🥱😴🤤😪😵🤐🥴🤢🤮🤧😷🤒🤕🤑🤠😈👿👻💀☠️👽🤖🎃😺😸😹😻😼😽🙀😿😾❤️🧡💛💚💙💜🖤🤍🤎💔❣️💕💞💓💗💖💘💝💟👍👎👌🤌✌️🤞🤟🤘🤙👈👉👆👇☝️✋🤚🖐️🖖👋🤝👏🙌🫶👐🤲🙏✍️💪👀👁️🧠🫀🫁🌱🌿☘️🍀🌸🌺🌻🌞🌙⭐✨⚡🔥🌈☀️☁️❄️☕🍕🍎🎉🎊🎈🎁🎵🎶🎨📚💡✅❌⚠️🚀🌍💻📱🔒🔑

example.com or https://example.com
Regular links: [title](example.com) or [title](https://example.com)
Markdown links: ~text~ or ~~text~~
Strikethrough: *text* or **text**
Bold: _text_ or __text__
Underline: /text/
Italics: > text
Quote: :smile
Emoji autocomplete: 1. first 2. second 3. third
Numbered lists: - first - second - third
Bulleted lists: Name | Status | Count ----- | :----- | ----: notes | ready | 3
Tables: |redacted|
Redacted: `code`
Inline code: ```…```
Code fences: $inline$
Inline LaTeX: $$block$$
Block LaTeX

Which one? #poll First option Second option
PollsUse 2–8 unique options.: Which one? #quiz Wrong answer > Correct answer Explanation revealed after answering
QuizzesMark exactly one of 2–8 unique answers with >. Text after a blank line is revealed after answering.: Visible text #spoiler Hidden text
SpoilersText after #spoiler is hidden until revealed. Aliases: #tldr, #sensitive, #contentwarning, #cw, and #triggerwarning.: Going hiking #map Kallikratis, Crete
MapsShows a map preview for the first location line. Alias: #location.: #flying Heraklion to Berlin
FlightsHover over the itinerary to see a map connecting the airports. The next three words form the itinerary: airport, to (or → or ->), airport. Use single-word airport names or IATA/ICAO codes.: Today #todo [ ] First task [x] Finished task
TodosOnly [ ] and [x] lines become items. Click your items to toggle them.: Run this #exec ```js console.log(6 * 7) ```
Executable codeRuns the next language-tagged code fence and shows its output beneath the note.: Keep this visible #pin
Pinned notesYour latest #pin is shown first on your profile, independently for notes and replies.: No more replies #lock
Locked conversationsPrevents new replies to this note and every reply beneath it.: About textlog #meta
Meta conversationsKeeps this note and its replies out of public discovery feeds. Aliases: #tlog and #textlog.: Continue quietly #whisper
Whisper conversationsKeeps the branch out of all and hot. Participants, mentions, and tag followers can receive it in my feed. It remains public elsewhere.: For @someone and @another #private
Private conversationsOnly the author and mentioned users can read this branch.: Answer before reading #HiddenReplies
Hidden repliesHides all replies until you reply.

moreless

replied to:

it was semi-intentional, here are the complete sentences you can imagine: “here are posts for you” (site talking) “these posts are addressed to me” (me talking)

continued:

we can also call them “following” and “inbox”

replied to:

Sure, but why is one statement the site talking and the other one me talking? It's just arbitrary and adds a moment of confusion. Maybe I'll run a poll to see if it's just me.

replied to:

Wouldn’t it be more confusing if there were two tabs with repeating pronouns? Idk I’m not settled on this. I just picked whatever felt better. They’re more visually different.

replied to:

Repeating pronouns would not be confusing for me. It would serve to indicate that it's the prepositions which are the important part (which they are). Anyway the poll is now live at so we can see what the majority think. Side note: is there a better way to refer to one post in another like this than putting the whole URL in there?

replied to:

Fantastic! About the post linking, I’ve thought about it and can’t come up with a good solution. For now it’s getting shrinked visually to /post/123 because it’s the app domain. Any suggestions here?

replied to:

I can't really think of anything better off-hand. You could overload the # some more and just follow it with the post number but then there would be chaos if anyone wanted a fully numerical hashtag which is going to happen at some point (new year, for instance). I like that it shortens it in the rendering as it stands - that's good enough for me. :)

replied to:

Let’s use ~~tilde~~ ampersand, check .

replied to:

That works nicely. Although again you will get unintentional usage because ~ followed by a number is often used to mean approximately that number. eg: "we're expecting ~100 people". You are also using it for strikethrough formatting. Looking at my keyboard the least ambiguous/overused symbol is probably the & - but I'm not sure if that's better overall.

replied to:

ugh yeah maybe not tilde. I’ll change it to &

continued:

done

replied to:

I think the ampersand is ok. It's doesn't much historical use for these things and being feels more like an append behavior than movement to or continuation of a conversation. >_2596, branded but looks and feels awkward >2596 or >>2596, I like the directionality and punch.

replied to:

The > is used for quoted text and also you need to say >10 sometimes. Ampersand is ok.

replied to:

I forgot about the canonical > blockquote. Good call.

join the communityorbrowse more notes

share with friends