PieFed
Rimu
Instance: piefed.social
(Admin)
Role permissions: Admin
Joined: a year ago
Posts: 342
Comments: 1432
Developer of PieFed, a sibling of Lemmy & Mbin.
-
Pronouns
he/him -
Location
Earth
c/webdev
Rimu
c/piefed_meta
c/goodnewseveryone
c/playground
c/health
c/python
c/fuck_ai
c/fediverse
c/california
500k customers
https://getlatka.com/companies/postman
I wonder if the surplus goods that would have been sent to USA will instead flood other markets and bring down prices there.
It's an alternative and will remain one for a long time. Browser & OS support needs to mature before we could even think about making it a hard requirement.
At present I expect only instance admins would be interested in passkeys.
Over time if adoption and viability increases we might want to make passkeys more prominent, include the creation of the passkey as a step in the onboarding process, make email-based 2FA compulsory for every login when people use the old username+password method and various UI nudges to get people moving in the 'right' direction. But all that feels like a long way off at the moment.
I saw your comment earlier today and thought "heh ok, challenge accepted."
https://piefed.social/post/762082
Ok take a look now :)
When viewing a post (not just the teaser of it in a list of other posts), look for this icon:
Only posts with a link will have it.
Yeah. Just off to the right of the screenshot is the approve button which didn't seem relevant at the time.
Yeah.
When I added the Post/Comments filter it became too wide so they were all put in their own dropdown.
I guess hot/top/new get used the most so they should be always visible, the rest can remain buried. Will look into it.
The things I paid attention to was
USB3 - you need this otherwise connecting external drives will be a joke
Motherboard needs to accept up to 32 GB of RAM. Mine currently has only 8 but knowing I can upgrade is nice.
Quiet - must be silent when idle.
CPUs of less than 8th? gen will suck at video transcoding due to lacking certain capabilities. Important if running jellyfin, etc.
The beauty of self hosting is it's all about your individual circumstances so you priorities and acceptable tradeoffs will differ.
There are competing concerns. The instance admin is concerned with avoiding de-federation by keeping the amount of spam and abuse coming from their instance to an acceptable level, without burning out. Some people signing up are concerned about their privacy. (Although this doesn't actually diminish their privacy or stop them from using a throwaway email address. It does suggest that their application needs extra care, tho.)
There's a balance to be struck.
In this case I'm leaning towards the side who pays the bills and the one who decides which software to install on their server. Without getting those people on board there won't be a place to apply for an account with and then act all distrustful about.
Someday when I make my super awesome instance-chooser, maybe "Email address is optional" will be one of the filters. Along with "Bans for criticism of China".
Rather than de-duplication it's more about blocking CSAM / spam and when a large flood of bad images have already arrived finding all the copies of them that there are (even if those copies are slightly different from each other). Demo of it at https://piefed.social/post/751901 .
It looks like we'll need a less fuzzy hash for de-duplication.
Pretty much every Lemmy instance requires email. The only ones that do not require it are small enough that spammers haven't found them yet.
Sure
We'll see. If it turns out to be useless noise, I'll remove it from the signal.
Ah I see we are using the word alias in a different way. I was using 'Alias' as technical term with a very specific meaning. Never mind.
Aliases are different and not flagged by this feature. It just looks at domain names.
Multiple big Lemmy instances have been using the exact same blocklist for a long time (although it's not a core feature, they've patched it in somehow). I got the idea by lurking in the Lemmy matrix rooms and seeing their discussion.
Ah, this is what you need. https://disposable.github.io/disposable-email-domains/lookup
I don't know which service you use or whether it is on the list. But if it's a paid service then it's probably not on the list. Things on the list are like https://10minutemail.com/ or https://www.guerrillamail.com/
You're free to maintain your privacy and admins are free to weigh the potential risk of accepting an application with a warning icon on it. I'm sure there will be plenty who ignore it.
The giant red flag is the name "PayPal".
The permissions system in PieFed is greatly inspired by Drupal , which I spent too many years building websites with. It even uses the same function call
user_access('administer all communities')to check if the current user can do something.Users have one or more roles. Each role has a collection of permissions that have been enabled for it. When a user tries to access a page PieFed doesn't check which role they have, it checks if any of their roles have the necessary permission. This is very flexible and extensible - to limit access to an area the admin can either remove the permission from a role OR remove a user from a role. It's simple for developers too - just call user_access() and leave it to the instance admin to decide which roles can access the functionality.