Skip Navigation

Posts
124
Comments
254
Joined
5 yr. ago

cultural reviewer and dabbler in stylistic premonitions

  • What you want is not an "uncensored" server, but rather a server that is moderated in a way that you find acceptable.

    There is no such thing as an "uncensored/open" server. Or, when there is, it can't last long. Every open server needs to delete some things, because if they don't, their disk will soon be full of spam and CSAM and then the server will go away. Some servers claiming to be "uncensored" might allow nearly everything besides those two categories, but they tend to quickly become nazi bars.

    Sorry i don't have any specific suggestion, but of the 61 servers listed here hopefully there is one with a moderation policy that is to your liking.

  • just tell them "it's been a long time"

  • thanks!

    here is a side-by-side comparison of the neural network upscaling slop (left) versus a conventional zoom in on the original (right):

    and then of course there is the text:

    😦

  • i'm not aware of anybody who allows public signups and is interoperating with bsky.app yet (besides Bridgy Fed which will create an ATP identity for your ActivityPub identity), but I'm pretty sure it is possible because I follow people there who appear to be doing it for themselves.

    see also my reply to you in another thread.

  • Very interesting, thanks! Is it possible for people to register on that relay?

    (if I understand correctly) you don't register on a relay, you register on a PDS (which you can easily self-host on a small computer at home). But, to register with a PDS, you need a DID, and to interoperate with the rest of bluesky it needs to be using one of their two currently-supported DID methods: either did:web or did:plc. The former is a thing which you can create using a domain you control, which gives you an identity that you lose control of when you lose control of that domain. The latter is the actually-centralized "placeholder" DID method implemented by an append-only log operated by BlueSky PBC, which is what most people are actually using. I'm not sure if/how you can create a did:plc without first creating an account on a bsky.app PDS, but you can migrate it to your own PDS after creating one there. or, you can use did:web and rely on your domain name registration instead of their centralized log.

    Further reading:

  • as i wrote in another thread:

    Content addressability is absolutely essential for building something that will last, and BlueSky gets that right. Decoupling the many responsibilities which an ActivityPub instance operator has (especially for identity) is also essential, i think, and while BlueSky’s identity solution is less than ideal it’s much better than ActivityPub and I expect it to improve.

    If you’re interested in the topic you probably want to also read the followup post from the same author (after reading the reply linked there from someone on the BlueSky team).

    Christine’s analysis is by far the best I’ve read on the topic, but I think she is too dismissive of the possibility that people will actually build things using ATP in a manner more like ActivityPub (where there doesn’t need to be a global view). It’s also possible/likely that ActivityPub will eventually evolve to adopt content addressability (Christine actually built a proof-of-concept of doing that years ago, linked in her blog post, but there doesn’t appear to be any recent progress in that direction), and decouple identity from responsibility for data availability, and adopt something like BlueSky’s composable moderation.

    Given their respective advantages over the other, i’m pretty sure that both ATP and AP will make changes which make them more like the other in the coming years.

  • in what sense

  • Reading through it, I’m not seeing much in favor of ATP

    See the "BlueSky's strengths" section, particularly the last paragraph of it. Content addressability is absolutely essential for building something that will last, and BlueSky gets that right. Decoupling the many responsibilities which an ActivityPub instance operator has (especially for identity) is also essential, i think, and while BlueSky's identity solution is less than ideal it's much better than ActivityPub and I expect it to improve.

    If you're interested in the topic you probably want to also read the followup post from the same author (after reading the linked reply from someone on the BlueSky team).

    Christine's analysis is by far the best I've read on the topic, but I think she is too dismissive of the possibility that people will actually build things using ATP in a manner more like ActivityPub (where there doesn't need to be a global view). It's also possible/likely that ActivityPub will eventually evolve to adopt content addressability (Christine actually built a proof-of-concept of doing that years ago, linked in her blog post, but there doesn't appear to be any recent progress in that direction), and decouple identity from responsibility for data availability, and adopt something like BlueSky's composable moderation.

    Given their respective advantages over the other, i'm pretty sure that both ATP and AP will make changes which make them more like the other in the coming years.

  • In my opinion, yes, the why does in fact matter. This blog post i've linked in other comments in this thread is by one of the authors of the ActivityPub spec. If you care enough to comment about it i recommend reading her analysis of what AT Proto gets right and wrong in comparison with ActivityPub.

  • but you have to question why they’re choosing to reinvent the wheel

    you don't have to wonder why if you take the time to read about why; see the links in my other comments in this thread if you're curious.

  • Is there any instance other than Bluesky where people can register?

    There aren't "instances" in the ActivityPub sense, where "instance" means single point of failure you're married to (its name is literally part of your identity) which is simultaneously responsible for keeping your data available and curating your view of the rest of the network; AT Protocol decomposes these responsibilities so that they can be delegated independently to different operators.

    See https://docs.bsky.app/docs/advanced-guides/federation-architecture and https://dustycloud.org/blog/how-decentralized-is-bluesky/ for details.

    There are many people running their own Personal Data Servers, AppViews, Labelers, and Feed Generators, but I'm not aware of anybody else running a large-scale Relay yet (which is one of the things this new foundation says they are planning to work on). I'm also not sure if you can actually create a did:plc using a self-hosted AppView or if maybe you need to use did:web to create a new identity without using their AppView currently.

  • have you read about why they didn't?

  • "Given they were trained on our data, it makes sense that it should be public commons – that way we all benefit from the processing of our data"

    I wonder how many people besides the author of this article are upset solely about the profit-from-copyright-infringement aspect of automated plagiarism and bullshit generation, and thus would be satisfied by the models being made more widely available.

    The inherent plagiarism aspect of LLMs seems far more offensive to me than the copyright infringement, but both of those problems pale in comparison to the effects on humanity of masses of people relying on bullshit generators with outputs that are convincingly-plausible-yet-totally-wrong (and/or subtly wrong) far more often than anyone notices.

    I liked the author's earlier very-unlikely-to-be-met-demand activism last year better:

    I just sent @OpenAI a cease and desist demanding they delete their GPT 3.5 and GPT 4 models in their entirety and remove all of my personal data from their training data sets before re-training in order to prevent #ChatGPT telling people I am dead.

    ...which at least yielded the amusingly misleading headline OpenAI ordered to delete ChatGPT over false death claims (it's technically true - a court didn't order it, but a guy who goes by the name "That One Privacy Guy" while blogging on linkedin did).

  • WordPress.org's login page demands you pledge loyalty to pineapple pizza

    Jump
  • That "underdog" you're talking about is owned by the 11th largest private equity firm in the world, and they really don't contribute much to the free software project Matt runs which their entire business is built on.

    Matt is certainly screwing up with his handling of the dispute, and it's sad to see because i think his commitment to free software ideals has generally been a benefit to society over the last two decades.

    From where I'm sitting (i've spent at least a couple hours reading about the dispute over the last few months) he's actually not wrong about the trademark thing. And he's also not wrong about pineapple on pizza 😂 ... but putting either on the login page is not a good look. 😢