ttldr · HackerTrans

@mods -- could we link to the DoJ post linked to in the article? the article doesn't contribute anything new other than superfluous (at best) images and salacious descriptions.

https://www.justice.gov/usao-ndga/pr/former-global-diversity...

ttldr

3 年前議論

depends how you do it?

good idea: https://en.wikipedia.org/wiki/Sokal_affair

bad idea: https://www.theverge.com/2021/4/22/22398156/university-minne...

ttldr

3 年前議論

congrats! regarding this particular post, you may want to revisit the primary source material, the secondary source tik tok, and ultimately the relevance of the post

https://news.ycombinator.com/item?id=36689930

EDIT: i don’t mean to take anything away from your blog, and thank you for posting these links! the theme is super interesting and 100% deserving of attention and analysis. thank you for putting it together, i’m enjoying reading through the posts :)

ttldr

3 年前議論

i think both OP and the motivating tiktok have misread, even inverted the narrative.

after rewatching the music video for Dilemma[1], i’m reading the nokia phone scene as: she’s received a message from her “boo” inquiring her whereabouts as she pines after nelly, and is not in fact attempting to send a message to nelly. that the green shirt and white pantsed clad figure outside her window is indeed nelly, and not her alleged boo, is supported by the prior scene in which nelly, clad in same clothes, is seen grinding with kelly in the street.

this changes the narrative of the linked blog post entirely. kelly was sold as a bimbo trying to send a text via a spreadsheet app without internet connectivity, when the facts better support a narrative of her being sent a needy message by this unsatisfactory “boo” in the form of a spreadsheet attachment (what a dork) while she further cements her infatuation with nelly and his unbelievable cheekbones (and inexplicable cheek sticker).

if she’s the recipient of a message, and not the sender, how could the HYPERLINK= VBA function be relevant at all?

[1]: https://youtu.be/8WYHDfJDPDc

phone scene time stamp 3:05

ttldr

4 年前議論

the article is certainly "Articulate", and i'm sure its content and message is agreeable to many in the community (myself included). no doubt that it speaks to the day-to-day chafes of working engineers and other technical folks in a corporate environment.

taking a look at the author's startup[1] is interesting. it seems clear that he's trying to collapse employees' personal slack afforded by remote/async work. that makes sense in terms of boosting butts-in-seats accountability, and i guess by some draconian measure that could translate to "productivity" (read: answering random interruptions to deep work). but i worry that the very dynamic he's espousing would itself kill builder culture. you can't think deeply about a problem when you have people bombarding your attention based on their own whims. from the company's landing page:

> Actually talk with your coworkers. Walk over to your teammate for a quick question. 10x faster than sending a zoom link.

also, i guess this is more aesthetic, but the skeuomorphism is super weird. i would be super suspicious of a work environment that requires this sort of SIMS-like virtual environment. it seems like a half-assed, 2D version of VR workplaces that are crawling their way out of R&D departments at certain advertising companies (looking at you Meta(verse)).

[1] https://www.teamflowhq.com/

ttldr

4 年前議論

FTA:

> I dunno where I'm going with this. I don't have any big thesis. I just wanted to write it down.

the invectives of “what did you expect?” seem at best tangential to the author’s intent here. sounds like they’re just trying to express perspective, not mount an argument with a specific aim.

to the author’s point, wasn’t it great when the internet had convinced itself that “zero sum”/scarcity were an unnecessary constraint of a physically constrained world? that ideal may not have shaken out, but there’s no reason to disparage someone for lamenting it (especially when they’ve actually put sweat into that vision).

not everything is a pitch. speech isn’t always an an advertisement or a polemic.

ttldr

5 年前議論

also not related to criminal investigations, but I've found How to Solve It by George Pólya to be very useful

ttldr

7 年前議論

> Sometimes being the voice for change, sometimes being the voice for not change. Always weighing up trade offs, always listening.

[emphasis mine]

i think she makes a really good point here: one that's often overlooked by the "improve"-everything-all-the-time culture that a lot of contemporary tech inveighs.

it's easy to advocate solipsistically for an alternate solution that you came up with. it's harder to objectively weigh the merits of extant design decision and admit that your predecessor made an optimal (or more-optimal-than-you-can-muster) choice and defend it. iconoclasts may occasionally create great things independently (perhaps if they're a Linus Torvalds or a Margaret Hamilton), but the meat and potatoes of building functional and robust software is building well on solid foundations, specifically by respecting those foundations when they're sound.

ttldr

7 年前議論

there are a lot of comments on this thread about the moral hazard of pharmaceutical advertising. i think the arguments against such advertising largely hold water, but i’m curious; what are the arguments for it?

can anyone substantiate an argument for why consumer advertising for prescription medications is good for patient outcomes?

ttldr

7 年前議論

+1. if you want to take it a step further, move all apps to folders in the second screen. this leaves you with a blank screen when opening the phone, and essentially forces you to search for the app you need instead of browse through your apps and potentially get distracted.

i tweak my (iOS) spotlight settings to only search apps, which makes the whole flow as simple as:

  - unlock phone
  - swipe down anywhere on screen
  - type first 2-3 letters of app name
  - open app

within a few days, this gets to feel intuitive, and much quicker than paging through lots of apps. even better, it forces you to know which app you want ahead of time, reducing chance of distraction.

this may seem subtle, but it’s been huge for me in reducing idle/wasted time on the phone.

edit: formatting

ttldr

8 年前議論

all fair points. and your product seems to be designed/documented/marketed with the notion of keeping the username (which is part of the ENVKEY) secret, so agreed that "security-by-obscurity" is unfair (coupled w/ massive ID space).

your product is very well designed, seems like a tremendous customer experience. best of luck; i hope you continue to grow

ttldr

8 年前議論

looks neat! would love to use something like this at work.

with regards to the S3 fail-over, how do you manage per-account access/authz?

source of fetch.go seems to indicate a single bucket is used for the fail-over: http://bit.ly/2p6ozyN

do you create per-account restricted policies and somehow have the client assume a particular IAM role or do you just have a world-readable bucket and rely on PGP for secrecy?

UPDATE: turns out that the first half of the ENVKEY (before the '-') is some sort of "env id". the S3 URL is then formed by appending the API version (v1 is valid, not sure if it's current) to the base bucket and prefix (see earlier bit.ly). for shits 'n giggles, let's try using the ENVKEY from the site's landing page ("p9WYzzHefy33gzgDdvPJ-EKdh4jgBsRBBNerK").

let's test it out with a simple, unauthenticated cURL:

  $ curl -s s3-eu-west-1.amazonaws.com/envkey-backup/envs/v1/p9WYzzHefy33gzgDdvPJ | wc -c
     15291

  $ curl s3-eu-west-1.amazonaws.com/envkey-backup/envs/v1/p9WYzzHefy33gzgDdvPJ
  ...

small sample of output for latter cmd: https://pastebin.com/igXQrk2z

so, it appears that the fail-over "feature" exposes your PGP-encrypted secrets to the world _without any authentication whatsoever_. PGP is pretty secure, and the space of potential IDs seems pretty large (20 chars^(26+26+10) ~ 4.61e80 potential IDs) so that's probably fine...

can users opt-out of the fail-over feature?

EDIT: s/security-by-obscurity//

コメント