Kalcifer @ Kalcifer @sh.itjust.works

All of this user's content is licensed under [CC BY 4.0](https://creativeco

---

Read more

Posts

161

Comments

1,710

Joined

2 yr. ago

[…] Admins don’t need demographic data at all.

What makes you so certain of that?

[…] It seems fairly likely that we will get a lot of junk data mixed in with the real data, making its usefulness questionable. […]

I am by no means an expert on the subject, but I presume that there are methods that can be employed to filter out bad-faith respondents.

[…] this isn’t official (yet). […]

Fair point! ^[1]

[…] I think OSM shouldn’t just go out and follow every random suggestion any politician makes. […]

I think there's some use in including a countries official names for specific features, in some way. I'm not saying that the primary name should be that, but it's at least a name that is known and conceivably could be searched.

[…] Let’s wait until anything actually changes officially […]

Hm, I would argue that there is no such thing as "officially" in regards to OpenStreetMap. Or are you referring to the name "Gulf of America" changing officially in the USA?

[…] Let’s wait until anything actually changes officially before we start going with some wild claim

I wasn't claiming anything — or, perhaps I misunderstand what you mean? Would you mind clarifying?

[…] It’s these fields that are relevant to Lemmy’s API, not the terminology that ActivityPub uses. […]

Fair point! I was incorrectly assuming that Lemmy's terminology directly matched that of ActivityPub.

[…] Lemmy distinguishes between ‘name’ for username, and ‘display_name’ for the display name. A better link for this is arguably https://github.com/LemmyNet/lemmy/blob/main/crates/db_schema/src/schema.rs#L735 but whatever. It’s these fields that are relevant to Lemmy’s API, not the terminology that ActivityPub uses. A client might reasonably want to know the limit for a username (as provided in the Site response), because it’s this that’s used for Signup and Login. Display name is set elsewhere, once that’s done, so it doesn’t make sense for actor_name_max_length to refer to this.

Within ActivityPub, the distinction between username and display name is ‘preferredUsername’ and ‘name’, but AP also uses ‘name’ for a bunch of other things (including but not limited to what becomes a post title, a choice in a poll, or the alt-text for an image). There’s some overlap with how Lemmy’s API refers to stuff (e.g. a post title is a post name), but it not a 1:1 match. […]

Thank you for providing this information.

[…] You shouldn’t have to be relying on guesswork by amateurs, irrespective of how many ‘references’ they can quote.

I think you are misunderstanding how I am using references. They are only being used to point to the origin of a bit of knowledge. Their existence does not guarantee any level of accuracy.

[…] What you should be asking, is - “How come when I post a question to Lemmy’s support community, on the instance owned by Lemmy devs, it looks like they just ignore it?”. […]

I have no reason to expect any obligatory answer from anybody. IMO, it would be very entitled of me, or anyone else, to expect otherwise.

[…] I don’t even use Lemmy, so - in my opinion - you’re asking the wrong question to the wrong person. […]

I don't know you, so how would I know what your level of expertise is regarding Lemmy? You are the one that commented on my post...

[…] I give you reproducible command-line instructions, which match up with your own findings, and it’s apparently not good enough. […]

Did you perhaps not see that I cited your comment's findings as a source for the solution...? Or is it that you can't believe that I would dare to exhibit any amount of skepticism of your claim?

You’ve accepted […] one link to a years-old migration as [an] answer,

[…] as that migration shows […]

I'm not sure what you are referring by "migration". Could you clarify?

[…] You’ve accepted your own unscientific prodding of one particular instance as an answer […]

What exactly do you think is unscientific about it?

I’m not used to this level of rigour to be honest. […]

In my opinion, one should always be open to scrutiny of their claims. One should strive to be precise in their communication — ie one should seek to rectify any uncertainties, ambiguities etc.

[…] they’re always using the same credentials no matter the website they use and no matter the website they can interact with everything that ever happened on the servers, no one has the power to prevent users from seeing some of the transactions that happened (no admins) because the website they use are just a front used to simplify interaction with the servers. […]

Hm, IIUC, this is one of Bluesky's issues that the linked blog post was pointing out — if joining the network requires one to mirror all existing data, it makes it prohibitively expensive for anyone to spin up a server to join the network if the size of the network is enormous.

If things were decentralized in similar way to crypto it would be way better for user adoption.

IIUC, are you perhaps referring to something like Nostr?

🐻 "it's not. it's not. it's not. ..."

🐻 "it's not. it's not. it's not. ..."

🐻 "it's not. it's not. it's not. ..."

/j

❤️

[…] Will try to emulate it going forward. Appreciate your […] style.

Keep in mind that my citation style is still very much a WIP 😜. There's a few things that I'm not sure exactly the best way to handle, at the moment. If you see inconsistencies in my citation style, it's likely because I'm trying out a change in formatting to see if it works. I'm trying to not let perfect be the enemy of good, so I'm developing it as I use it. Eventually, if I can get it to a satisfactory state, I'm planning on publishing my citation style (likely in some git repo). That way, I can standardize it and version the changes.