This is way too overkill for what we need. I’m sorry, I’ve been intentionally vague about the context for this but I guess it’s too unclear. We’re an activist group planning a protest. We might have to get this set up literally tomorrow and every penny comes out of (mostly my) pocket. We’re also all paranoid about opsec and anonymity, which is why the requirement about avoiding corporate services is there. Perhaps I should have posted this in a privacy focused comm instead, I apologize.

It’s pretty overkill for what we need, and it would still fall under “corporate” for us. At that point I could just go for the static Notion page which I can get live in 5m for free.

We can set up all of those but again, that’s kinda expensive for us rn. What’s the benefit of using a CMS like Joomla versus wishthis, or even a basic Caddy/Nginx webserver with a static page?

I believe you need root to access those, plus a file manager that supports it (I use Mixplorer which does). Otherwise, as someone else suggested, you can access them from a computer over ADB or MTP.

Nice! Kudos to Proton for not abandoning their promise to publish their sources… Hoping to see Calendar on there soon too.

I had high hopes when I tried it out but frankly it’s been almost unusable for me. Terrible performance, laggy UI, plenty of bugs, long loading times for songs…

I don’t know if something in my mobile environment was messing with it but I use quite a few indie FOSS apps still in beta and none of them worked as badly as Spotube did. I’d love to go back to it if it improves, but for now it’s just not worth the UX pain.

Edit: forgot to mention. The idea of sourcing tracks from YouTube is cool but causes loads od trouble in practice. I’ve found remixed versions streamed as the original, tracks with the intro from the music video, tracks with sound effects from the music video, and tracks that just cannot be streamed cause they aren’t on YouTube. I know there’s a feature to pick which version to stream, but it’s quite a bit of UX friction and it didn’t work often enough to be a showstopper.

Other people in that thread have pointed out that it isn’t showing posts being delivered to Threads despite the block. That should be testable with other instances, but not Threads since it’s not receiving any content from Mastodon at the moment. The concerning thing there is the user still being able to view content from people they’ve blocked, but that seems to be a bug if it’s reproducible.

In the EU companies can’t scrape personally identifiable information without consent, even if it’s already publicly available. IANAL, and there’s probably ways they can sneak around the GDPR, but at least it’s not a free for all. It’s unclear though how it works for federation. It’s definitely not the same legally though.

The reason for not directly federating content to Threads isn’t so nobody there can ever see my amazing posts, it’s so Meta can’t easily profile me. Scraping public posts on a different platform would probably be illegal, at least in the EU, and reposts don’t give them a lot of data about me. Federating content, however, would give them most of the same data that Mastodon has on me without even having to ask.

This post from Eugen Rochko mentions that blocking Threads at the user level “stops your posts from being delivered to or fetched by Threads”. Basically, the user-level instance block is bidirectional.

Limited federation mode is a different feature, at the admin level. It doesn’t really affect the delivery of posts in either direction, it just hides the blocked instance’s content from the global feed. Defederation on the other hand is indeed bidirectional, but again it’s on the admin level rather than users’.

Mastodon instance blocks are already bidirectional AFAIK: if you block an instance your content does not get federated with them. I was actually surprised that this does not seem to be the case for Lemmy. I don’t think this break any core abstraction of AP…

Ah ok this I’m not sure about. I mean, Lemmy added instance blocks as well in the latest release (0.19), but it seems that, unlike Mastodon, this only hides the content from you and doesn’t prevent your content from being sent to that instance. It does seem like a pretty big oversight, but I haven’t found a discussion about this. There might be good reasons why it’s this way.

I don’t think Lemmy does either…? It pushes updates to subs that at least someone on the receiving instance subscribes to (at least that’s how it worked last time I checked). That’s why there are scripts going around for new instances to automatically follow a bunch of popular subs to populate the All feed.

I think Mastodon works in the same way with users, where it sends updates for accounts that someone on the receiving end follows. So if nobody follows you from Threads it wouldn’t send any of your posts there.

a long form nuanced take

interesting, however have you considered pee pee poo poo

Truly a worthy contribution to the discourse, thank you…

ActivityPub doesn’t just push everything on a server to every federated instance like a fire hose. In the first place, as Masimatutu@mander.xyz said, it only feeds your content to an instance if somebody on that instance follows you, which you can set to require your manual approval. Your posts could also get pushed if somebody else boosts your post and they have followers on the other instance.

However, if you set an instance block, none of your posts get sent to the instance, period. They would have to resort to scraping. In other words, if you don’t want to give meta your data, just set an instance/domain block.

Oh yeah, you’re right on that. If I’m looking for privacy from the subscription manager signing up with a service like this is a terrible choice, because it is fully a financial institution.

I wish they were all on the same day of the month…

Dates aren’t a big concern though. What I was hoping for is something that would update automatically to some extent if (say) some amounts change, or a payment is missed. But I guess indeed that’s basically impossible without access to my payment data.

Given that I have to update it manually though, I would at least like it to be synced remotely. So that I can, say, check it from my laptop on a webpage or desktop app without redoing all the manual data input.

I thought I heard they were rolling out some material you theming in beta a while ago. Did they revert it?

For my use case yes, that would defeat the purpose, but for what it’s trying to do it kinda makes sense… At least, they have to do it to comply with payment regulations. And you’re still only exposing your identity to one service with a decent reputation, rather than plenty of possibly shadier ones. It seems like a fair tradeoff if what you’re looking for is privacy from services you want to pay for.

I’m not American, it seems to be available in the US only…