spaduf

cross-posted from: https://mander.xyz/post/8095934

Looks like we're getting company!

Highlights include:

0:51 Looking back on Mastodon’s epic year
3:22 Small team, big goals
4:55 The arrival of Threads/Meta: pro or con?
9:01 The way Mastodon/Fediverse is architected to provide a better social media experience
11:24 The “big win” of Meta adopting an open standard
12:10 The game-changing paradigm shift in how social media works
17:30 Why Meta is committing to Threads — a significant moment for the social web
18:10 Mastodon community’s reaction to Threads’ entry
19:24 Preemptively building walls to block Threads: self-defeating?
21:10 Tools and advice for instance owners on interoperating with Threads
26:09 Gaining momentum: who will federate next?
28:34 Bluesky
30:00 ActivityPub: the beauty of a generic protocol
38:24 User experiences in the Fediverse
41:06 “Embrace, extend, extinguish” and the XMPP comparison
50:28 Funding Mastodon through Patreon donations
53:10 U.S. nonprofit version of Mastodon and grant applications
54:23 On outside contributions to Mastodon’s code base
57:42 Hopes and dreams for the future

Links:
https://flipboard.video
!dot_social@flipboard.video
https://flipboard.video/c/dot_social/videos

cross-posted from: https://lemmy.ml/post/9347983

What is Lemmy?

Lemmy is a self-hosted social link aggregation and discussion platform. It is completely free and open, and not controlled by any company. This means that there is no advertising, tracking, or secret algorithms. Content is organized into communities, so it is easy to subscribe to topics that you are interested in, and ignore others. Voting is used to bring the most interesting items to the top.

Major Changes

This release is very large with almost 400 commits since 0.18.5. As such we can only give a general overview of the major changes in this post, and without going into detail. For more information, read the full changelog and linked issues at the bottom of this post.

Improved Post Ranking

There is a new scaled sort which takes into account the number of active users in a community, and boosts posts from less-active communities to the top. Additionally there is a new controversial sort which brings posts and comments to the top that have similar amounts of upvotes and downvotes. Lemmy's sorts are detailed here.

Instance Blocks for Users

Users can now block instances. Similar to community blocks, it means that any posts from communities which are hosted on that instance are hidden. However the block doesn't affect users from the blocked instance, their posts and comments can still be seen normally in other communities.

Two-Factor-Auth Rework

Previously 2FA was enabled in a single step which made it easy to lock yourself out. This is now fixed by using a two-step process, where the secret is generated first, and then 2FA is enabled by entering a valid 2FA token. It also fixes the problem where 2FA can be disabled without passing any 2FA token. As part of this change, 2FA is disabled for all users. This allows users who are locked out to get into their account again.

New Federation Queue

Outgoing federation actions are processed through a new persistent queue. This means that actions don't get lost if Lemmy is restarted. It is also much more performant, with separate senders for each target instance. This avoids problems when instances are unreachable. Additionally it supports horizontal scaling across different servers. The endpoint /api/v3/federated_instances contains details about federation state of each remote instance.

Remote Follow

Another new feature is support for remote follow. When browsing another instance where you don't have an account, you can click the subscribe button and enter the domain of your home instance in the popup dialog. It will automatically redirect you to your home instance where it fetches the community and presents a subscribe button. Here is a video showing how it works.

Authentication via Header or Cookie

Previous Lemmy versions used to send authentication tokens as part of the parameters. This was a leftover from websocket, which doesn't have any separate fields for this purpose. Now that we are using HTTP, authentication can finally be passed via jwt cookie or via header Authorization: Bearer . The old authentication method is not supported anymore to simplify maintenance. A major benefit of this change is that Lemmy can now send cache-control headers depending on authentication state. API responses with login have cache-control: private, those without have cache-control: public, max-age=60. This means that responses can be cached in Nginx which reduces server load.

Moderation

Reports are now resolved automatically when the associated post/comment is marked as deleted. This reduces the amount of work for moderators. There is a new log for image uploads which stores uploader. For now it is used to delete all user uploads when an account is purged. Later the list can be used for other purposes and made available through the API.

Cursor based pagination

0.19 adds support for cursor based pagination on the /api/v3/post/list endpoint. This is more efficient for the database. Instead of a query parameter ?page=3, listing responses now include a field "next_page": "Pa46c" which needs to be passed as ?page_cursor=Pa46c. The existing pagination method is still supported for backwards compatibility, but will be removed in the next version.

User data export/import

Users can now export their data (community follows, blocklists, profile settings), and import it again on another instance. This can be used for account migrations and also as a form of backup. The export format is designed to remain unchanged for a long time. You can make regular exports, and if the instance becomes unavailable, register a new account and import the data. This way you can continue using Lemmy seamlessly.

Time zone handling

Lemmy didn't have any support for timezones, which led to bugs when federating with other platforms. This is now fixed by using UTC timezone for all timestamps.

