

I can’t seem to add that on the instance I’m using.
When I try to manually do the webfinger lookup, I get 403 Forbidden from Cloudflare.
I’m a #SoftwareDeveloper from #Switzerland. My languages are #Java, #CSharp, #Javascript, German, English, and #SwissGerman. I’m in the process of #LearningJapanese.
I like to make custom #UserScripts and #UserStyles to personalize my experience on the web. In terms of #Gaming, currently I’m mainly interested in #VintageStory and #HonkaiStarRail. I’m a big fan of #Modding.
I also watch #Anime and read #Manga.
#fedi22 (for fediverse.info)


I can’t seem to add that on the instance I’m using.
When I try to manually do the webfinger lookup, I get 403 Forbidden from Cloudflare.


Also here’s a link to the location property.
https://www.w3.org/TR/activitystreams-vocabulary/#dfn-location


Why invent new stuff for this? AS2 has the location property and Place object, which imo should be used for this. It’s not like the request here requires functionality not enabled by those.
And if users refuse to label them, then community mods have tools that help them detect and label them for the users.
And another reason for me to dislike Piefed, I guess.
There is no reliable way to detect AI use automatically, so these tools can’t be a source of truth. But if they’re not, what’s even the point to them for moderation?


I love Mbin, but it’s no alternative for your use case. That AI moderation will keep affecting you as long as you interact with those affected communities, no matter which software you use yourself.


I think you can look at this in a gatekeeping way and a functional way. I’m personally anti-gatekeeping, so there’s that.
What I mean with functional is: why do you care about whether something is part of the fediverse? Obviously because you want to talk to it. You want to be able to reach it from places like Mastodon.
I see no benefit in worrying whether something is based on ActivityPub or merely supports it as one of several protocols. It remains reachable either way, unless your own platform restricts you like in Lemmy’s case.
That said, I do see your point regarding optionality. I think instances that choose not to use the fediverse plugin of their software aren’t part of the fediverse. But that’s no reason to call the software itself not a part of it. Just means users need to put extra effort into choosing an instance.


@Fu@hostux.social Sadly Mastodon isn’t really ideal for posting to Lemmy.
In the federated ActivityPub document, the URL of a Lemmy link post is just a link attachment. So if Mastodon allows you to add arbitrary attachments not limited to images, then maybe there is a way. But otherwise you’re probably out of luck there.


I see you’re on aggregatet.org, which I never heard about. FediDB says it has 10 monthly active users.
If you were to create a community on your instance, only people on your instance could see it. No one on other instances will be aware of it. And any posts made to it would not leave your instance.
For your community and posts therein to federate to other instances, the community needs to be subscribed to from them. You would have to constantly advertise it everywhere to make people aware that it exists, because the likelihood that someone visits your instance and stumbles on it is way too small. It won’t show up on their instance if they search.
With Lemmy Federate, you can give it your community, and it will attempt to subscribe to it from all the instances that have signed up with Lemmy Federate. That way your community appears on those instances when people search for it, and posts you make to the community will federate there.


On PieFed/Lemmy/Mbin groups are called communities, though.
Slight correction, on Mbin they’re “magazines”, not “communities”.


Mbin doesn’t directly merge threads together, in the Piefed sense where the comments from all threads appear on the same page. It does however group duplicate posts together. For example, I’m looking at this, I don’t see the comments on the other threads here, but I DO see there’s four other threads linked.
Tried attaching an image showing how it looks, not sure if that’ll show up in Interstellar/Piefed/Lemmy though.



Because it affects visibility of content.
Read OP’s post, they’re worrying about manipulation, not karma whoring or harassment.
Stuff like bots mass up or downvoting a post to promote or hide it.
I’m assuming they acted rash and emotionally when they decided to make their own platform, and realized the task was too big for them to shoulder, so they went nuclear. It’s not just the fluxer stuff, at least one of them also deleted their socials.
I think them deleting their apexsync discussion server before the release date (so people have no chance to switch over if they forget the name) is proof that the project has died. Or at least isn’t planned to release any time soon after all.
No, they’re pointing out that the server this post is about got deleted.
The admins got annoyed by Fluxer’s stability issues and announced they’d be developing their own activitypub platform instead to compete with fluxer, leading to them neglecting the Fluxer server this post is about.
Then, both the fediverse server and the one about their alternative got deleted. At least one of the admins also deleted their Mastodon.


Look, you’re free to keep replying, but I’m not going to further talk here. I’m just writing this last comment to clarify that, so you can stop wasting your time. I realize that you’re not arguing in good faith, so this is just going to go on endlessly otherwise.


and you don’t support resistance against genocide in practice
What I don’t agree with is that wording.
I don’t support this specific form of resistance against genocide in practice. What you wrote there most literally means I don’t support resistance against genocide in practice in general, which is what I can’t agree with. If we’re just talking about Hamas specifically, or the shape that resistance has taken in this genocide specifically, then I agree with the statement. But the way it’s written here and was written before, I can’t agree with it, it’s too broadly worded and easily misconstrued when taken out of context.


You’re really not arguing in good faith, are you? Not supporting hamas doesn’t mean I’m not in favor of resistance against genocide.
But just to clear this up once more:
So no, I do not support Hamas. But yes, I do support Palestinian resistance in theory.


If that’s your point, you replied to the wrong comment of mine earlier.
When I said “I don’t agree on that claim, no.” I was specifically referring to the claim that I oppose resistance to genocide, period. When in reality I’m opposing the form that resistance is taking, not resistance itself. That’s why I said I don’t agree with the claim made.
You don’t seem to argue with that fact, you’re just arguing about my actual position. Which isn’t what I was denying.


That’s not what I said that in response to. This doesn’t mean I oppose resistance to genocide, this means I have expectations towards resistance groups. Not the same position. Opposing the form doesn’t mean I oppose the concept.


I don’t agree on that claim, no.
No, what I meant was, I tried to investigate why it doesn’t work, by doing the request myself. Webfinger is the endpoint used by instances to resolve a
name@domain.tldaddress to an actual URL. And when I tried requesting that, I got a 403 Forbidden error from Cloudflare. Still getting the same result (both manually and on the instance, there’s still nothing there too).Looking into it further, it seems Cloudflare presented me with a Javascript challenge. Which won’t work without a browser. That’s why it didn’t work for my manual attempts, but federation would trip up there too unless the server was running Electron. Which makes no sense for a backend.
I’m not sure if this is why it didn’t work for the instance I’m using of course. It working for you suggests not everyone gets the challenge. But it is a likely reason it doesn’t work for some of us. In the first place, this kind of anti automated access protection makes no sense on endpoints specifically meant to be accessed in an automated manner.