cam

thanks! I haven't tried using claude for it yet, I wasn't sure how much code would be out there for it to have learned from. and will go through that track

loving the Gleam libraries! Did you have any resources you found especially helpful for learning gleam?

and, to play devil's advocate, might not have the annual carbon footprint of a medium sized country

Im saying that by defining dislikes as public that setting would be the behavior for everyone.

A block is on an account. A dislike is on a piece of content. with a public dislike am creating a backlink to content I specifically do not endorse

Let’s say I dont want to see graphic content on my feed. Public dislikes, by definition, associate my account with the graphic content I don’t want to see.

But by making dislikes public on the protocol, you are making that decision for everyone, not just yourself

I can see how this would expose people to harassment though. easy to imagine the first bot that will be built will be “posts disliked by bluesky team members.” So now that prevents them from tailoring their own feeds for fear of backlash

Im gonna disagree here, I think dislikes are inherently a bit more personal than likes and my intuition is they should be private by default. It reduces the ability of people to personalize their feeds as they desire if the personalization mechanism is open to the public and its scrutiny

Maybe it does or doesn't. But the fact that anyone can hop onto Sora and generate these videos and post them on the internet makes the issue susceptible to virality in a way that increases the likelihood of the average person being exposed to false information by orders of magnitude

I am not being facetious, I am having trouble grasping how this tech, if not regulated, will impact society without being ruinous. How can we function as a democracy if we corporations are allowed to beam falsehoods they generate and/or incentivize directly into the retinas of voters?

Those examples are literally libelous if done with malicious intent, yes. Andrew Cuomo is airing advertisements that contain AI-generated footage of Zohran Mamdani saying things he didn't say. What happens if Larry Ellison buys TikTok and allows that kind of thing to run rampant? It's poisonous, no?

There must be some sort of recourse for how to deal with AI-generated videos that impersonate another person and make it look like they said something they never said though, right? Or use their likeness for other nefarious purposes?

the more specific subs can be ok. I have found r/golang to be reasonable. it's the sweet spot of size and moderation. in general the quality of most subreddits have declined greatly over the past ~5 years to the point where it's not worth it

This is excellent, thank you for sharing

I do feel like there is a frontloading of these types of decisions architecturally when building an atproto app that I’m struggling with

Since its just a redirect you can remove the @ for go

Remove @ in tangled URLs #245 Currently something like https://tangled.org/xan.lol/xan.lol redirects to https://tangled.org/@xan.lol/xan.lol, when it might make more sense for that to be the other way around! Some reasons: 1. it d...

Theyre probably going to remove it tangled.org/@tangled.org...

But I would love to know if this is not idiomatic atproto

The way I have been thinking about it is to have an API endpoint for the client to notify to pull from the PDS, so push instead of pull, to reduce latency and also prevent clogging up the PDS with e.g. individual chess moves. So the only record would be the final scoreboard which shows a game log

Im working on similar turn based games. I guess a key question is what is the latency of the firehose/jetstream

Ive been thinking about this too. Noob question, is it definitely better to listen to the firehose/jetstream than to plug directly into the user’s PDS?

I love overleaf for latex. Have never used it for collaboration though. Are you thinking like Google Docs type collaboration?

My prompt is not as cool though

Yeah, I'm getting the same.

I still think in the situation he described Bluesky has a copy of your semiprivate data e.g. bookmarks in order to serve those xrpc endpoints from the appview. Regardless of oauth. But I could be missing something.

(Yet; paul outlines how it could be done in the linked article)

Well, assuming you trust your appview provider. Bluesky employees have access to your bookmarks. That is one level of private.

But also, that data is not “personal” in that its not in your PDS and so you cannot port it over should you leave the bluesky appview

well, that's good to hear it's mostly not a concern. i was worried about this writing my app. will report back with more experience under the belt!

sure. that is an option. it will make all the other appviews sad, though. maybe this is a JS/TS vs Go/Clojure style backwards compatibility discussion. In Go it's really frowned upon to making breaking changes after a certain level of adoption