Nobody asked me but I think it would make a lot of sense if every website used invite codes forever because that way if 30,000 spammers all got invite codes from the same person you'd know that person's invite codes shouldn't be trusted

When I started dating Christine, we did a sort of a… movie battle? We showed each other our favorite hacker movies, to see if we could convince each other our fave was better. I showed her "Sneakers". She thought it was basically okay. She showed me "Hackers". I thought it was amazing. I think she won the exchange

https://infosec.exchange/@paulasadoorian/115209872796642845

@fontenot @aeva @cthos One of the expected features of an AppView is full text search. This is a primary product differentiator versus Mastodon and users will be surprised if it is absent.

@KnightMustard No. I am saying a different group of people got harassed, a few years back, and I saw people leave the Fediverse as a result. My perception, which obviously is the perception of an outsider and so not trustworthy, is that black Fedi is smaller now than it used to be.

Rudy says he's never used Fedi.

@KnightMustard "What lead to it failing here?"

What lead to what failing?

@boris "Bsky doesn’t have auth on your account and can’t delete individual posts."

This is true in my case because I self host a PDS. Most users use a Bluesky PBC hosted PDS. In this case, Bluesky owns everything, they have the keys, the bits are resident on their servers. What prevents them from deleting a post? Aren't they legally bound to delete posts in case of DMCA takedown, CSAM, etc?

@jdp23 Blacksky is not only hosting a Bluesky alternative, they are *coding* a Bluesky alternative (in Rust, where Bluesky prefers a combination of TypeScript and Go). I assume(?) the combination of Rudy's statements should be interpreted to mean that the self-authored AppView is not ready yet, so he is hosting a PDS he wrote, hosting a relay he wrote, hosting Bluesky's appview and client on top of that, and he intends to replace Bluesky's appview soon. I assume.

Update: Rudy who operates blacksky.community responded to this thread on bluesky. Above I said I wasn't clear on how independent Blacksky was of the Bluesky infra. His answer is "completely". They run their own relay (which scrapes PDSes itself), the relay feeds into their own appview, the appview feeds into their own client. https://bsky.app/profile/rude1.blacksky.team/post/3lyv5rwpc722c

And since they bridge end-to-end, in my Hypothetical Example above, they *could* choose to make different moderation decisions from Bluesky PBC.

@jdp23 Rudy says they're appview and also client. https://bsky.app/profile/rude1.blacksky.team/post/3lyvbqh3m3s2e

@boris "(would also break verification of a repo and is detectable)"

What happens if I delete a post from a repo? If it can't be removed can someone then query the post from my PDS direct and get a copy of the deleted content?

@fleeky As an update, I searched on blacksky.community for "from:me blackbird" and found a post from 2024. So they have some source of older posts.

@boris "Content doesn’t get removed from the PDS it would be hidden by labels - accounts do have takedown labels applied." I could be wrong but this seems to be contradicted by actual events over the last two weeks.

"Bluesky operated relay doesn’t censor Lexicons that don’t validate" Contradicted by my own testing. Either the relay censors them or the appview does and it comes to the same thing, because when I make 301-character posts even third party tools can't see them.

@thisismissem @mat @eniko Okay, yes, that's more accurate.

@tylercook Yes, correct. If you already have a setup for hosting Docker containers standing up the PDS is *trivial*. Like, you could do it in under an hour. I don't pay per byte of bandwidth (VPS) but the load from running my PDS has been so low I don't notice it. And if it turns out to be a problem you can migrate out to another PDS.

I'm going to DM you a link to a Discord I found helpful when debugging issues with my PDS.

@mat @thisismissem @eniko The continuous event streams are HTTP. Mine are being proxied through Apache

@mat @eniko Isn't it convenient that Bluesky has architected an "open" system where the solution to every problem turns out to be "use Bluesky", and any other solution requires fighting incredible gravity?

@mat @eniko Now, that last thing is possible, and even easy. But at that point it's really, super unclear *why* you would architect your Wordpress server to *be* a PDS, rather than running the regular PDS software on the same box, and having the Wordpress server post to it from time to time using the external API. It's extra work, but there's no obvious advantage and there's barely even a difference.

@mat @eniko "but where are replies to those posts coming from in this setup?"

Short version: "You can't get them"

Long version: Currently the only ways to get replies to a post published in your Bluesky PDS are

- Run a "relay". This means (this is not a joke) receiving from Bluesky PBC a copy of literally every post made in the network, and filtering for ones that @ you.

- Log in to bsky.app (or a clone like blacksky) with your PDS username and password, and look in the notifications tab.

@mat @eniko So at that point, barring building an entire alternate Bluesky-like system for reading longposts— a system which would be redundant when ActivityPub exists— you're not mirroring your WordPress on Bluesky, rather you're using Bluesky as a funny kind of RSS feed, posting a short announcement of each post there… at which point, isn't it easier to just link your WordPress to a *regular* bluesky account, and use the API to auto-post summary+announcements for new posts?

Am I making sense?

@mat @eniko Another thing to note. Posts on ATProto are 300 characters. The entire system is set up to mark "schema invalid" and wholly censor any post which is more than 300 characters. So what you'd have to do is put a 270 character summary of your post, plus a link to your real wordpress, into the PDS. (It's not a schema violation to contain *extra* data, so you could include a "full-text" field in the post blob, but no system in existence could read it— not even yours, you'd be publish-only)