In other words, your post may still be visible on, say, a linked Mastodon server, even if you decide to delete it with Threads.

“I think this is a downside of the protocol that we use today, but I think it’s important to let people know that if you post something and another server grabs a copy, we can’t necessarily enforce it,” Cottle says.

… it’s not a downside of the protocol, it’s just a literal impossibility. Once someone’s downloaded something, you can’t do a thing to take it back.

As did Pleroma and several other fedi servers — that’s not really innovation, it’s something simple that Mastodon devs deliberately avoided implementing.

Better yet, check out NewPipe on F-Droid. :^)

It’ll try to render it, even if just as markup (like if you try using and Latex markup for math).

The federation with Mastodon is mostly one-way: We can’t see or comment on Mastodon posts, but Mastodon users can see and comment on Lemmy posts.

Mastodon’s like Twitter… its posts wouldn’t fit in the Lemmy UI well. Though I hear kbin works well with both Mastodon-style and Lemmy-style posts.

Thanks!

Would you mind sharing the link/author of the extension? I tried searching on Firefox’es site, but only found spammy-looking unrelated add-ons.

I’ve been wondering about this, too! It might be nice for hash-tags to somehow be invisible to Lemmy (so as to not be intrusive or annoying), but visible during federation to non-Lemmy/Kbin servers? Without hash-tags, discoverability of Lemmy posts on Mastodon & friends is pretty much DOA, unless they’re actively sought out.

Missed the chance for the title “There will never be a second Second Life,” real shame.

From what I understand, opening a port isn’t a risk in and of itself — it’s only a risk if the software using the port is insecure! So long as you use reliable software and take care to configure things properly (following through with instructions from a site like ArchWiki or the official documentation helps), you’re good.

CloudFlare is more for DDOS protection, which you almost certainly don’t need . You could always set up DDOS protection later on, if the need ever arises.

Glad to see raddle is still a cesspool of purity-testing and knee-jerk takes… =w="

I used to really like it, too. I was active and supportive for a couple years (even back when it was raddit!), but wow this reminds me about why I don’t miss it. I’m already liking Lemmy so much more, and I’ve only been here a couple weeks!

I reckon that people become leftists out of compassion, but the dehumanizing rhetoric seems cool and edgy; so they slide into it, thinking it’s OK.

Hate systems, not people. Don’t eat the rich, eat their money.

Jesus, this is just about as blatant as you can get. I honestly can’t imagine how people can eat up degeneracy politics and not get a bad taste in their mouth…

Here’s how you can tell if you’re the baddy: Do you support policies to spite or “own” others? Do you think, “fuck ‘em, I don’t care,” or “they’ve gotta be taught a lesson?”

Then you’re probably the baddy, stop it! Dehumanization, even casually, is the root of all evil.

It doesn’t necessarily mean you’re wrong, obviously — you might’ve stumbled into being right for the wrong reasons — but wow, is it a huge red flag!

I think a client program is a much simpler route — that is, you don’t really need cooperation with providers nor software vendors (with the myriad of headaches that comes with) unlike with the fediverse proposal.

A client could simply connect to the MyChart server of your provider, display the data, etc. The data could be downloaded and cached, in the case that you switch providers or the MyChart server goes down for whatever reason. In this way, the data is there on the patient’s computer for their viewing pleasure.

Of course, interfacing with the APIs of MyChart and other portals might not be easy, but it’s certainly easier and more viable than constructing a totally new infrastructure of these portals using ActivityPub.