Show newer

@niconiconi Ah, silly me for not noticing it. Thanks.

Huh, the way one should use it is somewhat funny (with the second identical transistor being used as a temperature sensor and the external heater controller).

Do you know what are the blemishes on pads with no wires? They seem to me like a wire was bonded and debonded there, but I don't see why that would be part of the production process (esp. given that the other two rings are narrower and shorter, so are unlikely to be viable substitutes for this one at production time).

@thibaultamartin @matrix I chose the instance running in my friend's kitchen.

@niconiconi What's that? I'm confused by the thing-in-the-middle that has no connection to the coils around (and the two out of three pairs of coils that don't have any wires bonded to them).

@nandalism

Sadly, fedi doesn't have a concept of following a thread (the same issue that mailing lists have, because it's modelled after them). If it had, that would be an obvious fit for following a game. Given that it doesn't, it might be useful to have a bot farm instead of a bot and create a new bot every time a new game is started. (I expect that honk's half-support for multiple users might be enough for that.)

Regarding players messaging each other _but not the bot_: there are two issues with that. First is that unless you are one of the players you can't feasibly find those messages, so public commentary track is not a thing. Secondly, Mastodon's (not fedi's) semantics around who-a-reply-is-cc'd-to are weird and I still don't understand them well, so I expect that players will not do that correctly most of the time.

> I really want to avoid spamming people who subscribe to sandestin but at the same time keep them up to date on the actions of other players.

I'm somewhat confused: what do you want them to see/not see in their inboxes?

> I must admit that how/when mastodon/honk decide to publish/show messages and where is a bit of a mystery to me.

Mastodon is confusing. If you speak in APub terms, then (if the source server doesn't lie -- the source server is the only guardian of the relationship between to/cc/bcc and where the message is actually sent):
- messages go to inboxes of all users who are in to/cc/bcc and end up in their feeds,
- messages addressed to Public go to public instance-wide and wider timelines (Mastodon terminology: they are not unlisted),
- messages addressed at whatever-the-name-is-for-followers-outbox get the moral equivalent of being sent to all followers inboxes.
What you can see on the public timeline _of the user_ on their local instance is instance-specific, on their timeline on a remote instance I don't know.

@trinsec But I do appreciate you pointing out ways to avoid the confusing part.

@trinsec I'm not saying it makes it hard for me to do things, but that that's a UI that's very confusing for newcomers.

@kuba @agnieszka @kukrak @arek @icd

Nie narzekam na ten konkretny przypadek, ale na to jak zasada jest sformalizowana.

@nandalism Also, do you have any ideas on how to integrate the commentary track?

@nandalism Do you intend to make it available (and legal to make derivatives of) within ~weeks?

@kuba @agnieszka @kukrak @arek @icd

Opłaca się tak skonstruować swój biznes/system który ten biznes implementuje/... żeby więcej rzeczy było "koniecznych". Sofort jest chyba dobrym przykładem na "zaplanowaliśmy wszystko tak, żeby straszne rzeczy były konieczne".

Nie znam wielu realnych przykładów na to w kontekście prywatności; realnie widuje ten problem w kontekście bezpieczeństwa w pracy ("musimy zrobić X, bo tak skonstruowaliśmy nasz system" w sytuacji gdy ta konstrukcja jest niepotrzebnie skomplikowana, a X nie powinno się nigdy robić -- i to wszystko w sytuacji gdy nie ma motywacji żeby robić X).

Główny problem, który mam z konceptem konieczności, to jego złe zdefiniowanie (*nigdy* nie jest konieczne używanie niczyich usług do przetwarzania danych -- zawsze _można_ to robić samemu, podobnie z komunikacją z klientami -- zawsze teoretycznie można mieć własną sieć etc.), które powoduje, że (a) można próbować przedstawiać sytuację w sposób który zmienia opinię słuchacza na temat konieczności (b) nie można z tego wnioskować (np. modus ponens nie działa).

@trinsec Yeah, that's JS-driven update without a reload kind of magic. Might be a bug then?

@trinsec Oh, that's very weird: if you navigate to that link it indeed does so. However, clicking on the "go to profile" link on mastodon.social/@foone does some magic (either JS-driven URL update or referer matching) and points you at the remote profile page on mastodon.social.

@nandalism Huh, so you don't checkpoint at every post? That's surprising; I would expect it to be way easier to do so (otherwise the synchronisation of the current state of the game between what's published on fedi and the internal state is much harder).

> It's more intended that people gather as a group to play a single game instance together.

+1. Are you aware of Club Floyd? (They do that over a text MUD.)

Is the source for the bot available somewhere?

@trinsec Imagine I'm a new Mastodon user (or even a non-Mastodon fedi instance user). I need to notice that "go to profile" doesn't yet send me where I want (and understand the concept of displaying remote profiles), and then find a link that's in a non-expanded menu.

@trinsec Because this is where the "go to user's new profile" link on mastodon.social/@foone takes me to.

Why is the link to the home instance of a user so hidden on ?

@kuba @agnieszka @kukrak @arek @icd

Jeśli przyjmujemy interpretację, że dostęp do zaszyfrowanych danych to dostęp do danych, to powinna zabraniać używania Internetu. Ale to pewnie jest konieczne do np. "sprzedawania przez Internet"...

@foone What's the phase relationship between the input and output?

Show older
Qoto Mastodon

QOTO: Question Others to Teach Ourselves
An inclusive, Academic Freedom, instance
All cultures welcome.
Hate speech and harassment strictly forbidden.