![](https://media.kbin.social/media/f8/ed/f8ed4148b1eeb9449c665a616ef87ab911cfbad8d24c2e6b8ef79dd2cbd40a98.jpg)
![](https://lemmy.ml/pictrs/image/st9xYggWap.png)
deleted by creator
+/- | amour l’espérance (he/they)
deleted by creator
he surely knows the tech. what’s concerning is how he’s blocking anyone trying to contribute to work on it if it doesn’t fit his agenda. very concerning and self centred. a total waste.
unfortunately he’s not one of the interesting co-author of the protocol. too self centred.
define these people. define these instances. etc etc
what’s your point? anyone can do a screen shot and share it too.
if you want to have a conversation about the content of my post, please keep it on topic : without authorised fetch and a domain blocked at the instance level, the content is pushed.
if you have technical knowledge to add to this or can correct me about the protocol I’m glad to hear it. if not I’m not interested.
Yes and that’s their right.
But thankfully they don’t impose anything to anyone. You had me worried for a minute.
where did you see that the fedipact main purpose was to impose defederation? that would be rich.
I came to the fediverse in 2017, so nothing to do with reddit or meta or twitter.
The fact is here, we have a choice. So you do you.
On mastodon I have an account on an instance that blocked meta and is using authorised fetch (so the proper way to block a domain) : great, my content won’t go there or on any other blocked domains : it’s my choice.
I have another account on another instance that didn’t blocked meta : great, my content will be shared with threads users and I will be able to browse threads.
Choice, isn’t it great?
protecting your content from being pushed to an instance that you though your blocked.
protecting your content from being shared where you though it won’t because of the way things are worded.
yes, on Mastodon when a user block an instance, it’s more like a mute than a block. Your posts will still be available to them, but you won’t see their content.
The only solution if you want to protect your content from being shared on an instance is to block it at the instance level AND that the instance use Authorised Fetch.
Not all instances have this feature on.
Apple Music pays two time what Spotify does. Easy pick between the two.
I’ve read that it doesn’t have e2ee in its specs. Google has a proprietary tweak enabling it but Apple will stick to RSC specs.
Let’s hope that RSC gets e2ee asap.
and for you throwing an example is enough to make a point? how do you know that I don’t bother about it on other places on the web? do you know about whataboutism? do you think that the old “it was always like this so it’s ok” is a relevant position?
please keep your condescending tone to you. if you don’t want to have a real discussion about this and just want to get upvotes, go for it. I don’t care and leave me alone please
Well I’m sorry that you read it this way. I was not my intention.
You didn’t address any of my points and you just unequivocally judged it and dismissed it.
Thanks @Bloonface for writing and sharing this. I think that it’s fundamental to analyse what’s happening with ActivityPub and the Fediverse. It’s good to be here, it feels good to be freed of any disgusting CEO. But still I find it sane to ask ourselves about the quirks that should be addressed with the fediverse?
I have a few on the top of my mind:
Not all instances are run as co-op. We rely on people who are doing a lot of work and paying server cost from their own pocket. Maybe they got funded by users, maybe not. It’s not that transparent. And admin have some issues with each other, defederating, blocking instance for personal or non so personal reason. So at the end it’s not a really sustainable way of building things in my opinion. Some instances are funded as co-op, but most are not. We are relying on individuals to keep things running. The mental charge is big.
We need transparency about instance ownership to be able to choose what model we want to support.
I’m also really interested on how the GDPR compliance will be enforced. Meta’s threads couldn’t launch in the EU, so I wonder about the status of Mastodon. Is it a work in progress situation or did the EU not reach out mastodon.social yet and wait for a bigger user base?
Regarding the efficiency of the protocol, I couldn’t find any discussion about it. I was wondering if the cost of being federated, posts and media being pushed from server to sever will have a negative impact regarding energetic consumption. I’ve read that mastodon was quite “hungry”. So I asked one of ActivityPub co author about it, if they accounted energetic consumption when designing the protocol. The answer was “No.” And they blocked me.
Maybe it’s not a big deal and the impact is not bad. But right now if have no idea. So I’m using a service without knowing the cost of it, the consequence, and this is not ok. And I find it really annoying that this topics is not being covered more and the discussion censored in a way.
It’s not a matter of ruining the nice thing we have. It’s more about transparency, let users know where we are now, so we can all decide where we would go next.
I strongly encourage this discussion, because at the end it’s up to the users - the community - to decide how to use those tools. I think that we have an opportunity here to embrace new custom, and leave what was on reddit on reddit.
but I would argue that the quality argument is flawed in my opinion. upvote and downvote are more used as agreement / disagreement markers.
so if you agree with content, I can understand that you just want to use the upvote (who really is a favorite here in the fediverse) to let the poster know that their content had a positive impact on yourself. I’m cool with that and it’s also good to avoid “+1” or “^^^^this” comments. But maybe it shouldn’t be displayed (every upvote downvote boosts are public in the fediverse, anyone can have access to this info it’s how ActivityPub works for now, just go to more>activity). Favorites are not that public on other platform, I guess only people from the same server are seeing it, or people you follow, I’m not sure about that.
but the downvote mechanism, who could imply a disagreement, is problematic to me. Because we should feel free to specify why we are in a disagreement. They can be so much reason for that and only a conversation, an exchange of thought can help us understand each other.
a simple click on the downvote button is more like a “shut up” for me. Not a really great way to express ourself, to express disagreement. And it’s also too healthy in my opinion.
So yes the strongest issue with this mechanism is how it contribute to encourage a single discourse, a single point of view and tend to discourage users with other point of view to engage. It’s really problematic for me.
upvote or downvote are not good indicator of the quality of a post. a controversial point of view can be of quality but still being downvoted.
I guess if you enable it on your device you are safe, but if your content is on another device that doesn’t enable it (it’s an opt in option), your content will be available.
Yes I’ll correct my post
if you setup tags for a magazine on kbin, posts being published in the fediverse with those tags end up in the Microblog
section. just check it.
He is not relevant