@OpenStars

I am not sure that you would get this unless I add your user tag @macfranc ?

Yes, I'd still get it, even if you didn't mention me. The problem arises when you reply to someone who replied to me: in that case, I might not receive the notification. Unfortunately (as often happens), the fault lies with Mastodon, not Lemmy/Piefed.

It is not your fault. The entire Fediverse is still being built, and it only gets better over time.:-) The fact that Lemmy + PieFed + mBin + nodeBB can intercommunicate at all is fantastic, even though yes there are some kinks remaining to be worked out:-).

I also believe this statement. Since I've been an instance administrator (Friendica, Lemmy, NodeBB, and Mastodon Glitch-soc), I've always been concerned with how the Fediverse software integrates with each other and with spreading knowledge of the various platforms

My intention was to make light of the reasoning behind criticism of your post, while pointing out to Threadiverse users that once you get past that, the actual content is quite solid. So less “wall of text” than merely “odd-looking introduction”. It’s a good post!

Thank you for your feedback. It's somewhere between a press release and an informational post about the Fediverse. I'm only surprised because, usually, the criticisms about length come from Mastodon users, not Lemmy users...

And yeah the giant text looks weird, haha!

Usually, the problem is solved at the user interface level. BBCode and Markdown have a certain number of standard levels for titles, and it's up to the final interpreter (the interface) to manage their display based on the tool (desktop browser, mobile browser, mobile app, etc.).

Especially since at first it is a repeat of the title, but then goes into new territory after that. I do not know if there is anything that can be done about it though, except further code development on the side of all the myriad varieties of recipients of the message.

Repeating the title, on the other hand, is the best possible solution for integrating threads opened in the forumverse by microblogging users: Lemmy takes the first 200 characters of the first paragraph and converts them into a title, disabling formatting, links, and mentions. That data, however, is re-proposed at the beginning of the post text.
I understand there are some issues, but I don't see any better solution than this.

I should add that, unfortunately, Mastodon's recent implementation of quoted posts has made it difficult for Lemmy to manage opening posts, because Mastodon formats posts that quote another post as:

Re: fedilinkhttps

Post text

And therefore, the title of a Lemmy thread would become
"Re: fedilinkhttps" 🤬

Add in Orbot/Proxy support and I'm there day 1

Tbf, no one will,...

but still!

@Phantaloons The idea would be very interesting. Could you explain it better? In fact, at first glance, it would seem simpler to run Orbot directly before launching the application.
Perhaps rather than adding Orbot to the application, it would be better to create a RaccoOnion fork

If the code is Ai slop, we might could, I dunno... have some proof? Maybe? It just might help your argument avoid another goal-post move.

Any app can be aimed at by Orbot, but if orbot goes down or loses connection, the app doesn't discriminate.

XMPP apps adopt this from Conversations, there's a setting to only listen to the proxy/orbot only.

have some proof?

OP saying it?

the development wasn’t done with vibe coding, but was done over the course of almost two years, integrating observations and addressing issues.

But if everyone stopped to investigate every piece of slop thrown in front of them, all they'd do all day is that.

It just might help your argument avoid another goal-post move.

This isn't an argument, if you think goalposts are moving it means you still don't understand any of it.

But most importantly, I don't really give a fuck if people end up understanding. Go for it bro, slop em up, get those steaks super sloppy and slick your hair back reaaaaaal nice.

There are so many fascinating differences in how your comment reply here shows vs. not.

Like on all of https://lemmy.dbzer0.com/post/70448923 and https://lemmy.world/post/48069327 and even https://piefed.zip/comment/5630582 your most recent comments here do not show up at all, despite it having been sent 2 hours ago. Though somehow your earlier comments are visible, but not your latest ones?

And yet I see them on my instance. I am not sure why, or if your tagging my username specifically helped cause that to happen for this instance but somehow no other instances.

