Comments, reactions on comments and replies

Open the comments from the speech bubble under a shot, from "View all" under the comment preview, or from "Add a comment" in the viewer.

React to a comment

Each comment has a small heart on its right. Tap it to like the comment; tap it again to take the like back. Since build 15 a like is one of the reactions, as on shots: you get one reaction per comment, the heart or any other emoji, and you can react to your own. If yours is another emoji, it shows where the heart was, and a tap there takes it back.

There is never a number. When a comment has reactions, a quiet line shows under it with up to three of the emoji sent: "Liked by Safal", "Liked by Safal and Dana", "Liked by you, Safal and others". You come first, as "you". "Liked by" is only for hearts: once any reaction is another emoji (build 16), the line after the emoji is just who: "You", or "You and Safal". Tap the line to see everyone who reacted and what they sent, and tap a name to open their profile.

Reactions on your comments show in Activity: a heart as "liked your comment", any other emoji drawn before "reacted to your comment". They're never pushed, as likes weren't.

Hold a comment

Hold any comment (or the heart beside it) and it lifts out of the list, the rest goes dark (blurred too on iPhone), and two things appear around it, the same on both phones:

• Above it, the vibe bar: tap an emoji to react, or "+" for any emoji. Your reaction has the safelight ring; tap it again to take it back. The heart is the like.
• Below it, what you can do with it.

What's below:

• Reply, as with the Reply link: "Replying to Safal" above the field, and the keyboard comes up.
• Copy the comment's text.
• Delete, on your own comment or any comment on your shot, with the same check as before.
• Report, on anyone else's comment, on your own shot too. Once the report is sent you can block them as well ("Block Safal too"), with the same check as on a profile. Block isn't in the menu itself, so a stray tap can't end a friendship.

"+" opens every emoji, by group, with the ones you picked lately first (kept on your phone only). It's Unicode's Emoji 14.0 set, so every phone in the group can draw them; skin tones, keycaps and letter symbols are left out. An emoji from "+" takes the "+" place in the bar, with the ring, until you take it back.

Near the bottom of the list, or with the keyboard up, the whole group moves up so it fits; the keyboard goes away and what you were typing stays. Tap outside, press Android's back button, or pick something to close it.

With a screen reader, every comment has the same choices as actions (Reply, Like or Take back your reaction, React, Copy, Delete, Report), so nothing needs a long press; React opens the menu on the emoji. While the menu is open, it's all the screen reader reads.

Reply to a comment

Tap "Reply" under a comment. The field above the keyboard says "Replying to Safal"; the text field stays empty, and the X next to it cancels the reply. Replies sit indented under their comment, in the order they were posted.

Replies go one level deep, like Instagram: replying to a reply puts yours under the same comment.

The person you replied to hears about it under "Vibes and comments" in Settings, Notifications (the same switch, the same quiet hours), gathered over 15 minutes: "Safal replied to your comment." Nobody hears about a reply to themselves. When the comment's author owns the shot, the comment note they already get covers the reply.

Photos and GIFs (build 15)

The photos button left of the field attaches a photo or a GIF from your phone. The system picker opens, and Durpin sees only the one you pick. It starts uploading at once: a small picture with a spinner sits above the field, and Send waits until it's in. The X next to it takes it off. Write a caption with it, or send it on its own. Replies can carry one too.

Your keyboard's GIF button works the same way. In Gboard or the Samsung keyboard on Android 12 or later, a GIF you tap goes on the comment as if you'd picked it (on older Android the keyboard says it can't put it there). On an iPhone, a keyboard GIF is copied: hold the field and tap Paste. Pasting a photo or GIF you copied works on both. The search is the keyboard's own; Durpin only gets the GIF you send.

• A GIF, or an animated WebP, is sent as it is, up to 5 MB.
• A GIF can be at most 1280 pixels on its long edge.
• A still photo (a JPEG, PNG or HEIC, a screenshot or a meme) is made a JPEG, which leaves its location and other details behind.
• Made smaller, a photo is at most 1600 pixels on its long edge.
• Up to 100 photos and GIFs in comments a day each.

Anything bigger says which limit it's over, and nothing is sent.

In the sheet the picture sits under the comment's text, in a rounded tile in its own shape, up to 220 by 260 points (a panorama is cropped to 3 to 1). A GIF moves only while it's on screen and the app is open; scrolled half away it shows still, with a small GIF label. With Reduce Motion on, a GIF waits as a still until you tap it. Tap a photo, or a GIF that's playing, to see it full screen: "GIF from Safal" at the top, the X, a tap anywhere or Android's back closes it. Holding the picture does what holding the comment does.

Under a shot nothing moves: the preview shows the caption, or just "GIF" or "Photo". Activity says "commented with a GIF" or "commented with a photo". Notifications never carry a comment, so they don't change.

Photos and GIFs from your phone go to Durpin's server, like your shots, and to nobody else. Comments are never edited, so a picture can't be swapped after it's sent. Deleting the comment, its shot or your account deletes its files too; a picture picked but never sent is removed by the server within two days.

Phones on build 14 or older show a comment with only a picture as an empty comment with a name and a time; updating shows it.

No GIF search

There's no GIF search in Durpin: GIFs come from your own phone, like photos, or from your keyboard. Durpin uses no GIF service, because one would see what friends search for and every GIF they look at (Bishal, 2026-10-20). A keyboard's GIF search is the keyboard's (Gboard, the Samsung keyboard or GIPHY), not Durpin's.

Deleting

Swipe your own comment to delete it, or hold it and pick Delete. The shot's owner can delete any comment on their shot. Deleting a comment deletes its replies too (the sheet says so before you confirm), and every reaction on them.

Under the shot

The preview under a shot in the feed and in the viewer shows the newest two top level comments; replies stay in the sheet. "View all 5 comments" counts every comment, replies included.

Who sees what

Anyone who can see a comment sees who reacted to it, and with what. A stranger who can't see the shot sees neither the comments nor the reactions. Someone either of you has blocked drops out: their comments, replies and reactions are hidden, and you can't react or reply to theirs.

Phones on build 14 show every reaction as a heart, and their heart is a like, so a tap there still likes and takes back.

A comment's photo or GIF follows the comment: the server hands it only to someone who can see the shot, and never to someone either side has blocked.

Reports

Report a photo or GIF comment the way you report words: hold it and pick Report. The admin's Reports screen (Settings, Reports) shows its still next to the reason, which the admin can open only while the report is open, and has Remove next to Done. Remove asks first, then deletes the comment for everyone, with any replies, and closes every report on it. A report stays until the admin marks it Done; since build 16 the Reports row in Settings shows how many are open.

Since build 16 a report keeps what it was about as it was then: the comment's words, or the shot's note, and their files. So the Reports screen shows what was reported even after the comment is deleted or a shot is turned. A shot report shows the shot's own still too. The copy is kept while the report is open. When it's closed, or the account it came from is deleted, the words go and so do the files, unless something else still uses them. Reports from before build 16 show what's there now.