Notices tagged with lemmy, page 7

@dangillmor

I really want to be done with Reddit like I am with the bird site but the alternative in #KBIN just isn't working --- the other alternative #Lemmy is run by some unsavory characters so I'm not going there....

@liaizon as you alluded to in your reply, WP gets around this by assuming type as:Note which I disagree with from a protocol fragmentation standpoint. It implicitly acknowledges Mastodon as the dominant #ActivityPub player with clout to change the behaviour of others, and I stand against it.

#nodebb will send type as:Page (like #lemmy and #kbin), and we will work with @article_interop (and hopefully @pfefferle) to encourage Mastodon to handle it properly by modelling the appropriate behaviour.

#Lemmy wants to have private communities!

See https://lemmy.ml/post/12014733

> Private spaces are a fundamental aspect of human communication. They allow discussing sensitive topics without interruption from outsiders. Supporting private communities in Lemmy gives a major new use case for talking among friends or within organizations. This use case is currently not covered by major Fediverse projects.

Novel for the #fediverse it seems.

I have to say, I am deeply, deeply disappointed in Lemmy as a community and as a platform. Lemmy clearly doesn't live up to its promise for a better and more equitable user experience. So let's give Mastodon a try.

#mastodon #federation #lemmy

Google provides a tool called PageSpeed Insights which gives a website some metrics to assess how well it is put together and how fast it loads. There are a lot of technical details but in general green scores are good, orange not great and red is bad.

I tried to ensure the tests were similar for each platform by choosing a page that shows a list of posts, like https://mastodon.social/explore.

PieFed and kbin do very well. pixelfed is pretty good, especially considering the image-heavy nature of the content.

The rest don’t seem to have prioritized performance or chose a software architecture that cannot be made to perform well on these metrics. It will be very interesting to see how that affects the cost of running large instances and the longevity of the platforms. Time will tell.

https://join.piefed.social/2024/02/13/technical-performance-of-each-fediverse-platform/

#akkoma #Kbin #Lemmy #mastodon #misskey #peertube #piefed #pixelfed #pleroma #webPerformance

The fediverse is working. I am now following (using Mastodon) a "Learning Rust" community on Lemmy [1], who I found through them commenting on my peertube video [2] using Lemmy.

[1] @learningrustandlemmy [2] https://diode.zone/w/wJJJ7DRh3fCvHq6KuZY3t9

#fediverse #rust #lemmy #peertube

Us sitting here with our fiber internet and recent model phones have it pretty good. But the “i” in iPhone stands for “inequality”. Most people in the world still have pretty bad internet and old/slow phones. For a platform to be widely adopted and to serve the needs of those who often miss out, it needs to be frugal in network and cpu usage.

Due to Lemmy’s javascript-heavy software architecture, visiting a Lemmy home page involves downloading a lot of JavaScript – about 4.0 MB of it. And this only gets you 20 posts! Also community thumbnails, even if displayed as a 22px by 22px icon are served directly from their home instances, unresized, which can often be multiple megabytes in size. The home page of lemmy.nz is currently weighing over 9 MB.

Kbin’s home page comes in at a respectable 1.65 MB due to relying less on JavaScript. However it is let down by not using loading=”lazy” on images so they all need to be loaded immediately and by generating post thumbnails that are twice as big as they need to be.

The PieFed home page, showing 5x more posts than Lemmy, weighs between 700 and 930 KB, depending on which posts are shown. In low bandwidth mode, the home page is only 320 KB due to not having any thumbnails.

When viewing a post, we can assume various assets (CSS, JS and some images) are cached due to loading the home page first.

The picture looks similar when viewing a post, which is a bit surprising. One of the usual benefits of the JS-heavy SPA architecture used by Lemmy is that once all the ‘app’ is loaded into the browser, subsequent pages only involve a small API call. However, going to a page in Lemmy involves two API calls (one for the page and one for the comments) both of which return quite a bit of data. If you look at the ‘get the comments on this post’ JSON response you can see the developers have fallen into the classic SPA pitfall of “over-fetching“. They’re retrieving a whole haystack from the backend and then using JavaScript to find the needle they want, which involves transferring the haystack over the internet. Ideally the backend would find the needle and just send that to the frontend.