The formatting if I ask to "view markdown source" is messed up - everything is on a single line, and some formatting indicators are missing - but the traditional, regular display mode of the message is perfect.

Interrelation between the different platforms still needs improvements, but it is encouraging to see it get better over time.:-)

@Phantaloons questo è davvero molto interessante. Ma sarebbe più opportuno che questo messaggio venisse letto da @dieguitux8623

I'm still @macfranc@poliversity.it

If I remember correctly, there was a problem in Lemmy that should be fixed with the upcoming 1.0 release and has already been fixed with the latest Piefed releases. This meant that third-level comments that didn't originate from Lemmy or Piefed weren't processed correctly by the platform.

They're out now, but I should compare them with the replies appended to the original post.
https://poliversity.it/@macfranc/116736605177662762

PieFed is running circles around Lemmy, even with the highly irresponsible code vulnerability disclosures awhile back.

As you know better than I, Friendica struggles mightily with scalability, Mastodon is slow to add new features especially those asked for many years, and Lemmy and Mbin are likewise exceedingly slow, whereas PieFed adds new MAJOR features quarterly even.

My hopes for the future of the entire Threadiverse lies with PieFed.

What you say is true, but that's exactly why I have a lot of faith in Lemmy 1.0 which should feature a completely new architectural design.

@Phantaloons @macfranc Laughing out loud for orbot! Who's orbot? A blind AI agent? Allucinating every time?
("orbo" is a term in my dialect meaning "blind" and I'm blind myself)
If I ever consider experimenting agent development, orbot is taken! 🧑‍🦯

@elettrona Orbot è un'applicazione fantastica che si può installare sui telefoni Android anche senza diritti di amministrazione e che in strada tutto il traffico su Rete Onion, la stessa di TOR Project

@Phantaloons

From what I can see, that is not a back-end restructuring but as far as a new architectural design it will purely affect the front-end UI. Which will begin to look somewhat more similar to PieFed, yet without coming anywhere close to what PieFed offers today, as opposed to what PieFed offered like a year ago. e.g. there will be no ability to hold polls (or to share those custom-built feeds?).

More relevant is that Lemmy 1.0 may take a year or so to become fully deployed across the Threadiverse, if past experience is any judge. The devs say to explicitly expect major breaking bugs and perhaps to avoid deployment in prod as a result. And ofc apps are going to need to catch up as well. This one being a breaking change may lead most older apps unable to connect to an instance that uses the newer software (unless I am misreading that part about the older backwards compatible API).

Lemmy.world in particular, which holds ~50% of Threadiverse users and >90% of the most highly-active communities (unfortunately for the aim of decentralization) is well-known for delaying deployment until the Lemmy code fixes such issues.

So a year from now Lemmy will begin to catch up to some of what PieFed had almost a year ago in the past already, and meanwhile I expect PieFed will not itself be standing still all that time... I am glad to see that Lemmy is still being actively worked on, truly I am, but also I find it hard to actually be excited about that pace, by comparison. Then again, any movement forward still counts, and improves the Fediverse as a whole, so by however much, it is still a good thing!

@macfranc @Phantaloons non mi potrei permettere un android "degooglizzato" neanche volendo...

I think you're extrapolating statements as admissions for the sake of your own benefit.

The OP being slop doesn't mean the original dev's code is.

the development wasn’t done with vibe coding, but was done over the course of almost two years, integrating observations and addressing issues.

...isn't an admission of vibecoding

So, let's back up.

GitHub - LiveFastEatTrashRaccoon/RaccoonForLemmy: A Kotlin Multiplatform client for Lemmy

A Kotlin Multiplatform client for Lemmy. Contribute to LiveFastEatTrashRaccoon/RaccoonForLemmy development by creating an account on GitHub.

GitHub (github.com)

There's the source, so you don't even have to go looking yourself, not that you were.

None of this would have been necessary if the platforms allowed native interoperability with a protocol that is literally designed to be interoperable.