The users in question are posting on a public forum under a username of their choosing, and it's still an invasion of privacy to read those posts and play pretend matchmaker?
For starters, it breaks two rule of the thread: "Agencies, recruiters, job boards, and so on, are off topic here" and "please only email these addresses to discuss work opportunities".
> The users in question are posting on a public forum under a username of their choosing, and it's still an invasion of privacy to read those posts and play pretend matchmaker?
Yes it is. There is an aggregation happening, that is not available on Hacker News per se. To make this aggregation easily available to anyone else is some kind of privacy invasion. To make matters worse, usernames can be traced back to IRL individuals, depending on the information they put into their "About" page on Hacker News. So yes, this is indeed an issue.
I think it's naive to be bothered by the scenario you describe just because it's visible to you and yet it's still being done everywhere you go whether you like it or not. Similarly, just because this Show HN is visible to the user it becomes a privacy issue, whereas hundreds of web scrapers are doing the same to HN every day and you don't know about it.
We are living in the Wild West of privacy. If you don't like it, you can share your grievance with the people running the public space or disengage entirely. It's still going to happen.
A third option is to air your grievances on that same public space and find people who feel similarly and care enough to raise their voice, and hopefully spread awareness and affect change. Which is also totally valid and what these users are doing.
You hung up a “services offered” flyer on every town square around the world and want to control what people do with the information after you’ve shouted it into the void? Don’t post if you don’t want every tom, dick, or jAIne reading your stuff.
The same principle applies: You would have to leave the service when it starts introducing such things.
As a market-driving force in the real world, basically an impossible task for the collective. However, occasionally consumers do successfully band together to abandon a service due to some perceived slight.
Been using it for half a year and so far it's doing well. I never remove it from its case so there's not much wear happening on the connector. At least it protects the original port as well.
The creator is really nice and basically handles everything himself. I had n issue in the upper separate piece and I learned just the top part can be ordered and replaced for cheap.
But how can I find the answer to the question without reading punchy headers followed by paragraphs like
> How We Leverage Naming
> Our Naming Strategy, Explained
> Why Swedish Is Important
> The Bottom Line
And unforgettable aphorisms like
> It isn't just a name—it is the output of a scalable, globally coordinated, linguistically validated, Swedish-inspired naming framework designed to optimize brand consistency
to let me know? I'm completely lost on this page and can't find the answer without these.
How long until someone invents a fully-integrated local video and audio adblock filter running on a passthrough VR headset or smart glasses? The progress on this front is taking a while. I wouldn't mind if the audio filter is white noise and a portion of what I see is blurred out. Maybe to make it more efficient, only scan near the places I'm looking at via foveated rendering.
How about we just get on with it and delegalize ads already? They’re a net negative in every form, subsidizing disgusting companies that shouldn’t exist, infringing on everyone’s privacy (including your children! think of the children!!!!!), and making us jump through all kinds of ridiculous hoops to minimize our exposure to them. I don’t think the solution is more hoops.
I don't think ads should be illegal because companies have a right to try to send me information or inform me of their products, but I also have a right to block them. The problem is that client-side computing seems to be lagging behind. Once an effective local video+audio filter is invented, it's either game over for adware or another arms race will begin where humans and classifiers can't tell what an ad is anymore (this has already run to completion on many platforms like Reddit, Amazon, and Google Maps anyway).
Criminalizing information flow is a non-trivial problem that I wouldn't want governments to be in control of.
Ads and the surveillance ecosystem are more than just a company sending you information. They're paying another company, which that other company uses to provide services below cost (often free, and often creating network lock-in effects), which is clearly an anti-competitive business practice. Ads completely destroy markets they operate in.
"companies have a right to try to send me information"
The problem isn't one company sending information unsolicited, it's when hundreds of thousands of companies flood every communication channel with their own unsolicited advertising.
Email, phone have become unusable channels, not to mention much of the web.
I've had to make the same request multiple times recently. Has anyone noticed it getting worse with the more recent models? It reminds me of when someone is trying to convince you of their intelligence by replacing simple and straightforward explanations with words pulled out of a thesaurus, so maybe that's the objective of these more recent iterations. Throwback to grade school.
That’s a common trope I see in “old” books (most recently for me in _Old Mortality_) that I can’t recall ever seeing in modern ones - deliberately obscured words intended to convey a notion of realism without naming an actual place or person. I guess it’s the 555 phone number of old books.
"It is (and, increasingly, was) used to signify that a bibliography entry has the exact same author(s), editor(s), translator(s), or corporate author(s) as the previous bibliography entry."
I mean... would it really be that big of a crime against humanity to insert two or three em dashes if the situation seriously needs it? I already have enough trouble distinguishing an en dash from an em dash.
Absolutely does not deserve a new character just for that(especially one that is so unusually large).
Whoever introduced that is absolutely drunk on power.
The only reason that exists is because of a power discrepancy where the people with powers to create new characters are also the ones who do enough writing that they feel such a specific and niche pain.
Did you notice the examples were really old? Like late 1700s old?
Now, imagine you have a wooden box of lead or pewter letter forms. They're small, heavy and backwards. You spend your days lining up those forms in rows and then pressing them to ink and paper to print books and documents.
So you're lining them up, slowly running out of 'e's and 'f's and 'r's. You decide to save yourself some time and more importantly some of your precious few letters that you need to make last the whole page. So you omit some of those words, names in this case, and establish a convention with other printers and authors about how and when to replace words with shorthand. This lets you and your fellow printers save time by not having to work to arrange those admittedly duplicate letters and stretch those letters.
Fun fact, that's why old 's' are sometimes written with an 'f' missing the bar. Because they were re-using forms where otherwise a letter was so common they'd run out!
> So you're lining them up, slowly running out of 'e's and 'f's and 'r's. You decide to save yourself some time and more importantly some of your precious few letters that you need to make last the whole page. So you omit some of those words, names in this case, and establish a convention with other printers and authors about how and when to replace words with shorthand. This lets you and your fellow printers save time by not having to work to arrange those admittedly duplicate letters and stretch those letters.
Seriously? You're claiming printers invented shorthand and abbreviations to make working with movable type easier? They were common in handwriting and predate the printing press. Look! Even the Wikipedia page for abbreviation has an illustration from scribal handwriting: https://en.wikipedia.org/wiki/Abbreviation.
> Fun fact, that's why old 's' are sometimes written with an 'f' missing the bar. Because they were re-using forms where otherwise a letter was so common they'd run out!
No, that's from handwriting, invented in the 8th century (https://en.wikipedia.org/wiki/Long_s). Go read the original handwritten copies of the US Constitution or Declaration of Independence. You don't have to read far until you find a long s:
>The only reason that exists is because of a power discrepancy where the people with powers to create new characters are also the ones who do enough writing that they feel such a specific and niche pain.
Counterpoint: the people who use tools the most should be the ones designign and creating them. All you have to do is continue not using it just like you did before it existed, but instead you insisted that its existence make sense to you as someone who doesn't need it and doesn't do what it's meant to help with.
I'm sorry but someone has to stand up for simplicity and to stop garbage from making its way into open public standards.
The bar has to be set somewhere. How many people actually use this thing? We can't go introducing characters into standards just because six people with power want some claim to fame.
I for one wasn't even aware that Unicode characters could be so large. Did they have to make a special exception for this or are there other characters that are that wide?
I don't think they're adding these things for fame, I gotta say. And yeah, unicode characters can be pretty large. Again, this is isn't even the tip of the iceberg of unicode complexity or weirdness.
Just because it’s a problem you’ve never encountered doesn’t make it stupid.
You’ve clearly never had to deal with a lot of references. Author lists can cluster. If you’re reading, it can get tedious if the last 5+ references are to the same three authors. Let alone 20+ references.
This happens. In some writing it happens _a lot_.
It’s a common enough that it’s even explicitly mentioned in the Chicago Manual [0], one of the main style guides for academic writing in the US:
> Em dashes also substitute for something missing. For example, in a bibliographic list, rather than repeating the same author over and over again, three consecutive em dashes (also known as a 3-em dash) stand in for the author’s name.
> Just because it’s a problem you’ve never encountered doesn’t make it stupid.
That's not what I said or what I intended to imply.
I think it's stupid because It sounds like the thing that I would assume almost nobody encounters. Like so few people that this is not needed. If more than 10,000, people have ever typed this thing out for its intended purpose, I stand fully corrected.
The line has to be drawn somewhere to prevent garbage from making its way into open standards.
How many people actually use this thing? 10 loud people with power using it does not justify putting it into the open standard.
This isn't some some language that thousands of people speak. To me this seems like some weird thing that some drunk academic came up with and told his friends about.
Also, this thing is freaking huge. How many characters are this wide? Should the bar be higher to introduce obviously weird characters?
> The line has to be drawn somewhere to prevent garbage from making its way into open standards.
Given that the term is explicitly mentioned in the Chicago Manual of Style, I suspect that this is much more of unicode trying to capture existing behavior, even if rare. And I think it's important to err on the side of capturing what people did, even if it's from an bygone era.
> How many people actually use this thing? 10 loud people with power using it does not justify putting it into the open standard.
It's definitely more than 10. But even if it's 10, I disagree with your assessment. People used this; it's worth a codepoint. There are far stranger code points out there.
And I've seen far weirder things in open standards. Have you read the C99 standard? Are you aware of the three allowed integer representations? Of which maybe two were in use in 1999, and one only in use in relic hardware that might exist in maybe tens of sites.
That assumption is incorrect. There are a lot of people doing academic research and of those people the vast majority of them encounter this situation a lot. This is like insisting that a strap wrench is stupid because most people don't ever need one.
To make it accurate, it would be like if there was only one store you could ever buy things from and that store had a limited number of shelves, and someone came along and wanted to use up one of the shelves that to sell an old tool that few people need, and they also only accepted a weird form of payment that would randomly cause issues with some people.
I think we're getting at the heart of your misunderstanding. You seem to feel that we're running out of codepoints in Unicode (the “limited number of shelves” analogy). This could not be further from the truth. Although the number of codepoints is technically finite, it is extremely large (over a million) compared to how many we need (currently only 160,000 are defined, and for obvious reasons the rate of new additions is slowing down). The Unicode roadmaps main page[0] displays only 5 of the 17 available planes because the remaining 12 (each 65,536 codepoints large) have not yet had any characters assigned to them whatsoever.
Hmm, like in the References section for a paper? Personally I don’t see any point to typing that sort of thing out (bibtex handles it more accurately that I could anyway).
For the reader… I dunno, do people actually read through a citation list, in a manner where the redundancy would be relevant? When I look, I’m usually specifically looking for the single entry that corresponds to the citation on some claim in the text.
Although if someone really wanted these triple-dashes for their journal for some reason, I bet some tex could be coded up that would generate them. Could look neat, maybe.
> Personally I don’t see any point to typing that sort of thing out
As other people have commented, it's partly a relic of an era where things were typeset by hand. Some journals may also require this in their style guide; I don't know of any offhand but the list of journals is long and their choice of style is varied.
> I dunno, do people actually read through a citation list, in a manner where the redundancy would be relevant?
Yes, they do. When you work on a Ph.D.-level dissertation, you end up having to learn your subfield pretty well: its major works, open questions, current major players, their ongoing arguments, etc. You start to notice citations cluster, and you can often find more than one opinion group. People you have to listen to (ie: your advisor / committee) will hand you articles with authors you don't know and who may come from labs that you don't know. One common way to start orienting yourself is to look at who they cite.
You pick up patterns: some people love to cite themselves and their friends, some people really try to give a detailed overview of the state of the field, and some people go out of their way to attack their rivals via citation. Sometimes the reference list has an author or work you don't recognize, and might have missed while glancing over the text. Mostly it's something mildly relevant and occasionally it's an exciting direction to look into.
The really long citation lists, where the triple emdash would make sense, mostly occur in fields outside science and engineering where knowledge is exchanged through chapters and books. Some fields expect a lot of detailed textual analysis which can involve a lot of careful citation of the same chapter or book over and over again.
While I've never worked in these fields, I've been friends and roommates with people in them, and I quickly learned that bibliographies are way more of a thing for them than I ever imagined.
I do have a PhD, and I have crawled up the trees of citations on occasion. But they were not so huge that I needed to manage them actively. But it was STEM, I wouldn’t be surprised to hear that more complex bibliographies exist elsewhere.
If not, I doubt some typesetter in the 19th century (or earlier) was so drunk with power when setting out the lead type to make the 3-em dash.
EDIT: Additionally, unicode primarily exists to encode the typographic symbols that exist—that is to say, it's a catalog of what already is. Take Ogham[1] for example.
I do miss the old PHP manuals on Hurricaine Electric with the comment sections where anyone could discuss every function, ask stupid questions, and post totally bogus answers, which everyone would then believe without skepticism, then copy and paste into their code in production.
It was like pre-AI poor man's artisnal LLM hallucinations.
There need to be chat discussions like that for every unicode character.
Only know the discussion superficially, but from what I understood, the problem was as follows: Chinese Hanzi, Japanese Kanji and Korean Hanja scripts have the same historical roots (Han) and still look very similar when you write them — however, they are fully separate scripts with different use of letters and optical differences that are important.
However, when encoding them into Unicode, the consortium suddenly discovered the importance of being frugal with character IDs and only defined a single "Han" sequence of characters for all three scripts. You need to select a matching font to actually display the text in the script that's intended.
This makes using those characters an unnecessary hassle and also came over as a cultural faux-pas to some (essentially like encoding Greek Eta, Latin H and Cyrillic En as the same character, because they look similar and the scripts have a common history)
<s>It also looks a bit hypocritical when Unicode otherwise goes the opposite way and has the space to encode dozens of variants of the Latin alphabet or — as we see here — several categories of dashes.</s> (Edit: Han unification was done when Unicode was still 16 bit, so there were real space constraints — so no hypocrisy actually)
I honestly agree with the arguments they made to defend it, but then they tied themselves in loops trying to defend things like separate Greek and Cyrillic scripts and making superfine distinctions about how that isn't the same phenomenon. But they couldn't merge those scripts together now even if they wanted to, because of the stability policy. And the existence of the blackletter, small-caps, superscript, etc. characters seems entirely indefensible to me. All font rendering issues; it's clearly the same symbol with the same fundamental meaning.
Really, they needed to come up with the idea of variation selectors way earlier, and use them aggressively. And design something more consistent for character composition, and skip the precomposed characters (those really are glyphs representing a cluster; being able to treat the cluster as an atomic entity versus its components doesn't add actual semantic information to the text).
If I'm writing a text about Russian language in English, I can easily include an example in Russian: "привет, как дела?" and it will be displayed correctly.
But, if I was writing about Mandarin Chinese in Japanese, I just wouldn't be able to do it using a simple text input (like HN comment form). I would need more advanced formatting tools to make sure that both Chinese and Japanese characters are displayed correctly.
Because, as far a I understand, one Unicode symbol could correspond to both a Hanzi character and a Kanji character. Which character will be displayed is only determined by font. Since HN doesn't allow me to select different fonts for different parts of my comment, it is simply impossible to create a comment that includes both Japanese and Chinese characters.
That depends. Your interpretation is “em+en+em”. But another, potentially wittier interpretation is “em in em”, i.e., you split an em-dash into two en-dashes and put an em-dash inside.
Three-em dashes are multinational conglomerate punctuation.
They can be used as adhesives, abrasives, laminates, passive fire protection, personal protective equipment, window films, paint-protection film, electrical insulation, car-care products, electronic circuits, optical films, Scotch tape, Post-it Notes, labels, dispensers, and magnetic tape.
In German, nouns have gender, so why not more inclusive punctuation? The him dash, her dash, it dash, and the nonbinary them dash. It would really infuriate MAGA if you could apply emoji gender and skin color.
And of course if you really want to make a statement and stick it to those anti-AI em-dash nit-pickers, there's always the Zen-like struck-out no-break space (U+00A0 NO-BREAK SPACE + U+0336 COMBINING LONG STROKE OVERLAY) ̶ ̶ ̶ ̶ ̶ ̶ ̶ ̶ ̶ ̶ ̶ ̶ ̶ ̶ ̶ ̶ ̶ ̶ ̶ ̶ ̶ ̶ ̶ ̶ ̶ ̶ you can combine them to any length!
It's a shame Hacker News filters out the really good ones, like the üm dash: — (U+2014 EM DASH + U+0308 COMBINING DIAERESIS) and the over-accentuated üm-á-ñå-ḍ-ç dash: — (EM DASH + DIAERESIS + ACUTE + TILDE + RING ABOVE + DOT BELOW + CEDILLA).
@dang I know @mentions don't work so you'll never read this, so screw you for filtering out my favorite glitchy punctuation diacritics, you jerk! I feel like my creativity is stifled and freedom of speech suppressed!
> They can be used as adhesives, abrasives, laminates, passive fire protection, personal protective equipment, window films, paint-protection film, electrical insulation, car-care products, electronic circuits, optical films, Scotch tape, Post-it Notes, labels, dispensers, and magnetic tape.
Triple emdash cannot be used as a lubricant. Do not touch, inhale, or look at triple emdash. Do not taunt triple emdash.
I'm not sure why this has to be specified more than once. Is a "slurry" meaningfully different enough from a "suspension" or "solution" such that it needs to be specified each time?
reply