Piero Bosio Social Web Site Personale

RE: https://mastodon.au/@Heliograph/116105174299893549

I wonder if it's possible to get a job making drones without your work being used to kill people

@soc What is the total ordering with respect to NaNs?

std::cmp::max fails.

The error message: "the trait bound `f32: Ord` is not satisfied"

*belabored sigh* sometimes the most frustrating thing about Rust is that it does things correctly

This is a very funny page https://unicode-explorer.com/list/large

@alilly @Hearth @xgranade ohhhh wait that would make so much sense :O with the old jamo

@chrisamaphone so remember, part of the revanchivist ideology in Analogue involved enforcement of writing in Hanja

Typed :( in a Rust comment and Sublime Text autocompleted it to :()

@thatdawnperson But seeing them lead with that just makes it seem oddly vindictive

@thatdawnperson I thiiiiink that the way they fit the antique Korean jamo into requires a really awkward hack that they just don't want these systems to have to deal with

@tomjennings An open source project I worked with used it as a total google docs replacement… we liked it. Isn't there an about page talking about who's behind it? It isn't loading for me today.

Somebody linked me RFC 7565, which linked to RFC7564, and if that's the place to look this appears to be the list of disallowed characters in a Fediverse username, and I'm cracking up because it's *mostly* stuff you'd expect, except the very first category of banned characters, specially, is "pre-1700 Korean characters".

The fediverse is welcome to all. EXCEPT KOREAN TIME TRAVELERS. Did you just wake up from being frozen in ice during the Joseon dynasty? The IETF is targeting you PERSONALLY

Consider a Mastodon/Fediverse handle, like @username@domain.example . What kinds of restrictions are there on "username"? Can I assume any valid unicode could go in there?

@lambdageek i'm going to write a unikernel in rust and crawl inside it forever

@ratsnakegames It would have worked!! It would have worked!! I trained myself out of "turn it off and on again" and that was the correct solution!!!

@lambdageek it worked. thank you

so to summarize, nothing was wrong, it's just the relevant daemon needed to be rebooted, and that's such a 1990s Linux kinda problem it didn't even occur to me to try it. i thought we were past that

*rolling around on the floor in pain* this is even more upsetting

https://mastodon.social/@lambdageek/116099504356976778

this worked

the problem was not the publish-workstation=no

the problem was not debian; nothing changed

my local avahi daemon had simply locked up

at least one other person replied to say their avahi daemon wedges semifrequently and they have to restart it

now i kinda *do* want to use the systemd mdns provider

however unfortunately https://chaos.social/@elomatreb/116099505178400601

@lambdageek Oh, that is such a good question :(

@elomatreb ow. ow. ow. ow. ow.

thanks for the explanation.

@lambdageek That's very interesting… to your knowledge, am I doing something *wrong* if I just switch publish-workstation to yes?

As far as I know what you just said is *correct*, but the fact I know what avahi is, but I don't know what nssswitch/libnss-mdns are, makes me nervous about touching the latter when making a change to avahi worked