MikeBeas

Bluesky is not all of atproto, first of all. There are a bunch of apps thats don’t use any relay at all. Second, even if you aren’t on bsky’s relay, there are others, like the Blacksky relay.

I’m guessing from your constantly-incorrect capitalization of “BlueSky” that you’re not familiar with any of this even a little bit and you’re just repeating what you’ve heard from other, equally unfamiliar people.

Relays are trivial to run now with changes to how syncing works a while back. AppViews are entirely up to the designer of the view. You can make it as complex and expensive or cheap and fast as you want, it’s entirely up to you. You do not have to provide the exact same functionality as Bluesky’s AppView and can basically do whatever you want.

Tons of people have started products without issue. But if you flood a popular relay with data that exceeds its rate limit then getting throttled is to be expected. This doesn’t prevent your participation in the protocol or network.

There are other relays and indexes out there that may have different rate limits. That’s just how these things work. The data from W is still there on their PDS, still public, still crawlable, and able to be backfilled within rate limits.

This is a non-issue.

My Mastodon instance blocked Threads preemptively because they were afraid of the traffic driving up their hosting costs so you’re basically just very wrong or lying about this. A huge flood of incoming traffic can be hugely expensive for ActivityPub node operators. The problem of giant onboarding events is real, there’s just no default protection against them in Mastodon like there is in Bluesky, so operators either have to take matters into their own hands with defederation or risk driving their bill through the roof.

I managed to do it during the beta. Since Catalina installs the OS on a separate partition inside an APFS container, I wiped the OS partition, then booted into one of the recovery modes (there are 3, I think) to reinstall Mojave on the partition containing my data. No data had to be wiped, and most kept working. Music library won’t work with iTunes but I got around that with Apple Music iCloud Library. A few other things won’t work, like Mojave Reminders won’t sync with iOS 13, but otherwise it wasn’t so bad. Think I had to reinstall Homebrew and Node and that was about it. After that I just removed the now-blank partition that formerly housed Catalina and renamed my data partition back to its regular name.

Unfortunately I do not recall which recovery mode I booted into. I tried a few, each offering a different OS to install. One would reinstall the current OS, one would reinstall the version that shipped on the Mac, and one would reinstall the current public build, I think. Wish I had a better recollection of which it was, but since Mojave is no longer the latest public build it may be moot. If you have the Mojave installer downloaded you might be able to just install it right on the data partition and wipe the Catalina OS partition afterwards.

Whatever you do, have a full backup before you even think about starting just in case, of course.

unfortunately im right there with you man. lol

I was typing in a password (which I have since changed, lol) that contained one of these letters and it kept rejecting it. Assuming I was typing it wrong (I’m prone to that), I very deliberately typed in every letter one at a time and noticed that no dot appeared when I got to that character. I was gonna tweet about that one letter but then I started wondering how many other letters would do the same. So I tried them all.

My day job used to be internal technical support at a software company, and now it’s engineering.

Before that I was at 9to5Mac reviewing apps, and even before that I was a pretty prolific beta tester for stuff like iOS jailbreak tweaks, so I’ve got a LOT of troubleshooting and debugging experience that comes in handy here haha. I live to break things.

So I am able to replicate this reliably but at first I misunderstood what was happening.

What happens is this:

1. Type some stuff in

2. Turn on “reveal password”

3. Type one of the “banned” characters

4. Switch “reveal password” back off

5. Type another character

6. The whole existing password is deleted and replaced by the letter you just typed.

So the reason I end up with two Cs in a row at the beginning is because I actually typed in another. After I type in the C that causes the field to reset, I erroneously believed that it had deleted both the B and C, leaving only the A, so I say “C” again out loud and type another C, believing the text entered is now “ac”.

In reality, it had cleared the field, replacing both the A and B with a C. So when I typed in that second C there were then two in a row.

The reason I didn’t understand what was going on was because I was just counting dots and assuming which letters were deleted at first.

Oddly, when this field-clearing behavior happens, it also hides the “reveal password” button until you add a second character to the field. That should be visible with only one character but in this particular situation it hides instead.

Catalyst. The old Twitter apps don’t work anymore. They’ve been cut off API-side.

Can’t imagine why this would cause it to delete all input in the field when one of those characters is typed in using “reveal password” mode though. If you enable reveal, type in a string containing b, and then switch off reveal mode and add another character, it deletes the whole password. If it was just dropping inputs that would be one thing but this seems to be aggressively refusing to allow them in the field.