Kbin sends more data than it needs to when viewing a post, again because of not using loading=”lazy” which causes every profile picture of the commenters to be loaded at once. Making this simple fix would bring the weight down, from ~800 KB to around 50 KB.

PieFed only sends 10 KB – 30 KB to show a post, but it varies depending on the number and length of comments. This could be reduced even more by minifying the HTML response but with PieFed under active development I prefer the source to be as readable as possible to aid in debugging.

This is no accident. It is the result of choices made very early on in the development process, well before any code was written. These choices were made based on certain priorities and values which will continue to shape PieFed in the future as it grows. In a world where digital access remains unequal, prioritizing accessible and fast-loading websites isn’t just about technology; it’s a step towards a more inclusive and equitable society.

https://join.piefed.social/2024/02/09/comparing-network-utilization-of-lemmy-kbin-and-piefed/

#Kbin #Lemmy #piefed #threadverse #webPerformance

New: Last Week in #Fediverse ep 54

- The #Lemmy developers host an AMA, talking about decentralisation, platform identity and a roadmap
- @nodebb talks about how they are thinking about what federating forums actually means, and how their implementation of #ActivityPub will look like
- Project Tapestry by @Iconfactory is a Kickstarter to build an App that gives you a single chronological feed from a variety of sources, such as #mastodon, #bluesky and #rss

Read at: https://fediversereport.com/last-week-in-fediverse-ep-54/

#Sharkey's recent vulnerability and their handling of it is still miles better than #Lemmy's #XSS exploit which actually took down a big instance and is something even more elementary than what Sharkey experienced.

Like seriously, the first thing you do when #Markdown parsing is involved is to sanitize the hell out of it, both in the Markdown input and the HTML output. And you put up a strict #CSP for good measure. Lemmy spectacularly failed on both counts, despite existing as a project for years and a lot more instances (and therefore users, which rivals #Mastodon) using their software!

I can cut some slack for the Sharkey devs here because:

