Seemed like a cool thing to say in the moment. No good?

I said it was my Mastodon account but that server was running Firefish then a fork of Firefish called iceshrimp, neither of which are Mastodon. But it’s now a Mastodon account again.

I follow my own Pixelfed account on Mastodon and will often boost posts. I have a pixelfed.social account though. It’s probably a federation issue on your specific Pixelfed instance. I’ve moved the Mastodon account a bunch and I’ve had problems on specific instances. I was never able to see my Pixelfed posts from fedia.social (ice shrimp), for example.

I was also able to search, follow, and see your Pixelfed posts from mastodon.social.

Edit: Your two newest photos from Aug 31st aren’t actually showing up on m.s. and I can’t see them on pixelfed.social either.

To do that in the short term, the Fediverse probably just needs more money. The competitors have a fuckload of it and can introduce features way faster because of it. I think Mastodon’s been “exploring/planning” quote posts for like 18 months and haven’t even begun working on it. I’d love to have user-controllable, optional algorithmic feeds in Mastodon (not replacing the main reverse-chron feed) but I can’t imagine it existing in less than 5 years.

Mods cracking down on the plague of ‘polite’ harassment (ex. passive-aggressive FYIs about CWs) wouldn’t hurt. It’s not as bad as it used to be but it’s chased a ton of people away.

I think in the long term the Fediverse has an advantage. The only real goal Fediverse services have is to get better for users. At some point, Bluesky and Threads will have to make money or die. I don’t think they have a way to do that without damaging the user experience.

I don’t disagree with your points but I think they apply to pretty specific groups. I doubt that the average person knows or cares that Bluesky is a PBC. The reaction of the average person to ‘open source’ is probably, “I have no idea what that is and please for the love of god don’t explain it to me.”

1. There are more people there.
2. Fewer people even know the Fediverse exists at all.
3. Mastodon (where most would probably move from Twitter) has a reputation for being more difficult to use.

Nailed it

That’s crazy high. Both my fairly old P6 and very new P8 have about 65mb of user data. I may not have as many nudes tho.

For sure, support isn’t always complete and the Masto API is doing a lot of heavy lifting. I think that Fedilab really wants to be a Fediverse app though. I’m pretty sure their development has slowed a lot in the last year too because their dev has had some health issues. Although it’s “tom79,” not Dansup (who makes Pixelfed and a million other things).

I don’t think it supports Pixelfed-exclusive features either. I don’t think there’s even an app that supports stories right now - even the official one.

I don’t think so. The closest might be fedilab. They support masto+ forks, pleroma, friendica, pixelfed, peertube, and many of the misskey forks partially (with fuller support promised). No Lemmy/mbin though and I haven’t seen anything saying that support is on the roadmap.

(there’s a little arrested development in the mix too)

Huzzah!

Missing some of the stuff you want, but I’d also recommend the Pixel+GrapheneOS. The Graphene web installation is ridiculously easy and it’s rock solid in my experience. You get 7+ years of support from Graphene too. Pixel build quality is great. Great camera, solid storage (ymmv), plenty of RAM. In my experience, Google’s hardware support is really good. I’ve been using their phones since the Galaxy Nexus and any time I’ve had even a minor issue they’re just like, “it’s under warranty, do you want a new one?” basically no questions asked. My Pixel 6 is two years out of warranty. A few days ago the battery started to swell a bit. Reported it Sunday and I have a free replacement arriving today. All they asked for was a pic and my mailing address.

Last summer, my nephew managed to grab my phone, take it out of its case, and drop it in the street where it was run over by an SUV. The only damage it took was some serious scratches on the back glass. My old Pixel 3 survived two years in my pocket working on an organic farm and it’s still kicking as my temporary replacement. I’ve found their phones shockingly durable.

I can’t find a complete list, but McCue lists some examples here. These newly-federated magazines are apparently curated by the original 25 publishers in their initial test of federation. You can find the list of those publishers here. You should be able to find the magazines by searching for the publishers on Mastodon. Euronews’ Russia-Ukraine crisis magazine, for example, is:
@russia-ukraine-crisis-euronews@flipboard.com

I was able to follow all the publishers I tried. I also followed a few of the new magazines. Seems to work!

WE DID IT!!

Holy shit, anti-S22+ actually pulled it off!! What an exciting time to be alive! :)

Running GrapheneOS on my Pixel 6. They prompt you to re-lock your bootloader after installing. It’s part of the installation process.

I really hope anti-S22+ wins it all

Unless I’m wrong, the unique thing here is that auth fetch is always off for the server. It’s on only at the user level and it’s only on at that level if a user has an active domain block.

That could actually solve a lot of problems for people. Admins are reluctant to enable it server-wide because it causes a bunch of problems. The biggest being that it breaks federation with servers running older software (Mastodon v <3.0 I think) and with other services (Pleroma, maybe others). It also uses more server resources. But there are always people who think it’s worth it.

@supapp@pixelfed.social

Releasing in beta soon!

Not the solution I was hoping for but it’s an extremely reasonable compromise. I’ve never heard of selective authorized fetch. Pretty sure he just invented it.