Even without privacy in the protocol it could be done in user space https://guide.fission.codes/developers/webnative/file-system-wnfs

But there may or may not be an "official" way to do private data.

I believe that ATP is by far the most promising compared to other competing standards. For a decentralized social network to 'work', i.e. provide acceptable user experience, the user has to be able to: 1) have their feed adequately moderated and curated, 2) easily migrate their identity in case their service provider goes down, 3) easily reach their target audience, 4) easily discover contents of their interest.

ActivityPub for example 1) relies too much on individual instance admins on moderation; 2) does not provide a straightforward way to migrate their data; 3) does not provide a way to easily expand the 'known network'; and 4) does not provide a way to easily discover remote activities.

ATP on the other hand 1) provides a standardized way for algorithmic moderation; 2) provides a way to migrate a user's entire data using DIDs; 3, 4) has a 'big-world' network outlined in the protocol for discoverability and reachability (while I'm not sure as to how much of this 'big-world' has been implemented).

Joanna I think you'll find that there is a segment of people for whom labels like "web3", "next internet" mean nothing, and do very little to actually explain what a project does, and in some cases even harm a project that might actually try to differentiate itself from every other using the same label.

For me for example the term "web3" is now burnt. Skiff for example is an amazing project, but their heavy rebranding towards web3 has put me off the whole project as it now feels like a cash grab, or just trying to ride the hype wave, and make money from people betting big into whatever web3 is.

I don't have a lot to say about Nostr, never used it.

Rewriting Matrix towards a social network would be difficult, but social network is not Matrix' job and Matrix does its job really well. Account migration seems tough, but it seems like there's been some progress.

I’m not familiar with ATP but i hope its design and success is not dependent on blockchain. I’ve seen exactly 0 blockchain projects with intrinsic value.

Does ATP decentralize the cost of running a social network? If you think I should read about the protocol before asking these questions, please feel free to tell me so. Thank you for answering my questions.

Hello friends!
Got one simple question regarding the identity. Does Bluesky allow to use IP addresses instead of domain names?

https://atproto.com/guides/identity#identifiers

The DNS handle is a user-facing identifier — it should be shown in UIs and promoted as a way to find users.

What if i use at://123.5.6.12 instead of at://

We've actually considered dropping IP address support for these reasons: it provides little to no value.

does it mean currently Bluesky does not allow that?

And a pds is able to declare its handle suffix independently of its location on the web

didn't get the idea.
or you mean - by using DNS ? :-)

so it works like this?

1. DNS lookup:
   alice.host.com
   -> IP
2. Call 'com.atproto.handle' on IP -> DID
3. Download DID -> DID Document from the centralized Bluesky DID server (in case of did:plc!!!)
4. Call 'com.atproto.sync.getRepo' on DID.repo

Same guy (Firefox CTO :-)) asked here https://educatedguesswork.org/posts/atproto-firstlook/:

A new DID form called DID placeholder (did:plc)), which consists of a hash of a public key which can then be used directly or sign new public keys to allow rollover (see my long post for more on this topic). As an aside, it's not clear to me how you actually obtain the DID document associated with a did:plc DID, as the public key isn't sufficient to retrieve it. There's apparently a PLC server, but is there only one? If not, how do you find the right one? This all seems unclear.

1. patched must be signed by a key the is already in the DID Document. The directory can't make up a diff only veto or reorder them.
2. once a patch is accepted into the ordered list of accepted patch if the directory forgets one the nodes that retrieved previously have proof the directory changed history.
3. If the directory ever gave divergent histories and the two PDS talk to each other they can prove that the directory is duplicitous

yes, agree

the difference is in other dimension - "compatibility" and "ease of use"

POA pros over some RAFT cluster:

• you can easily migrate POA into something like POS or even use some external well-established network like Polygon/Optimism -> more compatible with pure "crypto" tech
• there is a notion of "tokens" and "gas" right out of the box -> so anti-Sybil mechanism out of the box
• clients can launch light-nodes that will replicate the state, but not do a consensus -> better anti-censorship

you will have to build all of that manually in case of RAFT
am i right?

123456execute("""
SELECT operation
FROM operations
WHERE did = ?
ORDER BY createdAt ASC
""", did)

