vonunov

135 カルマ登録 17 年前

コメント

3 時間前議論

>But then again I also never seen anyone writing a word and doing the dots afterwards.

Interesting, I'd never really heard of it being done any other way. I suppose it occurred to me that it could be done otherwise, but I'd more or less assumed the "all in a batch at the end of each word" way was all but universal. (When writing at speed -- trying to keep up with an overflowing buffer -- this tends to lead to all the 't's in a word sharing one long crossbar, and the dots floating somewhere high and right of where they should be, depending on how far I'm lagging behind the verbal "point of focus", if that makes any sense.)

3 日前議論

> Byzaboos

Hey that's fresh. Do they have Hittitomori too?

8 日前議論

Good thinking. Might as well get a three-day weekend out of it!

8 日前議論

TYPOCALYPSE — 186,943 pts wave 33 · 40 wpm · 91% acc · 985 kills · x144 best combo

Let us enter a name for e-peen points

Consider displaying active ("locked") word at the center as you do with the actives. With the passive that auto-kills other words, the intended queue of words to do next can be broken and the time lost in the search for the unintentionally focused enemy becomes a more severe setback the further you go. Some protection against inadvertently resetting the combo in this situation would also be cool (maybe as a passive ability)

Also consider displaying the word always to the inside (i.e. the side of the icon that is the opposite of the side of the field it entered from, which is to say make the enemies enter the field word-first)

9 日前議論

Or are they? I don't know what to think anymore.

9 日前議論

Oh, hell! How the tables have pivoted. I was sitting here shaking my head at all the people who didn't realize this postdoc had written a satirical piece and wasn't really insisting that she should be allowed to use ChatGPT at her chalk talk. . . . Chalk talks aren't a thing! Anymore. It's about whiteboarding lmao

26 日前議論

Look into "worded thinking", "unworded speech", "partially worded speech": https://hurlburt.faculty.unlv.edu/codebook.html

See also papers from Hurlburt and others on "unsymbolized thinking" and surrounding topics

先月議論

Oh, neat. From the demo, it looks like it retains faster movement during strafe-running. And edge-jumping (and presumably crouch-jumping) as well, or is that a different thing being used?

先月議論

[dead]

先月議論

> sysadmin

Another domain where LLMs are very effective at confidently leading people down a messy path. I have a roommate using LLMs to guide him through setting up some ollama stuff in my WSL (I happen to have the half-decent GPU here) and after multiple rounds of the bot trying to get him to do things that were redundant if not in the wrong direction entirely (and vaguely insulting as a matter of course), I had to write "ground truths" along these lines, and probably more as I find them:

  We are using systemd. ~/.bashrc or similar dotfiles should not be used to start services/processes automatically. Do not "sudo" anything in ~/.bashrc.

[Yes, it did that]

  A systemd service should be created for any processes/services that need to run automatically and persistently. The current output of `systemctl list-unit-files | grep enabled` is available at [ . . . ]  

  sshd is already enabled + running and listening on 0.0.0.0:22 and [::]:22. ~/.ssh perms are already 700 and ~/.ssh/authorized_keys perms are already 600. Public key authentication is already enabled in sshd and ~/.ssh/authorized_keys already contains pubkeys ENDING as follows: . . . 

  tailscaled is already enabled + running; the tailscale address for [host] is [addr]

  It is not necessary to fix connectivity to any 192.168.0.0/16 ; tailscale interface should be used for any traffic to [host] or other hosts involved in the project; hosts/nodes lacking tailscale interface should be assigned one

[roommate + bot spent 45 minutes on trying to configure their way through NAT when not having to do that is almost the entire point of tailscale. It was just (essentially) like, "You're absolutely right. We have tailscale set up, so we don't need to be able to ssh to that other interface at all. Not troubleshooting that would have saved 45 whole minutes. Oh well, now what?"]

Maybe it's just me, but I'm not inclined to trust the judgment of something that can't keep this kind of thing straight, which I know is to some degree a matter of having all the needed info in the context window. But maybe it would be able to do that if it didn't waste tokens telling me to cd into the same directory that I'm already in every 2 minutes, or chmod .ssh/ again, or (when it really needs to burn some tokens) blow away the .venv and pull a bunch of modules again just to "start clean".

先月議論

I used to do audio transcription and some video captioning. Found it a bit drudgerous and fatiguing in rather specific ways, but I was effective at it and could find some satisfaction in it. It's been some years now, so I haven't had a chance to try out the kind of thing they're doing now, but I'm pretty sure I wouldn't want to. I can raise my blood pressure just sitting here and thinking about what it would be like to have to go through a Word doc and correct the bot's errors. But, even putting aside my professional pride (or indignation), I can only imagine that it would make all kinds of mistakes I never would, and wouldn't be any help with the parts I'd have trouble with. And I'm pretty sure that, at least often enough for it to be an issue, the priming of reading what the bot thought something was could easily make it way harder to hear it correctly, if I notice there's something wrong in the first place. I assume there's a similar problem for your sister along the lines of throwing off how it would occur to her to express something in the target language.

先月議論

Oh boy, that means I'll be a real pirate! I can't wait

先月議論

> and will be ranked on how deeply the integration goes.

Oh, that must be why the Gmail web interface has so many spans that contain nothing but another span (including the span containing the "Press / to help me write" placeholder text in the message body area when replying). Here you go, boss, it's deeper now!

先月議論

I saw the "Press /" using Thorium (a Chromium fork). Tried to use the element picker in uBlock to get rid of it. This failed, of course, because the thing to be blocked disappears as soon as the text input area loses focus, even after I deleted every event listener that I thought could have been relevant.

In a Firefox fork (Floorp) using another Google account but with the seemingly relevant part of Gmail configuration matching, I don't see "Press /" at all. Not sure why exactly, it's a somewhat interesting question but I already went poking through dev console to write a selector for it and I'm starting to get irritated at the idea of spending any more time on it, lol

uBlock:

  mail.google.com##div[aria-label="Message Body"] span[contenteditable="false"]

or user styles / Stylus / etc.:

  div[aria-label="Message Body"] span[contenteditable="false"] { display: none !important; }

先月議論

  mail.google.com##div[aria-label="Message Body"] span[contenteditable="false"]

It is admittedly a bit beyond "easy customizability" once you find yourself sifting through element attributes in the dev console to craft a selector ("easy" shouldn't require knowing what any of those things are, I would think), but in case you still want to actually do it, this seems to work.

They have an ungodly number of event listeners. Why do they need so many? And I keep finding spans nested inside spans for no reason; i.e., the parent span only contains a child span. It's such an outrageous mess

先月議論

Marketing content without a reader persona or a writer persona, or rather, without the backing of a real consciousness with agency and life experience. I wonder if this might be part of why there are waves of different tells (in addition to the model updates): People pick up on an uncanniness in the writing but aren't fully aware of it or its nature, so they seek indicators and find what's there to find at the time

先月議論

> I'm not dropping emdashes -- though you can always tell mine by their two-hyphen form lol

I think of this as a dash (abstract function of punctuation) but not an em dash (concrete typographical form). I see the double hyphen as one of the possible representations of the dash¹ -- and a perfectly well-established one, to be sure² -- along with the em dash and the en dash, either of which can also be used to do the same job, depending on where you are and who you're writing for (the US uses em dashes of varying format (spacing) for that, while much of the UK uses en dashes with spaces to represent the same punctuation abstract). Are you instead conceptualizing the double hyphen as a representation of the em dash glyph?

If that makes sense then I'll leave it at that, but if it doesn't quite, then I have a somewhat longer hair-split I can send if you care for it.

1. A pseudo-glyph, maybe

2. Still acknowledged by Garner's as recently as 2003

先月議論

For what it's worth (or maybe just for the record) I have a counterexample: Gemini once dug in its heels and insisted that some ebay listings for GPUs were scams because the cards they were selling hadn't been released yet (they had been, but its training data was too old, I assume).

I went a few rounds with it and it kept pushing back, which was odd for sure, as I'm also used to being able to essentially just say "no, x = 2". There was a lot happening in that session (it was really someone else's and he just kind of lets his context windows fill up with all sorts of stuff), so I bet it would have sufficed to start a new one, but after a point I just wanted to see what would happen. It didn't concede until I sent it a PDF of some kind of white paper or tech spec sheet or something that included release dates from an authoritative source.

I may need to find that session later, because now I'm wondering if it was entirely the PDF that did it, or if it also helped to point out that the info cutoff could be a factor, and I don't remember whether I tried the latter first.

Also not sure off the top of my head what the situation was as far as model, custom instructions, or whatever else.

先月議論

Yes, this is the kind of thing I've been hoping more people would notice.

I think another tell with a long lifespan is that it will try to write about a thing it experienced, but having no real knowledge of the qualia, it'll end up only referring to it (not uncommonly using "that") and leaving all the substance as an exercise for the reader

先月議論

/* This function doesn't return an int. It doesn't return a float. It doesn't return a char. It doesn't ret-- */