LILinuxBender·Aug 29, 2018
It is on Github [1]
[1] - https://github.com/g3rv4/BetterSlack
In Bye bye BetterSlackg3rv4
Refined
TypeScript2018–2018
g3rv4 / Refined · Archived
Refined
An extension to personalize Slack
2Distinct people
2Mentions
0Explicit recommenders
155GitHub stars
What to know before exploring
What it is
An extension to personalize Slack
GitHub
Where it is used
No documented product use has been verified yet.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by 3-hour interval2 dated mentions
Observed mentions: 2018-08-27 17:31:42 UTC to 2018-08-29 20:06:59 UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| Aug 27, 15:00 | 2018-08-27 15:00:00 UTC | 2018-08-27 18:00:00 UTC | 1 | 0 | 1 |
| Aug 27, 18:00 | 2018-08-27 18:00:00 UTC | 2018-08-27 21:00:00 UTC | 0 | 0 | 0 |
| Aug 27, 21:00 | 2018-08-27 21:00:00 UTC | 2018-08-28 00:00:00 UTC | 0 | 0 | 0 |
| Aug 28, 00:00 | 2018-08-28 00:00:00 UTC | 2018-08-28 03:00:00 UTC | 0 | 0 | 0 |
| Aug 28, 03:00 | 2018-08-28 03:00:00 UTC | 2018-08-28 06:00:00 UTC | 0 | 0 | 0 |
| Aug 28, 06:00 | 2018-08-28 06:00:00 UTC | 2018-08-28 09:00:00 UTC | 0 | 0 | 0 |
| Aug 28, 09:00 | 2018-08-28 09:00:00 UTC | 2018-08-28 12:00:00 UTC | 0 | 0 | 0 |
| Aug 28, 12:00 | 2018-08-28 12:00:00 UTC | 2018-08-28 15:00:00 UTC | 0 | 0 | 0 |
| Aug 28, 15:00 | 2018-08-28 15:00:00 UTC | 2018-08-28 18:00:00 UTC | 0 | 0 | 0 |
| Aug 28, 18:00 | 2018-08-28 18:00:00 UTC | 2018-08-28 21:00:00 UTC | 0 | 0 | 0 |
| Aug 28, 21:00 | 2018-08-28 21:00:00 UTC | 2018-08-29 00:00:00 UTC | 0 | 0 | 0 |
| Aug 29, 00:00 | 2018-08-29 00:00:00 UTC | 2018-08-29 03:00:00 UTC | 0 | 0 | 0 |
| Aug 29, 03:00 | 2018-08-29 03:00:00 UTC | 2018-08-29 06:00:00 UTC | 0 | 0 | 0 |
| Aug 29, 06:00 | 2018-08-29 06:00:00 UTC | 2018-08-29 09:00:00 UTC | 0 | 0 | 0 |
| Aug 29, 09:00 | 2018-08-29 09:00:00 UTC | 2018-08-29 12:00:00 UTC | 0 | 0 | 0 |
| Aug 29, 12:00 | 2018-08-29 12:00:00 UTC | 2018-08-29 15:00:00 UTC | 0 | 0 | 0 |
| Aug 29, 15:00 | 2018-08-29 15:00:00 UTC | 2018-08-29 18:00:00 UTC | 0 | 0 | 0 |
| Aug 29, 18:00 | 2018-08-29 18:00:00 UTC | 2018-08-29 21:00:00 UTC | 1 | 0 | 1 |
What Hacker News says
2 sources> If you write [here's a link](https://gmc.uy), it shows it as a link :)
> The nice part? it shows it as a link for everybody, not only those who have the extension installed.
Wait, wat? I'm looking at the code[0], and this is the most surprising part of this entire project to me. Slack goes out of its way to say "we don't support Markdown because we think the link support is an exploit." But they just have an alternate, undocumented way to send links anyway?
Is that a bug on Slack's side? I'm trying the syntax format that you're casting to in DMs to myself, and it doesn't seem to work? Are they doing clientside escaping or something?
Don't get me wrong, I think the "people might phish links" excuse is kind of lame when there are multiple ways for them to mitigate that problem, I'm just very curious about how and why this works.
[0]: http
In Show HN: BetterSlack – A Chrome extension to make Slack better