https://github.com/bluesky-social/atproto/blob/75e14ae102d9ac5e2c3a47aa2341d8cb7e854397/packages/plc/src/server/db.ts#L163-L170

That's basicly all we ask the directory to do.

that would be great! i would attend a call if that's possible

I'm mostly into the ActivityPub, Subconscious Noosphere, SSB, etc
also, very interested in the identity + blockchain (DIDs etc) topic

https://github.com/bluesky-social/atproto/issues

but that is very zoomed in.
Hard to have a public longer term plan as plans tent to change

This is very exciting: https://apps.apple.com/us/app/bluesky-social/id6444370199

but, internal server error

1234$ lerna run build
$ cd packages/pds
$ node dist/bin.js
ATP Data server is running at https://localhost:2583

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263[
  {
    "level": 20,
    "time": 1676893811836,
    "pid": 1,
    "hostname": "xxx",
    "name": "pds:db",
    "handle": "syui.localhost",
    "email": "syui@syui.cf",
    "msg": "registering user"
  },
  {
    "level": 30,
    "time": 1676893811949,
    "pid": 1,
    "hostname": "xxx",
    "name": "pds:db",
    "handle": "syui.localhost",
    "email": "syui@syui.cf",
    "did": "did:plc:xxx",
    "msg": "registered user"
  },
  {
    "level": 50,
    "time": 1676893811993,
    "pid": 1,
    "hostname": "xxx",
    "name": "pds",
    "req": {
      "id": 2,
      "method": "POST",
      "url": "/xrpc/com.atproto.account.create",
      "query": {},
      "params": {},
      "headers": {
        "accept": "*/*",
        "content-type": "application/json",
        "accept-encoding": "gzip, deflate, br",
        "user-agent": "Darwin",
        "content-length": "0",
        "accept-language": "ja",
        "x-request-start": "t=1676893811814520",
        "host": "localhost",
        "fly-client-ip": "127.0.0.1",
        "x-forwarded-for": "127.0.0.1",
        "fly-forwarded-proto": "https",
        "x-forwarded-proto": "https",
        "fly-forwarded-ssl": "on",
        "x-forwarded-ssl": "on",
        "fly-forwarded-port": "443",
        "x-forwarded-port": "443",
        "fly-region": "nrt",
        "fly-request-id": "00",
        "via": "bluesky.io",
        "fly-traceparent": "00",
        "fly-tracestate": ""
      }
    },
    "didKey": "did:key:xxx",
    "handle": "syui.localhost",
    "msg": "failed to create did:plc"
  }
]

This is the dockerfile I have been using:

123456789101112131415161718FROM node:18-alpine
RUN apk update
RUN apk add git

WORKDIR /app

RUN git clone https://github.com/bluesky-social/atproto/
WORKDIR atproto

RUN yarn install --frozen-lockfile
RUN yarn build

WORKDIR packages/dev-env
ENTRYPOINT ["yarn", "run", "start"]

EXPOSE 2582
EXPOSE 2583

I'm getting an error like this, does it currently only work on supported domains?

1234567891011121314$ cd packages/dev-env
$ yarn run start
/app/packages/dev-env/dist/cli.js:91476
        throw new XRPCError(resCode, res.body.error, res.body.message);
              ^
XRPCError: Not a supported handle domain
    at ServiceClient.call (/app/packages/dev-env/dist/cli.js:91476:15)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async generateMockSetup (/app/packages/dev-env/dist/cli.js:123766:17)
    at async start (/app/packages/dev-env/dist/cli.js:123976:3) {
  status: 400,
  error: 'UnsupportedDomain',
  success: false
}

The one i posted has about ten uses, the 4pry4 one probably only has one or two left

yes

oh no...... I didn't realize this was the invite code......

I'll be waiting for someone to drop another invite code on a whim.

I can't get through this, can you help me ?
url=https://$host/xrpc/com.atproto.repo.createRecord

json='{
"did": "did:plc:uqzpqmrjnptsxezjx4xuh2mn",
"collection": "

curl -X POST -H "Content-Type: application/json" -H "Authorization: Bearer $token" -d "$json" $url

https://docs.mau.fi/gomuks/commands.html

/quit seems to be the answer.

I think that's true, only iOS rn.

whyrusleeping is there a public API for the bluesky PDS that you can use to pull down posts?