Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
pfraze
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
15 ms
·
241.
▲
by
pfraze
2y ago
Servers are holding up so far. Somewhere been 800k-1mm signups (need to check backend). Fortunately we were overprovisioned. If we hit 4mm new signups then things should get interesting. edit: we did have some degradations (user handles ent
242.
▲
by
pfraze
2y ago
Same logic as a search engine might apply to the Web - some kind of crawling rules. That said, the network tends to use Relay services to optimize it. The Relays are essentially dumb caches that provide a firehose from multiple servers. We
243.
▲
by
pfraze
2y ago
Yeah actually I agree about this, we should update it
244.
▲
by
pfraze
2y ago
Not sure why you say that. The Biden admin pursued a number of cases and recently got a monopoly ruling on Google
245.
▲
by
pfraze
2y ago
Does wasm provide synchronous access through the perimeter?
246.
▲
by
pfraze
2y ago
As stroustrup said, “There are only two kinds of languages: the ones people complain about and the ones nobody uses.” There are many better languages than JS, and the browser ecosystem has shut down innovation in PLs, but there are some pre
247.
▲
by
pfraze
2y ago
My team is kind of a miniature qntm fan club. We include copies of antimemetics as a new employee gift.
248.
▲
by
pfraze
2y ago
To give some context, this discussion is maintained by one of our team, and is way to help us communicate future changes and known blehs in the protocol.
249.
▲
by
pfraze
2y ago
It’s a little bit different.
250.
▲
by
pfraze
2y ago
You can visit the Internet Archive in SF. It’s worth it. They use an old church
251.
▲
by
pfraze
2y ago
We couldn’t handle the server load and had to build a T&S team. The invites were the only thing that stopped us from collapsing.
252.
▲
by
pfraze
2y ago
Products take time to build; protocol takes a lot of time. That we were able to productionize in about 4 months — having previously been a team of 4 working on the protocol for 10 months — and not collapse under the load is a pretty decent.
253.
▲
by
pfraze
3y ago
that's still how it works, we just shard our users across multiple hosts
254.
▲
by
pfraze
3y ago
I'm pretty curious to see more as well, though FYI at first glance this looks like it's using DIDs
255.
▲
by
pfraze
3y ago
I’m guessing the issue is devs putting business logic constraints in the client and not duplicating them in the server
256.
▲
by
pfraze
3y ago
That's how you'd build a subreddit-like experience on Bluesky, yep. Something we're looking at right now is bundling all these lego pieces to make that a bit more convenient to do.
257.
▲
by
pfraze
3y ago
Custom labels are in the v1 yes.
258.
▲
by
pfraze
3y ago
There aren’t a lot of exact matches that I’m aware of. Spam filters, ad blockers, Reddit, mastodon, and block party all came up during the discussions.
259.
▲
by
pfraze
3y ago
You have to first distinguish between infra moderation and app moderation. Infra is the aggregation layer (the relay and appview). App is the application client. The application client sets its labelers and filters entirely client side. Our
260.
▲
by
pfraze
3y ago
It’s driven by the PDSes and will be moving to this OAuth system soon: https://github.com/bluesky-social/proposals/blob/main/0004-o...
261.
▲
by
pfraze
3y ago
I’m a huge nerd about this so I enjoy this question. The logic of the system is that the protocol offers users rights by architecture. They include rights to an identity, to speak, and to choose your providers. The right to control reach is
262.
▲
by
pfraze
3y ago
We'll let you know when we figure out why we're doing it.
263.
▲
by
pfraze
3y ago
Are people confused by why we mean by moderation? Did we lie and call it "speech amplification?" I should think people would be significantly more confused if we began talking about our robust solution to censorship, because by co
264.
▲
by
pfraze
3y ago
It might be worth trying, but essentially what you're trying to do is cost/load sharing on the aggregation system. You could do that by computing indexes and sharing them around, to reduce some amount of required compute, and I su
265.
▲
by
pfraze
3y ago
> I think what might be needed here is that anyone with enough resources can run their own relay, and PDSes can subscribe to multiple relays and deduplicate certain things. That is how it's designed, yes!
266.
▲
by
pfraze
3y ago
I’m unsure how it will play out in practice. I think it’s possible that different infra could wind up being deployed in jurisdictions that differ too significantly. Certainly that could happen outside of Bluesky. Bluesky itself is US-based.
267.
▲
by
pfraze
3y ago
The network can be reduced to three primary roles: data servers, the aggregation infrastructure, and the application clients. Anybody can operate any of these, but generally the aggregation infra is high scale (and therefore expensive). So
268.
▲
by
pfraze
3y ago
I assume a foaf expansion of the block graph
269.
▲
by
pfraze
3y ago
This was a very active topic of debate within the team. We ended up establishing the idea of "jurisdictions" to talk about it. If a moderation decision is universal to all viewers, we'd say that it's under a specific j
270.
▲
by
pfraze
3y ago
No, other clients -- including forks of our open source client -- can opt out of our censorship (if we're really going to call it that). I mention infrastructure takedowns in my other comment. If we ever cross the line on that layer, y
More ›