Josh Shaked

Josh Shaked

@jshaked.com

Investing in the open web

301 followers412 following77 posts

WOW, this is unbelievably cool! @awarm.space will these mentions/embeds live on protocol (i.e. when I mention a semble collection on a given leaflet, there is a strong connection between that semble collection and that leaflet post that lives on protocol)?

jared@awarm.space

In theory, anything can be published as a loose document under the standard.site.document lexicon - a twitter post, a youtube video, an amazon review. Excited to see further explore extending standard.site beyond long-form content, even though that's not what it was meant for :)

I built a TwitLonger for Bluesky. Write as much as you want, it saves to your repo as a Standard.site document record, then posts a teaser to your feed with a link back. Read more about it on https://unthread.at/@aka.dad/3mg5ejw7eil23

Josh Shaked reposted

atproto is so funny. Leading protocol explorer in the previous ecosystem I worked in: Etherscan, a 70-person company with ~$35,000,000 in yearly revenue Leading protocol explorer in the ecosystem I work in now: @pdsls.dev by @juli.ee, it's great

This post is unavailable.

the first building block of an atproto-based social browser

Sri@sri.xyz

@atpi.at is live. A tiny set of tools and integrations to resolve AT Protocol URLs and preview atproto JSON data! - Direct URL prefixing (atpi.at//...) - npm pkg - Chrome Extension - VS Code Extension and... some fun ones! Check out: docs.atpi.at It’s not just an API. It’s ATPI. GET it?

This! There is a clear conflict of interest running an app view and a PDS. In the future, I expect PDS hosts to run independent of major app views

Eurosky Sebastian@sebastian.eurosky.social

Limiting your PDS to your app‘s lexicon defeats the entire purpose of #atproto. I hope Eurosky‘s CoCoMo can be part of „a“ solution. Would love to hear from @bnewbold.net and @pfrazee.com what their take is on this.

As atproto apps increasingly choose to verticalize PDS hosting, we need to be weary of user identity/data fragmentation across apps (ironically one of the key problems that atproto/bluesky was designed to solve)

Interesting to see another atproto app vertically integrate PDS

Tangled@tangled.org

💫 tangled is now hosting its own PDS! head to tangled.sh/signup to get a new account. 🇪🇺 just like the rest of our infrastructure, everything is EU based, right out of beautiful Helsinki 🇫🇮 2/5

Josh Shaked reposted

bsky should really emphasize the best part of atproto: the PDS. investors should fund startups selling PDSs, both as a cloud service and a physical self host device. make it clear to users that the biggest benefit of atproto isn’t “one account for all platforms”, it’s “choice in sharing data online”

One step closer to building a general-purpose atproto client

bryan newbold@bnewbold.net

messing around with a lexicon web catalog: lexidex.bsky.dev consumes from the firehose, or can load from local disk. not very hardened or complete yet

One of the most powerful features of crypto/blockchain systems is the separation of user data from application presentation. I can take my identity and token balances with me across apps. Atproto will do the same for the web, taking us from enshittification --> cryptification.

With atproto, we can go from monetizing the screen real estate users see (i.e. clients) to monetizing data itself. I believe this subtle difference will lead to a more open and innovative web where data exists and is useful independent of the client it was created in.

You are up to date.