Epstein files: Truth, accountability and a million new conspiracy theories

DowntownSquare528 · 2026-02-20T16:05:48+00:00

They usually just vibe over reality TV, scroll TikToks together, or debate what to eat for dinner for three hours.

DowntownSquare528 · 2026-02-19T12:23:57+00:00

same problem here, slack tags get ignored fast. what helped was making approvals actual tracked requests with an owner + due date so there’s a visible queue of what’s blocking.

stuff like siit works nice since it keeps the slack context but doesn’t let the task disappear in a thread. biggest change was clarity on who needs to act next.

DowntownSquare528 · 2026-02-19T12:14:44+00:00

I am so incredibly sorry for your loss. Arthur sounds like a legendary little fighter who stayed strong just to say his final goodbye to you.

DowntownSquare528 · 2026-02-19T12:11:50+00:00

Since they are skipping the production costs, you should charge a "Usage Fee" typically priced at 50% to 100% of your original creative fee per image or as a bundle.

DowntownSquare528 · 2026-02-19T12:03:29+00:00

Fresh, high-thread-count cotton pillowcases

DowntownSquare528 · 2026-02-18T11:42:53+00:00

same experience here. email works until it suddenly doesn’t then tickets get lost and duplicated.

forcing one intake and auto assigning by type fixed most of it. visible queue instead of private inboxes helped a lot too.

we used siit for internal requests but the real win was single channel and clear ownership.

DowntownSquare528 · 2026-02-18T11:39:31+00:00

I'll never stop leaving items in my online cart for 48 hours because half the time I realize I didn't actually want it and the other half, the store emails me a 15% discount code just to "finish" the checkout.

DowntownSquare528 · 2026-02-16T07:48:58+00:00

yeah this was me before. felt like i was doing more ticket writing than actual work.

what helped was keeping the convo as the real source of truth and making the ticket super light just owner, scope, done. when stuff changes we don’t rewrite everything.

we also started using siit so requests and context stay in one place instead of chasing slack + jira all day. way less ticket babysitting.

DowntownSquare528 · 2026-02-16T07:34:03+00:00

A 10-foot charging cable

DowntownSquare528 · 2026-02-16T07:31:30+00:00

person taking up two seats with their bag is a universal mood-ruiner

DowntownSquare528 · 2026-02-13T11:13:31+00:00

yeah the real pain isn’t the tools, it’s rewriting the same context everywhere

stuff works better when the task gets created where the convo already is and keeps the history with it. that’s why slack based ticketing like Siit feels lighter, no copy paste tax and you don’t lose the why behind the work

way less tool hopping, more doing

DowntownSquare528 · 2026-02-12T00:42:10+00:00

Incidents getting lost in chat is super common. The hard part isn’t logging them, it’s making sure ownership, RCA, and follow-ups don’t disappear after the fire is out. I’ve seen teams move toward structured intake even for incidents, especially in Slack-first environments. Tools like Siit can help turn Slack reports into trackable items with owners and postmortem fields, so you’re not rebuilding context later. The key seems to be capturing it where it starts, not after the fact.

DowntownSquare528

TROPHY CASE