They mention SWICG’s data portability spec, I assume they’re referring to LOLA: https://swicg.github.io/activitypub-data-portability/lola

Just lemmy.org.uk for me.

Hexbear is basically only blocks lemmy.world

Hexbear runs an allowlist, they only federate with instances they select.

The secure chat option is something called Matrix, which is a separate service that doesn’t integrate like Reddit’s chat. Lemmy just supports being able to set a Matrix account as the place to reach a user.

It not having the people to be a place for you is perfectly acceptable reason to not be interested, but dismissing near 40K people as nothing is just wrong. That’s the population of a decent sized town.

We’re the ones trying to make a product for them

I really hate this language. I’m trying to build a community, not make something to be profited off.

Obviously it’d only be a subset of HTML. No website that uses user-submitted HTML (Tumblr, AO3, Royal Road, etc) actually allows the full suite of tags.

Cool!

Image markdown style formatting to allow more advanced control of how images are rendered. e.g. 

You might as just let users write the <img> tags directly at this point, at least then you won’t add noise to third party apps’ accessibility stacks.

(I honestly wouldn’t be opposed to letting users write HTML directly, it was one of Tumblr’s best features imo)

This seems way less insane than the ‘let’s model online age verification on pubs’ laws we’ve seen in places like the UK and France.

I don’t see why it’d have to be limited to Piefed instances and we can do certain heuristics to test if an instance is good for a user’s location (Piefed’s instance chooser does this).

I’ll defer to you given I don’t do outreach while you do. Honestly an ideal would just be a simple website that chooses a random instance from a list of known good instances and takes them through the sign up process.

You can pry wget from my cold, dead hands.

Not really, a slick design can’t really get away from the fact this is presenting a new user with too much information that they don’t have the system knowledge to understand. This will still lead to choice paralysis and ultimately the user not signing up for any instance.

I’d even say that Piefed putting it on the instance level registration page is actually a really bad idea.

Instance choosers in general are an anti-pattern.

Interestingly, the person who added these to Bluesky say they’re a bad idea: https://blue.mackuba.eu/skythread/?author=hailey.at&post=3m2mldbsmys2t

Probably not. One of the main complaints of Mastodon I’ve seen on bsky is that it’s “Twitter but run by Reddit mods” so I doubt they’d be interested in here.

Of course, a hallmark of a decentralized network is that there is no central authority that could actually do that. Implicitly, this demand is a rejection of the very concept of decentralization.

What, you can absolutely ban people on a decentralised network. You may not be able to expunge someone from a part of the network they control themselves, but you can expunge them from the part you control. Bluesky has this power and has used it in the past.

Masto interprets a Note set as as:sensitive without a summary to mean ‘blur any media attached, but don’t collapse the text content’. I believe the same is true for non-Notes, but obviously without the summary = CW logic.

So a summary included in a non-Note is not CW’d by Mastodon currently.

I know, I was just saying that it prevents a non-Note from being CW’d, as the summery is used as the post’s content.

If it has a summary, I will use that as the content

But isn’t that how Mastodon handles content warnings? Baffling that they’d do it like that frankly given that it prevents long-form content (when masto actually starts supporting that) from being CW’d.

How they see it: https://sfba.social/@otters_raft@lemmy.ca/115267196743748430

Do note that Mastodon forces a redirect to the original instance for non-local posts, here’s a direct link to the comment: https://sfba.social/@karlauerbach/115267230182946226

It seems that threadiverse posts are being seen by more mastodon users now, which is great, but maybe the formatting could use some improvements?

There’s actually some related (yet-to-be-merged) changes to this on the Mastodon side, add support for links in Attachments (this is how Lemmy and the like federate links).

I don’t think anything’s changed, just two users finding a post in a hashtag (Lemmy adds the community name as a hastag for posts). I’ve seen some masto users complain about this in the past on the #lemmy tag.