PieFed v1.9 is released - Shared Blocklists, Auto-bans and TOTP
-
I don't want to get too off-topic here, so I'll message you.
May as well start with rimu flat out attacking everyone associated with it again
-
...what? No its not...https://codeberg.org/rimu/pyfedi/commits/branch/main its all people. real people.
Plus the code is not in the style AI usually does python.
did you even read the thread here? Rimu already admitted to using AI to patch a commit into piefed he didn't even bother to copy and paste under his own credentials.
Even OP’s boyfriend admitted to using LLM for this theme.Both projects use LLM. This isn't debate, but facts.
-
{
"@context": "...",
"id": "https://example.org/blocklist/general",
"type": "OrderedCollection",
"name": "General Blocklist",
"summary": "Description of the list",
"attributedTo": "https://example.org/u/admin",
"published": "...",
"updated": "...",
"totalItems": 2,
"first": "https://example.org/blocklist/general/entries?page=1",
"inbox": "https://example.org/inbox",
"visibility": "public",
"subscriberCount": 10
}The feature is nothing more than shared basic JSON data. If your thrust is that Rimu is too incompetent to handle that, I don't really think so, but I can accept that too.
Are you going to share your source for your claim of "deliberately breaking compatibility"? Pretty strong claim...
-
You won't acknowledge it but for everyone else here's rimu saying well it's just unfortunate and their fault totally nothing I did
PieFed v1.9 is released - Shared Blocklists, Auto-bans and TOTP - Lemmy.World
cross-posted from: https://piefed.social/c/piefed_meta@piefed.social [/c/piefed_meta@piefed.social]/p/2603915/piefed-v1-9-is-released-shared-blocklists-auto-bans-and-totp [https://piefed.social/c/piefed_meta@piefed.social/p/2603915/piefed-v1-9-is-released-shared-blocklists-auto-bans-and-totp] ## New features - Shared blocklists - these are like feeds except instead of listing communities to join it lists people to block. To to Account -> Blocklists to find this feature. Changes by the blocklist author effect all the people who subscribe to the list, causing them to block the list members. They federate, so you can subscribe to blocklists on other instances. - Edit comments inline, without loading a separate page - wjs018 - Fediverse statistics at https://piefed.social/statistics [https://piefed.social/statistics] - 2-factor authentication (TOTP) - can be added to your account in the ‘Security’ page in your settings. ## For admins - Auto-ban based on the bans that instances you choose, with keyword matching on the ban reason. Go to /admin/users/auto_ban. Try putting ‘piefed.social’ in as the instance and ‘spam’ as the keyword filter. It’ll cut down on the work involved in running your instance SO much. - Voting pattern graph on user profiles to help spot automated voting. - Reset the password of any user. - Lots of inauthentic behaviour reports for finding bots and serial downvoters, see /admin/votes and PM me for an instructional video. It’s a lot to take in but the video will explain it all. ## API - edit matrix user id when saving user profile data. - scheduled post endpoints - wjs018 Plus a lot more bits and pieces, browse the list of recent releases in the 1.8.x line at https://codeberg.org/rimu/pyfedi/releases [https://codeberg.org/rimu/pyfedi/releases] for details. — ## To upgrade from 1.8.x or earlier git pull git checkout v1.9.x Then, ./deploy.sh or ./deploy-docker2.sh — ### Donations PieFed is free and open-source [https://codeberg.org/rimu/pyfedi/src/branch/main/LICENSE#L587] software while operating without any advertising, monetization, or reliance on venture capital. Your donations are vital in supporting the PieFed development effort, allowing us to expand and enhance PieFed with new features. Donations can be made via Patreon [https://www.patreon.com/PieFed], Liberapay [https://liberapay.com/PieFed/] or Ko-fi [https://ko-fi.com/piefed].
(lemmy.world)
What do you mean I "won't acknowledge it"?
Are you defending @awesomelowlander@cozyver.se 's claim?
-
Are you going to share your source for your claim of "deliberately breaking compatibility"? Pretty strong claim...
There are 3 possibilities:
- By accident. That would mean Rimu didn't know about the existence of Pylova's blocklist feature. Lets not go down there.
- Forced / without choice. Because he wasn't capable of doing it, or somebody held a gun to his head.
- Deliberate. He made a conscious choice to do so. Whether because he felt another approach was preferable, easier, w/e.
You seem to be conflating 'deliberate' with 'malicious'. Those are 2 separate things. Read my original statement again without projecting any of your assumptions onto it.
-
did you even read the thread here? Rimu already admitted to using AI to patch a commit into piefed he didn't even bother to copy and paste under his own credentials.
Even OP’s boyfriend admitted to using LLM for this theme.Both projects use LLM. This isn't debate, but facts.
Your first link doesn't mention AI at all and your second link is about a separate frontend for PieFed from a separate repo?
-
Your first link doesn't mention AI at all and your second link is about a separate frontend for PieFed from a separate repo?
Look up the dates of Mia’s pulled patch in the diff.. You’ll find Rimu’s output of ChatGPT’s Python.
-
This is a different question. The comment above is advocating for "Piefed to stop copying Pylova features", you are speaking about compatibility, which I guess would also be criticized for "copying the feature".
I'm only pointing out the optics of it aren't great. I do agree Pylova doesn't have a monopoly on a feature just because it implemented it first.
-
What do you mean I "won't acknowledge it"?
Are you defending @awesomelowlander@cozyver.se 's claim?
Ty for proving the point
-
There are 3 possibilities:
- By accident. That would mean Rimu didn't know about the existence of Pylova's blocklist feature. Lets not go down there.
- Forced / without choice. Because he wasn't capable of doing it, or somebody held a gun to his head.
- Deliberate. He made a conscious choice to do so. Whether because he felt another approach was preferable, easier, w/e.
You seem to be conflating 'deliberate' with 'malicious'. Those are 2 separate things. Read my original statement again without projecting any of your assumptions onto it.
I notice you have once again failed to provide any source for your strong claim. I think at this point we can assume you made it up.
Gee, who could have predicted the exact crybullies rimu was talking about who show up to tell lies about him any time PieFed is mentioned would show up and tell lies about him!
-
I notice you have once again failed to provide any source for your strong claim. I think at this point we can assume you made it up.
Gee, who could have predicted the exact crybullies rimu was talking about who show up to tell lies about him any time PieFed is mentioned would show up and tell lies about him!
At this point I'm not sure you even read my comment... WHAT strong claim? Would you like to take a look at my previous comment and tell me which of the 3 possibilities you think was the case?
-
Look up the dates of Mia’s pulled patch in the diff.. You’ll find Rimu’s output of ChatGPT’s Python.
Which patch? I'm not gonna dig through the whole git history...
-
Ty for proving the point
I mean, I definitely proved a point.
-
At this point I'm not sure you even read my comment... WHAT strong claim? Would you like to take a look at my previous comment and tell me which of the 3 possibilities you think was the case?
WHAT strong claim?
You made the strong positive claim that rimu deliberately broke compatibility with pylova.
I've asked you twice now for your source for that claim. You've instead given me other scenarios you imagine could be the case if it wasn't true that rimu deliberately broke compatibility.
That's completely non-responsive to my question... No one asked what you imagine might have happened.
-
WHAT strong claim?
You made the strong positive claim that rimu deliberately broke compatibility with pylova.
I've asked you twice now for your source for that claim. You've instead given me other scenarios you imagine could be the case if it wasn't true that rimu deliberately broke compatibility.
That's completely non-responsive to my question... No one asked what you imagine might have happened.
So the comment that somebody else linked an hour ago, that you replied to, direct from Rimu, isn't enough? Or are you being deliberately facetious here?
PieFed v1.9 is released - Shared Blocklists, Auto-bans and TOTP - Lemmy.World
cross-posted from: https://piefed.social/c/piefed_meta@piefed.social [/c/piefed_meta@piefed.social]/p/2603915/piefed-v1-9-is-released-shared-blocklists-auto-bans-and-totp [https://piefed.social/c/piefed_meta@piefed.social/p/2603915/piefed-v1-9-is-released-shared-blocklists-auto-bans-and-totp] ## New features - Shared blocklists - these are like feeds except instead of listing communities to join it lists people to block. To to Account -> Blocklists to find this feature. Changes by the blocklist author effect all the people who subscribe to the list, causing them to block the list members. They federate, so you can subscribe to blocklists on other instances. - Edit comments inline, without loading a separate page - wjs018 - Fediverse statistics at https://piefed.social/statistics [https://piefed.social/statistics] - 2-factor authentication (TOTP) - can be added to your account in the ‘Security’ page in your settings. ## For admins - Auto-ban based on the bans that instances you choose, with keyword matching on the ban reason. Go to /admin/users/auto_ban. Try putting ‘piefed.social’ in as the instance and ‘spam’ as the keyword filter. It’ll cut down on the work involved in running your instance SO much. - Voting pattern graph on user profiles to help spot automated voting. - Reset the password of any user. - Lots of inauthentic behaviour reports for finding bots and serial downvoters, see /admin/votes and PM me for an instructional video. It’s a lot to take in but the video will explain it all. ## API - edit matrix user id when saving user profile data. - scheduled post endpoints - wjs018 Plus a lot more bits and pieces, browse the list of recent releases in the 1.8.x line at https://codeberg.org/rimu/pyfedi/releases [https://codeberg.org/rimu/pyfedi/releases] for details. — ## To upgrade from 1.8.x or earlier git pull git checkout v1.9.x Then, ./deploy.sh or ./deploy-docker2.sh — ### Donations PieFed is free and open-source [https://codeberg.org/rimu/pyfedi/src/branch/main/LICENSE#L587] software while operating without any advertising, monetization, or reliance on venture capital. Your donations are vital in supporting the PieFed development effort, allowing us to expand and enhance PieFed with new features. Donations can be made via Patreon [https://www.patreon.com/PieFed], Liberapay [https://liberapay.com/PieFed/] or Ko-fi [https://ko-fi.com/piefed].
(lemmy.world)
Do you understand the meaning of the word deliberate?
-
So the comment that somebody else linked an hour ago, that you replied to, direct from Rimu, isn't enough? Or are you being deliberately facetious here?
PieFed v1.9 is released - Shared Blocklists, Auto-bans and TOTP - Lemmy.World
cross-posted from: https://piefed.social/c/piefed_meta@piefed.social [/c/piefed_meta@piefed.social]/p/2603915/piefed-v1-9-is-released-shared-blocklists-auto-bans-and-totp [https://piefed.social/c/piefed_meta@piefed.social/p/2603915/piefed-v1-9-is-released-shared-blocklists-auto-bans-and-totp] ## New features - Shared blocklists - these are like feeds except instead of listing communities to join it lists people to block. To to Account -> Blocklists to find this feature. Changes by the blocklist author effect all the people who subscribe to the list, causing them to block the list members. They federate, so you can subscribe to blocklists on other instances. - Edit comments inline, without loading a separate page - wjs018 - Fediverse statistics at https://piefed.social/statistics [https://piefed.social/statistics] - 2-factor authentication (TOTP) - can be added to your account in the ‘Security’ page in your settings. ## For admins - Auto-ban based on the bans that instances you choose, with keyword matching on the ban reason. Go to /admin/users/auto_ban. Try putting ‘piefed.social’ in as the instance and ‘spam’ as the keyword filter. It’ll cut down on the work involved in running your instance SO much. - Voting pattern graph on user profiles to help spot automated voting. - Reset the password of any user. - Lots of inauthentic behaviour reports for finding bots and serial downvoters, see /admin/votes and PM me for an instructional video. It’s a lot to take in but the video will explain it all. ## API - edit matrix user id when saving user profile data. - scheduled post endpoints - wjs018 Plus a lot more bits and pieces, browse the list of recent releases in the 1.8.x line at https://codeberg.org/rimu/pyfedi/releases [https://codeberg.org/rimu/pyfedi/releases] for details. — ## To upgrade from 1.8.x or earlier git pull git checkout v1.9.x Then, ./deploy.sh or ./deploy-docker2.sh — ### Donations PieFed is free and open-source [https://codeberg.org/rimu/pyfedi/src/branch/main/LICENSE#L587] software while operating without any advertising, monetization, or reliance on venture capital. Your donations are vital in supporting the PieFed development effort, allowing us to expand and enhance PieFed with new features. Donations can be made via Patreon [https://www.patreon.com/PieFed], Liberapay [https://liberapay.com/PieFed/] or Ko-fi [https://ko-fi.com/piefed].
(lemmy.world)
Do you understand the meaning of the word deliberate?
That comment doesn't demonstrate whatsoever that rimu "deliberately broke compatibility with pylova".
Do you understand the meaning of the word deliberate?
Of course I do. Do you? How about the word "break"?
Edit: Do you think deliberate means "not intentional"?
-
That comment doesn't demonstrate whatsoever that rimu "deliberately broke compatibility with pylova".
Do you understand the meaning of the word deliberate?
Of course I do. Do you? How about the word "break"?
Edit: Do you think deliberate means "not intentional"?
Oh it only took 5 comments for you to narrow down what your actual issue with my statement is. So your objection is to my usage of the word 'break', then? Nothing else? Why didn't you say so 4 comments ago? And not after you conclusively lost the argument on deliberate?
Rimu deliberately chosing to not be compatible with Pylova’s identical blocklist feature isn’t the best look though.
Better?
-
Oh it only took 5 comments for you to narrow down what your actual issue with my statement is. So your objection is to my usage of the word 'break', then? Nothing else? Why didn't you say so 4 comments ago? And not after you conclusively lost the argument on deliberate?
Rimu deliberately chosing to not be compatible with Pylova’s identical blocklist feature isn’t the best look though.
Better?
Oh it only took 5 comments for you to narrow down what your actual issue with my statement is. So your objection is to my usage of the word ‘break’, then?
No, I just thought you might also not know what that meant. Looks like I was right.
Rimu deliberately chosing to not be compatible with Pylova’s identical blocklist feature isn’t the best look though.
Source for rimu "deliberately chosing to not be compatible with Pylova"? Your previous source was about rimu not intentionally choosing to be incompatible with Pylova. Which is, of course, the exact opposite of your claim.
-
Oh it only took 5 comments for you to narrow down what your actual issue with my statement is. So your objection is to my usage of the word ‘break’, then?
No, I just thought you might also not know what that meant. Looks like I was right.
Rimu deliberately chosing to not be compatible with Pylova’s identical blocklist feature isn’t the best look though.
Source for rimu "deliberately chosing to not be compatible with Pylova"? Your previous source was about rimu not intentionally choosing to be incompatible with Pylova. Which is, of course, the exact opposite of your claim.
No no, I'm done. Thank you for providing a good show for everybody else.
-
Which patch? I'm not gonna dig through the whole git history...
… your hypocrisy is outstanding.
Notice Rimu replaced quokkau’s commits for a ghost profile called rimu and consequently, Shadow is ChatGPT..
Ciao! Sembra che tu sia interessato a questa conversazione, ma non hai ancora un account.
Stanco di dover scorrere gli stessi post a ogni visita? Quando registri un account, tornerai sempre esattamente dove eri rimasto e potrai scegliere di essere avvisato delle nuove risposte (tramite email o notifica push). Potrai anche salvare segnalibri e votare i post per mostrare il tuo apprezzamento agli altri membri della comunità.
Con il tuo contributo, questo post potrebbe essere ancora migliore 💗
Registrati Accedi
Citiverse è un progetto che si basa su NodeBB ed è federato! | Categorie federate | Chat | 📱 Installa web app o APK | 🧡 Donazioni | Privacy Policy