bluesky

The at will henceforth be atproto.

bluesky is positioned as a model service for atproto, which is currently being developed and operated by bsky.team.

The goal of bsky.team is to enable atproto to be adopted behind the scenes of various services and to allow communication between services.

Until now, accounts were only valid within a service. Therefore, it was necessary to switch accounts for each service. This is an attempt to change this.

bluesky will work with pds, plc, and bgs.

To describe the role of each, pds is the main body of bluesky.

plc is like dns and registers handle and did, and performs name resolution.

Basically, bluesky works only with pds.

However, when an account is created, it connects to plc, so if there is no connection to plc, an error will occur.

plc is not necessarily needed when an account is created; it is needed when a handle is registered or changed.

bgs builds the timeline of the account when connecting to other pds.

graph TD; A[pds]-->B[plc]; C[pds]-->B[plc]; D[pds]-->B[plc];
graph TD; A[pds]-->B[bgs]; C[pds]-->B[bgs]; D[pds]-->B[bgs];

dns

What is a dns above is a server that performs name resolution on the Internet.

You connect to the internet by the number ip address.

For example, to connect to google, it is 172.217.25.174.

$ dig google.com
google.com.             291     IN      A       172.217.25.174

Try this number in your browser to see if it works. It should lead to google.com.

However, since numbers are difficult for humans to remember and handle, they are usually given names that are replaced by letters of the alphabet.

The server responsible for connecting the name to the number ip address is called dns.

The following is a command that displays the route to the desired host. You can see that it is connected via several servers.

$ traceroute google.com
20.27.177.113
17.253.144.10
172.217.25.174

If you want to know your ip address, you can use ipinfo.io.

$ curl -sL ipinfo.io
20.27.177.113

plc

These are the most commonly used plc's at this time. All are provided by bsky.team.

https://plc.directory

https://plc.bsky-sandbox.dev

Specifically, it is used as follows

https://plc.directory/export

https://plc.directory/export?after=1970-01-01T00:00:00.000Z

https://plc.directory/did:plc:oc6vwdlmk2kqyida5i74d3p5

https://plc.directory/did:plc:oc6vwdlmk2kqyida5i74d3p5/log

.env

#DID_PLC_URL=https://plc.directory
DID_PLC_URL=https://plc.bsky-sandbox.dev

bast service

Since both api and pds are publicly available for bluesky, various services are being developed.

The following is a list of representative services.

https://firesky.tv : Global Timeline Stream. You can configure and filter it in many ways.

https://bsky.jazco.dev : User Visualization

https://bsky.jazco.dev/stats : Number of user posts

https://vqv.app : User profile aggregation, etc.

https://atscan.net : Scanning of pds and did

https://skybridge.fly.dev : url to do bluesky in mastodon client

https://tapbots.com/ivory : Support for mastodon client ivory

https://skyfeed.app : Generation of feeds

results matching ""

    No results matching ""