I continue to be squeezed by both sides of the threads situation. I am operating on the premise that people who think I’m a terrible person and this is a terrible instance for allowing any interaction with threads have left and/or blocked, those remaining seem to want to either have nothing to do with threads at all and are mainly concerned with their data, and those who want to seamlessly interact with threads. I have threads limited/silenced on Infosec.exchange, but that isn’t seamless, and it’s also not fully blocking. So, here’s my proposal: I remove the limit from threads, and run a job to domain block threads for each account. Any account who chooses can undo the block (or ask me to do it) and then they can seamlessly interact with threads, and those who want nothing to do with them get their way.

[...]

(Note: this was only intended for Infosec.exchange/.town, and fedia.social)

– @jerry@infosec.exchange

Here's a very different take on Threads by a Fosstodon admin.

There's a common false dichotomy about #Threads: cut them off, or leave it to user choice.

I can't speak to other software, but Mastodon offers a third option: limiting Threads. This can be done for all users of a server.

- You can follow Threads accounts after clicking through a warning.

- People who don't follow those same people won't see their posts.

- You have to manually approve followers _from_ Threads.

Basically, it puts Threads in quarantine, without cutting off all connections.

I like that option for our server, social.coop, and it's the one we voted to implement earlier this year.

We know that Threads already hosts bad actors (e.g., LibsOfTikTok). We know some reasonable folks have set up shop there and will continue to flee there from X.

This option makes it clear that Threads is not a safe space, while allowing limited connections.

Every instance will implement the option that makes sense to them, of course.

social.coop/@eloquence/1115888…

Año 2023. Todo Internet está bajo el control del imperio GAFAM. ¿Todo? No. Porque algunos pequeños pueblos se resisten a la opresión. Y algunos de esos pueblos comenzaron a agregarse, formando el «Fediverso».

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.

I know there is mobilzon but mobilzon is a meetup.com clone whereas evite is different.

Evite you can create an event and invite people via email or send them a link. They can rsvp and add it to their calendars.

Come of these features are covered by mobilzon but not quite. Evite doesn't require you make a group or add people to the group as members. It's a little more atomic. Honestly I think it's a good deal more flexible than the meetup/mobilzon design pattern.

Default instance blocks should largely replace defederation

Since what content users might want to see is quite unlikely to match which servers the admins tolerate, choosing instance on the Fediverse can be quite complicated, which is inconvenient and off-putting for new users.

For this reason, and simply that the Fediverse is stronger united, I believe defederation should ideally be reserved for illegal content and extreme cases. If Fediverse platforms would allow instances to simply block the rest for users by default, the user experience would be the same, unless they decide otherwise.

@fediverse #fediverse #defederation

https://www.threads.net/@zuck/post/C0zXcQmxO77

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.

I think the title says it all. Basically, when a new comment appears on your targeted post, it sends you a PM about it.

@PostWatchBot@lemy.lol

Usage

• Subscribe to a post: just mention the bot in the comments or send the link to the bot via PM.
• Unsubscribe from a post: send PM to the bot with stop text and link of the post like stop https://lemmy.ml/post/1234
• Unsubscribe completely: Send PM to the bot and add stop text to your message. It will unsubscribe you from all subscriptions.

Note: the bot sends only one notification per post. It waits for the previous notification to be marked as read for new comments.

Made with @CannotSleep420@hexbear.net's lemmy-bot project 🙏 Tomorrow I will publish the code publicly after adding README and self-hosting guide.

from https://lemmy.fediverse.observer/stats

Artemis was a promising mobile app for Kbin, with a dedicated community, a rapid pace of development, and a high level of polish. Then, the developer disappeared.