It is, but maybe they mean they want no limit whatsoever on post length.

which, well, if your instance starts sending out megabyte-sized text posts I don’t expect it to stay federated with many others for very long.

I see, thanks for the correction.

There used to be this website, but the url just loads up a scam site now (I’ve created this issue on the project’s tracker if anyone has additional info to contribute).

I don’t know how technical you are, @[email protected] , but you could try running the “defed-investigator” project locally.

lemmy.ml, no, but I’m fairly certain that lemmygrad.ml has been defederated from lemmy.world at least, if not others.

I just searched on GitHub for "Sha1-Hulud: The Second Coming.": 692 repositories. On the first page of results I was able to find a repo clearly made by the malware, and in that repo I was able to find someone’s github token with a few applications of “decode from base64”.

This is pretty bad. I don’t know what exactly comes next, an awareness campaign to get people to clean their infected machines and packages?

From my own experience querying public mastodon timelines via API (edit: removed incorrect /api/v1s in the AP_IDs):

• Mastodon user accounts have an ActivityPub URI of https://<instance.domain.tld>/users/<username>
• Mastodon posts have an ActivityPub URI of https://<instance.domain.tld>/users/<post_author_username>/statuses/<post_id> (they also have a url property of https://<instance.domain.tld>/@<post_author_username>/<post_id> but that tends to serve the html view of the post)

To see for yourself, pick an instance that allows viewing their public timeline without logging in (mastodon.social is perfect for this) and follow the “Playing with public data” section of the docs. That page ellides most of the info you’re looking for in the example payloads they give (as the JSON payloads themself are quite large and nested), but I can assure you that AP_IDs for user accounts and posts can be found pretty quickly from a single timeline query.

I don’t think Mastodon has any notion of community, nor does it distinguish between posts and comments (when following a lemmy community, both posts and comments show up in my masto feed as “top-level” statuses (ie posts)).

If we want to keep it silly, then "pie-munchers’ gets my nomination.

Op, I appreciate that you seem to be genuinely interested in these topics, and are not just farming engagement (which is kinda meaningless here on the Fedi, anyways…). If I may offer a suggestion, try to find a tone that doesn’t sound like a roadmap for some corporate brand strategy. Most of us that are here and would be interested in a “fediverse permaculture” are severely put off by the structure of your post, not to mention it lacks in depth for most suggestions to be directly actionable (for example, the merch you would sell to support the insurance still needs to be made somewhere, by someone, who either needs to be paid for their time or are already independently wealthy).

Have you taken a look around [email protected] ? Permaculture is not just about principles of mutual support but also a long process of experimentation to see which combinations of which plants and practices works out “for the best”. You might foster more of the conversation you’re looking for if you can bring some more concrete examples or proposals to serve as topics instead of an all-encompassing manifesto post.

The next time I’m about to moan and complain about how nobody directly implements activitypub apis “the standard way”, I’ll remember this article and be mollified.

As @[email protected] states, diversity is a strength when it comes to resisting capture.

Haven’t gotten through the entire protocol description yet, but so far it seems closer to DMs on a social network than digital letters.

Neat, but maybe we should just do email-over-activitypub then…

I’m not sure if you explicitly want an RFC-style description (i.e. follows https://www.rfc-editor.org/rfc/rfc2119 for MUST vs SHOULD vs etc) or if you are using RFC as a colloquial term for the technical details of the protocol.

In case of the latter, the “protocol” link at the top resolves to this GitHub repo: https://github.com/Open-Email/MailHTTPS-Protocol

Damn, thanks for linking that report. I have appreciated devault’s work for almost a decade, this is a good reminder that just because someone’s public actions align with my values does not automatically mean they are infallible nor should they be canonized.

Same, it’s impressive how much it irks people.

My own hasty judgement is that [those upset] only speak English, have a prescriptivist take on language (albeit unconsciously), and have no idea how damaging hegemony and uniformity for their own sake can be.

Also they’re lazy and would rather shame someone than take on a little bit of discomfort to adapt to them.

I guess that makes it “judgements”, plural.

(youtube) explainer link for the unfamiliar : https://youtube.com/watch?v=ABpT6e-KlOo

For instances that already have a user base, admins should not make any significant decisions without the consent of their users. This goes against our values, and we will not permit an instance to use Bridgy Fed in this manner. We’ve had conversations on how to handle a situation like this, and we would block instances [3] from doing so. We strongly expect admins to be loud about bridging, especially during signup. 3/10

This is very encouraging to read from a project that initially did not understand why many would be opposed to an opt-out bridge to ATProto.

Wanted to try it, signed up for the beta, still waiting on my invite code.

On the surface, bluesky integration makes sense if they’re trying to onboard people onto “the social web”. Still, I’m disappointed they seem to want to be a curated view on what they determine is a feed, and not some kind of plug’n’play feed viewer beyond RSS.

Ok but if it allows anubis to judge the soul of my bytes as being worthy of reaching a certain site I’m trying to access, then the program is not making any calculations that I don’t want it to.

Would the FSF prefer the challenge page wait for user interaction before starting that proof of work? Along with giving them user a “don’t ask again” checkbox for future challenges?

To my knowledge, there is 1 feature that forgejo has that gitea doesn’t: it can generate a new ssh key for you at the click of a button that can be used to push repo changes to another git forge.

I have several personal repos on my forgejo instance that are each setup so that they mirror themselves onto my Codeberg account at noon every day.

I also have a gitea instance on a raspi on my local network that itself will push out changes on certain repos to the (public-facing) forgejo instance.

I can push and/or pull to any of the three origins as needed, but usually I just push to the gitea when I’m at home and the forgejo when I’m not, and let the mirroring take care of propagating changes to Codeberg.

I see the tumblr culture is already present, congrats! Although I never personally used tumblr, my understanding is that more than features or functionality it was very much the culture that its users cultivated that made that site special.

I suspect there is wisdom to be learned from forest management, specifically how regular, small controlled burns are how you avoid huge, unmanageable forest fires.