ARM64 Support

Thanks to help from @raskyld and @kroese, there are now offical Lemmy releases for ARM64 available.

Activity now includes voters

• Previously, site and community activity counts were only based on people who commented, or posted. Those counts now include anyone who voted on a comment or post as well. Thanks to @Ategon for this change.

Upgrade instructions

Follow the upgrade instructions for ansible or docker. The upgrade should take less than 30 minutes.

If you need help with the upgrade, you can ask in our support forum or on the Matrix Chat.

Pict-rs 0.5 is also close to releasing. The upgrade takes a while due to a database migration, so read the migration guide to speed it up. Note that Lemmy 0.19 still works perfectly with pict-rs 0.4.

Thanks to everyone

We'd like to thank our many contributors and users of Lemmy for coding, translating, testing, and helping find and fix bugs. We're glad many people find it useful and enjoyable enough to contribute.

Support development

We (@dessalines and @nutomic) have been working full-time on Lemmy for over three years. This is largely thanks to support from NLnet foundation, as well as donations from individual users.

This month we are running a funding drive with the goal of increasing recurring donations from currently €4.000 to at least €12.000. With this amount @dessalines and @nutomic can each receive a yearly salary of €50.000 which is in line with median developer salaries. It will also allow one additional developer to work fulltime on Lemmy and speed up development.

Read more details in the funding drive announcement.

cross-posted from: https://lemmy.world/post/9483559

PeerTube is a decentralized and federated alternative to YouTube. The goal of PeerTube is not to replace YouTube but to offer a viable alternative using the strength of ActivityPub and P2P protocols.

Being built on ActivityPub means PeerTube is able to be part of a bigger social network, the Fediverse (the Federated Universe). On the other hand, P2P technologies help PeerTube to solve the issue of money, inbound with all streaming platform : With PeerTube, you don't need to have a lot of bandwidth available on your server to host a PeerTube platform because all users (which didn't disable the feature) watching a video on PeerTube will be able to share this same video to other viewers.

If you are curious about PeerTube, I can't recommend you enough to check the official website to learn more about the project. If after that you want to try to use PeerTube as a content creator, you can try to find a platform available there to register or host yourself your own PeerTube platform on your own server.

The development of PeerTube is actually sponsored by Framasoft, a french non-for-profit popular educational organization, a group of friends convinced that an emancipating digital world is possible, convinced that it will arise through actual actions on real world and online with and for you!

Framasoft is also involved in the development of Mobilizon, a decentralized and federated alternative to Facebook Events and Meetup.

If you want to contribute to PeerTube, feel free to:

• report bugs and give your feedback on Github or on our forums
• submit your brillant ideas on our Feedback platform
• Help to translate the software, following the contributing guide
• Make a donation to help to pay bills inbound in the development of PeerTube.

Announcement post here: https://discuit.substack.com/p/df5f002f-e27a-46a6-b30d-7641b266bd65

https://discuit.net/

For those unfamiliar, Discuit is another Reddit alternative that's been floating around for a while. I was unable to find a MAU count, but I am honestly more interested in their software than their communities. Particularly curious what you all think of this stack. A consistent complaint around Lemmy is that a Rust backend makes contribution difficult, will a Go backend contribute to a lower overall barrier of entry?

The fascinating thing about PeerTube right now is that the frontend experience actually seems to be best on other services. This is primarily because discoverability between instances is fairly poor due to both federation mechanics and due to the nature of bootstrapping social. Because Lemmy and Mastodon feature their own human driven mechanisms for content discovery this problem is largely solved so long as you are browsing through another platform (the same mechanisms do not seem to transfer well to a youtube like frontend, although nobody has tried yet). Comments made on Lemmy and Mastodon will also federate back to PeerTube so you're not segregated based on what service you follow from.

Check out some popular channels:
!veronicaexplains_channel@tilvids.com
!letstalkphilosophy_channel@tilvids.com
!alliterative_channel@tilvids.com
!kde@tube.kockatoo.org
!lofiorchestra@makertube.net
!random_retro@makertube.net

Tips:

• All of the above are channels. On Lemmy you can only subscribe to channels while on Mastodon you can subscribe to both channels and users. This is important as some videos get federated under the channels and some under the users. I believe this is up to the individual creator.
• Whitelist only is still fairly popular among PeerTube instances so you may not be able to access all creators from your Lemmy instance.
• Federation does not backfill so if the channels appear blank don't panic. It will fill in with future videos.
• If you follow these channels from Mastodon and then put them in a list you have a feed that is analogous to Youtube's subscribed page.
• Major advantage to following from Mastodon in these early days is it puts you in a better position to help these channels grow, If the boost button is right there things are a lot more likely to gain traction.

Presumably this is due to recent actions regarding adblockers over at Youtube.

https://instances.joinpeertube.org/instances/stats