Reddit didn’t keep their deadline for the API implementation. I’ve still got Boost installed and it’s still working, nsfw posts however went away yesterday. You can still get nsfw if you use revanced apparently but I’m just checking reddit now out of curiosity.
Perhaps it’s not completely implemented everywhere. You can go to r/BoostforReddit if you want to read more about it. Idk and honestly idc either, the whole thing is kind of a shitshow. When Boost stops working without patching I’m out of the reddit ecosystem for good.
Edit: I just woke up when I wrote the original comment and I can see that it’s not the clearest piece of text I’ve ever produced. What I meant is that I fully agree with defederating (and I’ll do it on my instance), but I don’t think censoring Meta in the core technology (ActivityPub) is the way to go.
It literally is, do you not see the power dynamics here? If the fediverse is to defend itself it must at all cost not federate with Meta or we will end up like XMPP.
Meta doesn’t need Lemmy/Kbin/Mastodon. They are competing with Twitter. Threads will probably have more users than the whole fediverse combined within the first few days.
That’s known, but it’s foolish to think that for example Mastodon isn’t seen as a Twitter alternative. Meta knows that and I think they want to not just be a corporate alternative to twitter, they want to make sure they are the alternative to twitter. The Fediverse has to take measures defending itself or Threads will overtake and stomp over everything, even if the sudden user surge might be appealing to some.
Changeable definitely, would have to think about whether default block is the smart thing to do. It’s hard, I really dislike Meta, but on the other hand if you go censoring instances by default, where does it stop?
IMO this should be the job of articles that tell you how to setup Lemmy, mentioning something like “Note that by default you also allow Meta the access to your instance which might mean privacy breach, here’s how you disable it.”
Many admins are lazy, and they expect their software to run well on sensible defaults, most won’t care and just go with whatever the devs consider to be fine. By choosing wether Meta is blocked or not by default the fediverse will have to take a stance.
Do we allow extremely powerful corporations that want to monopolize their influence but we get a user surge in the short term.
Or do we block them by default and anyone making an instance should make the concious choice to join the corpo-verse themselves so we can continue to foster a healthier alternative to whatever they are cooking.
Its not censorship and its not up to you, the instances are run by private people, they can defederate whatever they want. If you don’t like it use their “service” problem is that due to federation its very problematic to forward data to Facebook, especially for European Servers.
Arbitrarily blocking an actor at the protocol level is directly contrary to the entire point of decentralized protocols in the first place.
I know, Meta bad, but the fact of the matter is that they probably won't be defederated by everyone, actually, because the idea of being able interact with your real friends and family and other people you know is going to be enticing.
I want their products to fail so miserably that they regret coming here, and if i have to host several bot instances to spam the worst shit imaginable on their shitty platform. I don’t want Facebook to be a part of the internet in the future, they can go bankrupt. They don’t deserve the internet.
I know there won’t be a Meta filter in activityhub, its just a wish.
That’s interesting about mastodon, I’m not exactly surprised, I feel like it’s merely a question of when, not if, apparently that time has already passed for mastodon. I have no doubt folks are already capitalizing or attempting to capitalize on lemmy data in some way or another, or at least letting the data fill their bucket while they figure out how to monetize it.
As a note though, wefwef is FOSS. It’s GitHub page is linked in the web app and there are instructions to host a version of it yourself, if you so desire.
I think there is (unfortunately) value to be mined from packaging the data conveniently, or offering a subscription service to make it trivial to query for anyone without sysadmin or database skills. Or just throw porn ads on it or some shady ad network that doesn’t mind being placed on questionable sites.
I really think Lemmy, Kbin, and Mastodon need to figure out a way to have a default terms of service that ship with their product which forbids using the API to collect data for commercial purposes.
Additionally, there should be a way for users to indicate licensing for individual posts, with a default license instance admins can set.
That way for-profit instances could be forced to filter out posts with licenses that do not allow for-profit use. Honestly, even just a simple check mark "[ ] allow for-profit republication", and have two licenses that can be attached: one that allows for-profit use and one that does not.
Whoever's doing this wouldn't be using Lemmy, Kbin, or Mastodon code. They'd likely write up some custom ActivityPub service that listened in on that protocol. ActivityPub is an open protocol so trying to put some kind of "no profit" restriction on it at this point would be impossible, and having it on there from the start would have killed its adoption.
Lemmy, Kbin, and Mastodon are all currently licensed under the GPL so good luck trying to retroactively put that genie back in the bottle too. The GPL allows for-profit companies to run the code with no further restrictions.
Europe's got the GDPR, if you really want to try some kind of legal route to counter this, but I don't think it's very likely to work well.
I’m pretty sure there is no particular reason why it’s done this way. It’s just the easiest method to coomunicate upvotes across different servers. There are already a lot of ideas for doing it differently or more efficient (e.g. vote aggregation) but that requires a more sophisticated architecture:
Vote aggregation also makes faking votes much more efficient and requires different detection methods. Of course, a spam server can also invent users or votes but it’s a bit more complicated.
Aggregation in any form can be hard to implement because it should be flexible enough to reduce load but not increase delay or make tracking a consistent state even harder. Finding the right configuration will be difficult and go through a lot of trial and error. Should be easier though now that more people are working on the code.
Keep in mind that Lemmy should also be able to communicate with other services across the Fediverse like Mastodon via ActivityPub. I’m not sure if there is something in the standard for message aggregation yet. It’s definitely being discussed because Mastodon, Pixelfed and Peertube all have or went thorugh the same growth problems as Lemmy in terms of scaling, spam and security concerns. If there’s a good solution it will likely come through the AP standard.
Im undecided, to be totally candid I am not super confident in my Ansible skills yet, and dont want to push some of my ansible to github and accidentally expose passwords, public IP addresses, etc. I chose Gitea because it was the first application that came up on Google when I googled “self hosted github”…
I am working on vaulting all of that stuff now and will eventually just move over to Github
lemmy.world
Oldest