Lemmy instances can enable an option to prevent non-admins from creating communities, so if it isn’t available on your instance (usually in the header area on the website) then your instance admins have disabled that option

A possible solution to moderation is allowing communities to delete a parent comment (+ the child comments) from that community w/o actually fully deleting the comment

Therefore if you view that specific post with the context of a specific community, you only see the comments that are not deleted, which have (most likely) been moderated already

If you view the source post directly, you would see all the comments for that post

With the feature request I posted on GitHub, it would work similarly to reposting/reblogging on Mastodon.

Except inside Lemmy anyone who can post in the community would (most likely) create a post linking to an existing post and it would appear that the post mentioned just got posted into that community

Moderators would ideally see who created that crosspost and have the ability to block that person from crossposting (or posting entirely) to that community w/o affecting the third-party post

If someone wouldn’t want their posts crossposted they can just block the community’s actor (account)

It would also allow for Lemmy users to crosspost posts from other Fediverse services, such as Mastodon

Eg you see a post on Mastodon that would fit great in a startrek community, you would be able to cross post that Mastodon post into that community

This would enable individual posts to gain traction and comments without having comments/replies being spread across multiple places

Edit: it would work very similarly to reposting/reblogging on mastodon

🍞

Video hosting is a very expensive process and peertube does a lot more stuff to video files compared to Lemmy/mastodon

I’m not sure if this would be feasible for development or peertube hosts but idk, it would be a neat idea though

I don’t know Rust well enough to implement it in the core of Lemmy, instead it’d be another service instances would run then do some reverse proxy magic to properly run it on their servers

but I’m planning to use it for canvas 2024, so in a couple months there should be at least a functional version published on github (or some other code platform) (i’ll post updates to this on !canvas@toast.ooo & probably my mastodon)

OpenID is a federated protocol and it would honestly be great if Fediverse projects added it to the core servers

more info on this

Your ISP can see that you used tor but not what for

Pixelfed also uses PHP/Laravel in the backend

If you’re worried about notifying the sender that you are a real person, it’s probably not great interacting with the links at all because they are linked directly to your email (same with normal unsubscribe links)

Obviously toast.ooo — no reason

It’s recommended you keep the default port because as soon as your IP is known it takes less than 5 minutes to scan every port for an ssh port

deleted by creator

They also support payment in Monero so you don’t even need your crypto chain

Either way the Matrix homeserver you’re connecting to will log your IP

I ran into this issue when writing the Canvas authentication thing

There is a standard to simplify authentication and identification across the entire web but it isn’t fully implemented everywhere

OAuth2 is the big name in this, it supplies authorized requests to access data from other companies and services

OpenID is related to OAuth2 but it only supplies identification in a standardized way. OpenID has mechanisms to announce that a specific domain has support for this and how to automatically register for it (removing the need to have a bunch of login buttons)

For Canvas 2024 I’m implementing drop in implementations for popular Fediverse software (including Lemmy)

Hopefully more fedi software implements OAuth2 or at least OpenID to vastly simplify authentication (and possibly replace “login with google”)

Related Links:

• OpenID Core Spec
• OpenID Discovery Spec
• OpenID Dynamic Registration Spec
• !canvas@toast.ooo

I’d recommend setting up a Matrix server with Element

E2E encrypted text & voice calls (I believe unless they’re still doing the rewrite of e2e voice calls)

Matrix info: https://matrix.org Synapse server install: https://matrix-org.github.io/synapse/latest/setup/installation.html Synapse TURN (voice) install: https://matrix-org.github.io/synapse/latest/turn-howto.html

Edit: calls also work on mobile (hooks into native mobile calling apis to look very similar to a normal phone call)

The instances page at join-lemmy is completely automated

This definitely needs to get pushed to the two main devs for lemmy as they control that website

If the instance requires verified emails the application won’t even show up to staff if it’s not verified