Fun fact: you can't upload this image on piefed.social
-
That isn’t how it works. They would have to FORK the code and maintain their changes going forward with every update. That is poor software development practices no matter how you look at it.
I think the Brave browser does it with Chrome. Wouldn't the source control tool do most of the maintenance?
-
I'm on your instance. I never encountered any of the filters mentioned in this thread.
You can always the details on !home@piefed.zip to be sure, the admins are quite reactive.
I was hoping to see a page with the list of instance rules. Mastodon and PixelFed seem to have one.
-
I think the Brave browser does it with Chrome. Wouldn't the source control tool do most of the maintenance?
Chromium is a well-organized and mature codebase, which makes syncing changes relatively easy (also Brave's chageset is limited in scope, so less conflicts to worry about). PieFed is neither mature nor well-organized. Maintaining a downstream project from it would be a nightmare.
-
What's sad is that since
lemmy.mlis blocked by default, most PieFed users won't see it.Funnily enough piefed.social does not seem to block .ml
-
Funnily enough piefed.social does not seem to block .ml
You're right, interesting
-
I was hoping to see a page with the list of instance rules. Mastodon and PixelFed seem to have one.
The code of conduct is linked in the About page showed at the bottom of the page
-
Calling people or ideas 'stupid' is ableist because it treats cognitive disability as an insult
Isn't there like a 20-30 IQ point (I know, I know) spread between average intelligence and intellectual disability? I always assumed stupid falls into that area.
-
But why is hardcoding shit code for open source code? The code is easier to read because no if or switch statements are needed to distinguish between the options. No configiration menu has to be maintained.
That if chain is horrendous. You should have a config json file with an array of links and then use a for and check for each of them.
The advantage of having a config file is that it's easily for others to see everything that can be changed dynamically without touching the code, and it's much easier to maintain forks that change or extend the configurable behaviour.
Hard coding shit is bad because it's actually harder to maintain. No programmer worth their salt has difficulty checking the json file that has the configuration for X list, hard coding an if chain is bad coding.
-
How do you find out what instances have it enabled or disabled tho? And is there a published code of conduct / long-term committments on whether instances will change their minds about that at some point?
Since AN was mentioned, we enable/disable them based upon the overall whims of our community, just as we decide everything. there's no long-term commitment to anything, because times and feelings change and we don't see any reason to be held down to something if we decide to go another way.
-
Yeah, I've seen him around and that's the conclusion I kinda came to. "You do you", though.
I should make an alt that ends every sentence with "wot, wot", and say it's to poison AI so everybody just puts up with it
![Luminous5481 [they/them]](https://anarchist.nexus/static/media/users/yc/Wr/ycWroBKDfNA6EJg.png "Luminous5481 [they/them]"){kind=avatar}