- they're relatively new (only months since the project started)
- it only affected note imports from #Twitter which is already niche enough
- it was easy to mitigate (just disable note import)
- it didn't affect single-user instances IIUC
- I haven't seen any Sharkey instance get actually exploited by this
- they're taking steps to make sure this shit doesn't happen again (haven't seen this from Lemmy yet, and last I checked their CSP is still shit)

So this is not worth blowing over in the #fediverse. Your assessment is exaggerated, this energy could've been spent somewhere else, and you owe the Sharkey devs an apology.

#fediversemeta #security

RE: https://meowcity.club/fedi/tetra/p/1706812792.496325

don.park@gmail.com is coming to #FediForum and wants to talk about:

Identity re-use, especially a #mastodon account to login to a #lemmy server

Do you think this is a problem, too? If so, join us in March! More info and registration: https://fediforum.org

Made a #Fediverse #Infographic.
🌚 #DarkMode
📱 #HandDrawn with #Dotpict for #Android
🗨️ #FeedbackWelcome
🏴☠️ License: #CCBY ( #CreativeCommons Attribution 4.0 International) vrtxd
🗓️ Sun 28 Jan 2024

#PixelArt #DigitalArt #LibreCulture #Facebook #Friendica #YouTube #PeerTube #WhatsApp #Signal #Instagram #Pixelfed #WeChat #WordPress #TikTok #Firefish #Messenger #Element #Twitter #Mastodon #Zoom #Jitsi #Slack #Zulip #Discord #Mumble #Reddit #Lemmy

#Activitypub related #projects supported by NGI Zero. #EU

#NGIZero #fediverse #mastodon #Lemmy #keyoxide #pixeldroid #peertube #GoToSocial #OwnCast #Bonfire #Hubzilla #Kbin #Xwiki #Funkwhale #ForgeFed #Castopod #Nyxt #Mobillzon #ActivityPods #Libervia #Pixelfed

New blog post: “Why I Started @sublinks” https://jasongr.im/blog/why-i-started-sublinks/

#sublinks #fediverse #lemmy

#Lemmy and #kbin are technically forum softwares as well, even though their design lineage shares more in common with Reddit than traditional forum software. I assume you're already familiar with them 😅

Lastly, while @luceos and I have not spoken at length about integration, it is in our best interest to work together so that compatibility between our platforms is strong. All thanks to #ActivityPub!

@leroy @nodebb @multiverseofbadness

The last 5 days have been very busy, as expected. Things always get intense for a while when other people start using new software out there in the real world.

The main purpose of this phase is to fix problems that show up and to get enough #ActivityPub data flowing through the system to highlight any fundamental design problems with either the structure of the database or the code. I have been pleasantly surprised at how well it handles a high volume of incoming Activity data. After 5 days of operations there are now 7,000 posts, 28,000 comments and 500,000 votes while all database queries are still returning their results in under 100ms and CPU load average is under 1.0 (under 0.20 during quiet times). It seems to be about 33% as heavy as my #Kbin instance (running on the same server) was.

As well as fixing bugs and monitoring performance, I’ve added a slew of improvements and features:

• Comments are ranked by hotness, not just ‘top’ as they were at the start.
• Image posts can be viewed ‘inline’, without having to go to the post itself. Look for the magnifying-glass icon. This will the body of text posts in the same way, soon.
• Community subscriptions can be imported from #Lemmy
• Bell icon on community heading to be notified about new posts in the community. Notifications about replies to to your post or comment can be toggled using a similar bell icon on your post/comment.
• Low bandwidth mode – no images and less Javascript
• A notice on Beehaw posts to be mindful of their higher quality standards
• Topics in breadcrumb – better community discoverability
• PieFed groups to join

Coming up soon, no promises when tho:

• Send an email about unread notifications (with unsubscribe, naturally)
• Federation fixes, especially issues with Communities hosted on PieFed not sending posts out to other servers.
• Masonry-based layout for image-heavy communities like this one.
• Themes, including dark ones.
• Code introduction and development environment setup screen-casts, for future developers.

https://join.piefed.social/2024/01/10/beta-test-update/

#activitypub #fediverse #Kbin #Lemmy #piefed #python

@malcircuit Is there any forum software that federates? Besides #Lemmy?

I guess now we know the small reach of #Guppe groups is indeed a Guppe #bug or #WAI (working-as-intended).

I've noticed this since last year, after Guppe went down for almost a month(?); but I thought it was just me, or a temporary scaling issue with Guppe. But there's no denying it anymore, Guppe's reach is now very limited.

Read this: https://catodon.social/notes/9o5rig8kn30k3hdw

If similar software / platforms work fine (like #Friendica forums, #Chirp groups, #Kbin magazine, and #Lemmy communities) then the logical conclusion is this issue is on the side of Guppe groups.

Major communities still using Guppe groups should consider moving to Chirp, Friendica, Kbin, or Lemmy, if they want to reach #Fediverse network, until this is fixed.

@retrobeetism I have a similar experience. #Guppe groups (at least after it went offline for almost a month(?)) rarely works all other #Fediverse platforms (those I've tried). But #Chirp groups, #Friendica forums, #Kbin magazine, and #Lemmy communities, there are rarely any problems.

My brain tells me that the issue is with Guppe platform, since all other similar software works fine. They did something to break interoperability with the rest of the Fediverse, and created its own bubble with Mastodon.

@007 @ArtBear

@007 Ahh, really? During the early days of #Guppe it was working fine for any #Fediverse platform. I'm not sure when it stopped.

It wouldn't be a stretched that it stopped working for the entire Fediverse, except Mastodon, after it went online for almost a month(?). So, that means they intentionally blocked everyone else?

I guess #Chirp, #Kbin, and #Lemmy are the best options now. What's the point of using Guppe groups if it cannot reach the entire Fediverse.

@panos