Right now the only PDS is the bsky one which most likely doesn't support random schemas as it's designed as a micro blogging service.
That doesn't mean people won't be spinning up PDSes that are general purpose in the future. Think of it like dropbox.
You register, pay for storage, and you can hold any schemas you want.

The main issue right now with this ^ is that right now from what I understand the server implementation is both a PDS as-well-as a bsky-server that is needed for the client to work. I think that these will eventually need to be decoupled to two distinct servers/services for what we're discussing to work nicely.

RE: placeholder did https://github.com/bluesky-social/did-method-plc

The DID itself is derived from the sha256 hash of the first operation in the log. It is then base32 encoded and truncated to 24 chars.

According to my calculations, it is computationally feasible (on the order of "a few thousand dollars") to generate a hash collision of this truncated length. i.e. to generate a pair of new identities with the same ID string - but not to match with a chosen existing ID (aka a preimage attack). I don't yet have a very solid understanding of the rest of the protocol, so I'm asking here, would there be any security implications of generating such a collision?

yeah, it's something like

12345678910{
    type: 'create',
    signingKey: 'did:key:zDnaejYFhgFiVF89LhJ4UipACLKuqo6PteZf8eKDVKeExXUPk',
    recoveryKey: 'did:key:zDnaeSezF2TgCD71b5DiiFyhHQwKAfsBVqTTHRMvP597Z5Ztn',
    username: 'alice.example.com',
    service: 'https://example.com',
    prev: null,
    sig: 'vi6JAl5W4FfyViD5_BKL9p0rbI3MxTWuh0g_egTFAjtf7gwoSfSe1O3qMOEUPX6QH3H0Q9M4y7gOLGblWkEwfQ'
  }
``` (from the docs)

<

@alrozzi:matrix.org

> Anyone got an invite for me?

This is a developer room, please don't ask for invite codes here

Verifiable Credentials would be interesting to add to the mix

https://www.w3.org/TR/vc-data-model-2.0/

You can run a pds, but the uses on that pds will one see each other and their posts.

Your users can use the official bsky app to connect to your pds.

Once federation is done and deployed your pds should also be able to communicate with the bsky and other ones as well.

The pds server is available on the gothub repo.

then what you're asking is for providers to become the root of trust/source of truth, at that point you don't need bluesky or anything else, facebook and twitter do this just fine. it's essentially antithetical to everything being built here

clients utilising a registry or parsing verified credentials from the protocol for the purpose of indicating authenticity is merely an abstraction to streamline general UX.

users won't and don't have to depend on their providers as they can self-certify and verify these same facts at the protocol level independently.

@ifeeltiredboss:matrix.org

🤔

I would hope the immutable legger moves to something more decentralized before 100 years.

Yeah now the legger is

atomdmac: "

jack doesn’t have unilateral power. he has 1/3 influence on the board. i’m the CEO...i have the most control over this endeavor, and i’m grateful for everyone who’s trusted me with it." https://blue.amazingca.dev/?username=jay.bsky.team&postid=3ju6gsfeyda2j

Nostr has individual notes as it's core objects where atproto has repositories. The relays are not tied to any particular publisher in the way that the PDS is expected to have all the content a DID published.

I generally think about the difference as a best effort distribution vs a completeness distribution.

Should this page include?

"
Company Name: BLUESKY, PBLLC,
File Number: 6282898,
Filing State: Delaware (DE),
Filing Date: October 4, 2021
"

from

def generate_code():
return ''.join(random.choices(string.ascii_lowercase + string.digits, k=7))

driver =

driver.get("https://staging.bsky.app")
time.sleep(3)

wait = WebDriverWait(driver, 10)
wait.until(EC.presence_of_element_located((By.XPATH, "//div[@data-testid='createAccountButton']")))

create_account_button = driver.find_element(By.XPATH, "//div[@data-testid='createAccountButton']")
create_account_

bluesky = driver.find_element(By.XPATH, "//div[contains(text(),'Bluesky')]")

next_button = driver.find_element(By.XPATH, '//div[@data-testid="nextBtn"]')
next_

invite_code_input = wait.until(EC.presence_of_element_located((By.CSS_SELECTOR, "input[data-testid='inviteCodeInput']")))

email_input = driver.find_element(By.CSS_SELECTOR, "[data-testid='emailInput']")
password_input = driver.find_element(By.CSS_SELECTOR, "[data-testid='passwordInput']")
legal_check = driver.find_element(By.CSS_SELECTOR, ".css-175oi2r")
next_button = driver.find_element(By.XPATH, "//div[contains(text(),'Next') and contains(@class, 'css-1rynq56')]")

next_

wait.until(EC.presence_of_element_located((By.XPATH, "//input[@data-testid='phoneNumberInput']")))

while True:
invite_code = "bsky-social-" + generate_code()
ActionChains(driver).move_to_element(invite_code_input).click().perform()

1234567891011121314151617181920212223242526272829303132invite_code_input.send_keys(invite_code)

email_input = wait.until(EC.element_to_be_clickable((By.CSS_SELECTOR, "[data-testid='emailInput']")))
email_input.send_keys("exemple@domain.com")

password_input = driver.find_element(By.CSS_SELECTOR, "[data-testid='passwordInput']")
password_input.send_keys("password")

legal_check.click()
time.sleep(3)

next_button.click()
time.sleep(3)
try:
    wait.until(EC.presence_of_element_located((By.XPATH, "//div[@data-testid='someElementOnNextPage']")))
    next_button = driver.find_element(By.XPATH, "//div[contains(text(),'Next') and contains(@class, 'css-1rynq56')]")
    next_button.click()
    time.sleep(1)
except:
    pass

error_messages = driver.find_elements(By.XPATH, "//div[contains(text(),'Invite code not accepted.')]")

if not error_messages:
    print("Invite code accepted:", invite_code)
    break

invite_code_input.clear()
email_input.clear()
password_input.clear()
legal_check.click()
time.sleep(1)