Docker Apology - Hackdot

Re:Docker Apology by afarrell on Thursday March 16, 2023 @03:55PM (#35187499)

One of the difficulties of public relations is communicating to multiple audiences at once. One of Docker’s audiences are the paying customers who outside that 2% and would want some assurance that if docker makes errors, those errors are smaller in magnitude. This statement seems like it is aimed at assuaging the worries of that audience. Is it good practice? I do not know.

[ Parent | on HN ]

Re:Docker Apology by dheera on Thursday March 16, 2023 @04:32PM (#35188078)

> One of the difficulties of public relations is communicating to multiple audiences at once.

Why not just release multiple statements and links?

"Click here for customized PR statement if you are a open source developer"

"Click here for customized PR statement if you are a closed source developer"

"Click here for customized PR statement if you are an executive who can't code"

"Click here for customized PR statement if you are a billionaire who invested in Docker but secretly don't know what it is"

etc.

[ Parent | on HN ]

Re:Docker Apology by hawski on Thursday March 16, 2023 @05:25PM (#35188902)

ChatGPT> Could you rephrase the PR statement to the ad profile of this HTTP client?

[ Parent | on HN ]

Re:Docker Apology by hk__2 on Thursday March 16, 2023 @05:48PM (#35189214)

What if you are a "closed source developer" at work but an open-source one during your free time? What if you are a billionaire codes? What if… etc. You could make TL;DR's targeted at specific audiences, but you still need the same introduction for everyone.

[ Parent | on HN ]

Re:Docker Apology by bleuchase on Thursday March 16, 2023 @06:54PM (#35190080)

Is that a serious suggestion? Who on earth would take the time to look through all of those to see which one best fits them? Companies have enough trouble getting press releases read already.

[ Parent | on HN ]

Re:Docker Apology by dheera on Thursday March 16, 2023 @11:40PM (#35192728)

I guess then you could use some heuristics and ChatGPT to tailor the press release to the particular viewer.

For example if the user has a screen resolution of three 4K monitors side by side, using Linux, and coming from a Silicon Valley IP address, they are probably a developer. If they have the screen resolution of an iPad Pro and a New York IP address they are probably an executive on the go. Use ChatGPT to reword the press release appropriately.

[ Parent | on HN ]

Re:Docker Apology by bleuchase on Friday March 17, 2023 @03:46AM (#35194389)

That could be a more effective approach.

[ Parent | on HN ]

Re:Docker Apology by AmalgatedAmoeba on Saturday March 18, 2023 @05:31AM (#35207575)

This is a genuinely terrifying vision of the future. Already things like prices may differ based one’s location. Adding content writing AI to the mix is positively dystopian.

[ Parent | on HN ]

Re:Docker Apology by r00fus on Thursday March 16, 2023 @04:44PM (#35188273)

Can't they say something like "a small and important group", yada yada, etc. Just laying out the % alone is derisive and pointless.

[ Parent | on HN ]

Re:Docker Apology by burnished on Thursday March 16, 2023 @04:54PM (#35188436)

Well, the end result would be some one else complaining about that phrasing being insulting, or a lack of transparency or something.

[ Parent | on HN ]

Re:Docker Apology by hgsgm on Thursday March 16, 2023 @05:48PM (#35189216)

There are 2 audiences: 1 with impact and 1 with 100% impact. The relative size of those audiences is irrelevant to the people in the audience.

[ Parent | on HN ]