bnewbold

6 ms·

1.
by bnewbold 5mo ago
Where are you getting the 200 megawatt number from? The document you linked says that a large auto assembly plant consumes around 188,000 MWh annually (with regional variation). By my quick math that is less than 22 megawatts baseline load
2.
by bnewbold 8mo ago
Thanks for the response Nora. Because of your blog post I went through the process of setting up a did:web account myself this afternoon, and it was painful. Eg, I found a bug in our Go SDK causing that "deactivated" error ( https
3.
by bnewbold 8mo ago
fair enough, the did:web flows are not documented even for technical atproto developers, and there needs to be a self-serve way to heal identity/account problems elsewhere in the network (the "burn" problem). I do think that
4.
by bnewbold 1y ago
(I added a reply up-thread here: https://news.ycombinator.com/item?id=45469667 )
5.
by bnewbold 1y ago
DNS poisoning is a concern in some situations, but not always. The common case with at:// strings is to put in the DID in the "authority" slot, not the handle. In that case, whether resolving a did:plc or did:web, there
6.
by bnewbold 1y ago
"A Full-Network Relay for $34/month" https://whtwnd.com/bnewbold.net/3lo7a2a4qxg2l
7.
by bnewbold 1y ago
This one has been popular recently: https://bsky.app/profile/spacecowboy17.bsky.social/feed/for-... (there are several feeds named "For You"; IIUC this started a couple weeks ago and is based on &qu
8.
by bnewbold 1y ago
Yes, all of those social graph relationships are hinged off a permanent identifier (DID) and everything comes along when accounts migrate PDS instances. Folks can use zeppelin.social from any PDS instance. The DID PLC directory is currently
9.
by bnewbold 1y ago
If you want a service which indexes every post in the public network, including from folks you don't follow, that is just going to require resources. I think $200/month for a full-network index (as zepplin does) is very reasonable
10.
by bnewbold 1y ago
hundreds (thousands?) of users have signed up for Bluesky Social, then moved their accounts to independent hosts. folks can use https://zeppelin.social/ as a totally free-standing bluesky posting experience that interoperat
11.
by bnewbold 1y ago
I agree with the general sentiment here, but don't like the examples. 200 photos per person per year isn't very much! That is all fine. What really bloats things out is surveillance (video and online behavioral) and logging/t
12.
by bnewbold 3y ago
SeaweedFS does the thing: I've used it to store billions of medium-sized XML documents, image thumbnails, PDF files, etc. It fills the gap between "databases" (broadly defined; maybe you can do few-tens-KByte docs but stretch
13.
Why Not RDF in the at Protocol?(pfrazee.com)
4 points by bnewbold 3y ago|0 comments
14.
by bnewbold 3y ago
This is exactly the problem that the Internet Archive created their Scholar project to mitigate ( https://scholar.archive.org/about ). The https://fatcat.wiki component acts as a dashboard to track preservation of
15.
by bnewbold 3y ago
not as satisfying as a friend's "<name> at at dot dot see see"
16.
by bnewbold 3y ago
This tool is so great for robustly dealing with content in old and poorly formatted HTML. There are a lot of similar tools for extracting "the main text" from free-form HTML, but this was the most reliable in my experience, especi
17.
by bnewbold 3y ago
all public account content is in a "repo", commits to the repo are signed, and the identity resolution mechanism gives anybody the current/active signing key. the most direct analogy is to signed git commits. this is an inten
18.
by bnewbold 3y ago
some quick thoughts/notes (I am on the bluesky team, but this isn't an official policy statement): - content on bluesky is public, but we have not set expectations/comms around that well yet, and this dump may be a surprise
19.
by bnewbold 3y ago
dropped domains will be a bit of a UX problem. the human root of identity is the handle (memorable/recognizable), but the real identity root for the account is a DID. which is a pretty open/wild spec, so we mostly use did:plc (&qu
20.
by bnewbold 3y ago
You can point your web browser to https://staging.bsky.app The team is too small to develop and maintain even an electron desktop app or something like that wrapping the existing react-native-web SPA. But this leaves space for f
21.
by bnewbold 3y ago
I don't really understand your question. Maybe it helps to clarify that the concept of a handle is totally distinct from the "Personal Data Server" or PDS. You look up the PDS for a handle by resolving the DID first (via DNS
22.
by bnewbold 3y ago
atproto handle resolution tries DNS TXT first, then will try an HTTP endpoint. the endpoint is not a ".well-known", it is an "/xrpc/"-prefixed endpoint with a query parameter, which is workable on some static h
23.
by bnewbold 4y ago
As a small nit, André Staltz is not directly affiliated with Bluesky. Paul and a couple other folks on the team have a track record with similar open projects.
24.
by bnewbold 4y ago
No, the Bluesky app does not ask for your contacts. Somebody else could build an app for Bluesky that did ask, the same as somebody could in theory build an RSS feed reader that asks for contacts.
25.
by bnewbold 4y ago
The content in scholar.archive.org has been indexed in to Google Scholar (and other indices are likewise welcome to crawl the sitemap). There was some content "only" in scholar.archive.org, but now it should basically all be in Go
26.
by bnewbold 4y ago
This seems like a good contribution. It would great if one of these "lists of blessed crates" itself becomes blessed and sticks around! This list seems like it was created by somebody with "good taste", and I enjoy the a
27.
by bnewbold 4y ago
I'm really curious to see if efforts like this, and from computational augmentation and automation more generally, will yield progress on symbolic modeling of large natural systems. There is a segment in Adam Curtis's "All Wa
28.
by bnewbold 4y ago
It is true that some might need to be done manually, but Google Scholar shows that it can be done, with some level of accuracy, via HTML and PDF scraping. PIDs and more formalized metadata make things much easier. But Google Scholar did res
29.
by bnewbold 4y ago
Unpaywall is based on Crossref DOIs (one-to-one records), and adds information about publicly accessible versions of each work. In theory publishers can register metadata about whether articles are OA or not with Crossref, but the quality a
30.
by bnewbold 4y ago
Hi, i'm the maintainer of scholar.archive.org. It looks like we are missing a bunch of your public papers, such as those published here: http://park.itc.u-tokyo.ac.jp/eigo/publication_en.html Both unpaywall and sc

More ›