Whitehat93875
3w ago
•
100%
Understandable, last I checked it seems very stable on all the other instances that use it.
Just wondering when do you think it'll be possible to upgrade Lemmy.world to 0.19.5. Just curious since I know that 0.19.5 comes with many nice improvements including the ability to delete your own image uploads. As well as many bug fixes.
Whitehat93875
10mo ago
•
66%
Willing to bet that they were probably banned because of disinformative conspiratorial crap like this. Is that not why it was banned on World for a short time?
Whitehat93875
11mo ago
•
100%
Willing to bet they're on Kbin, Kbin favors trolls more than Lemmy does, since they have significantly worse moderation and some kbin instances have no moderation.
Whitehat93875
1y ago
•
100%
Vote manipulation will be tricky to enforce, since votes can come from any Instance due to the whole federation thing, if the user uses the same username on their account it's easy but if not it can be very difficult if not impossible.
cross-posted from: https://lemmy.ml/post/5711722 > We are getting closer to the next major release. This version will have many breaking changes, so we are listing them here for app and client developers to adjust their projects. > > As we prepare for the release of Lemmy `0.19.0`, we'd like to provide any app or client developers ample time to upgrade their apps, as well as discover any problems, before we do the release. This will be **at least 4 weeks from now** (but likely longer). > > Server admins can also upgrade to the latest release candidates for testing. Be aware that they are still unstable and shouldn't be used in production. As with any upgrade it is important to have working backups in place. > > It should be possible for clients to support both Lemmy 0.18 and 0.19 without major workarounds. If backwards compatibility is causing you trouble, comment below and we will help to find a solution. > > To test, you can point your app to the following test instance running a release candidate of `0.19.0`: https://voyager.lemmy.ml > > A diff of API changes is here: [lemmy-js-client API changes from 0.18.3 -> 0.19.0-rc's](https://github.com/LemmyNet/lemmy-js-client/compare/0.18.3...0.19.0-rc.13) > > *Note for developers not using typescript or rust*: > > If you'd like to auto-generate an API client for your language, you can try out [@MV-GH's lemmy_openapi_spec](https://github.com/MV-GH/lemmy_openapi_spec), or (if in kotlin), use Jerboa's [script here](https://github.com/dessalines/jerboa/blob/main/copy_generated_types_from_lemmy_js_client.sh). > > ## Major Changes > > ### Authentication > > Previous Lemmy versions used to take authentication as query/post parameters. This is insecure and unnecessarily complicated. With `0.19`, the `jwt` token can be passed either as cookie with name `auth`, or as header in the form `Authorization: Bearer `. > > A major advantage is that this allows us to send proper cache-control headers, with responses to unauthenticated users being cacheable. It also prevents token leaks in web server logs. The login and registration endpoints attempt to set the cookie automatically. If that is supported on your platform, you don't have to worry about the authentication token at all. > > In order for your client to be compatible with both Lemmy `0.18` and `0.19`, you should send auth in both ways. Meaning with each API call, send the old `auth` query/post parameter, as well as the new header or cookie. > > A few PRs detailing these changes: > > - https://github.com/LemmyNet/lemmy/pull/3725 > - https://github.com/LemmyNet/lemmy/pull/3926 > - https://github.com/LemmyNet/lemmy/pull/3946 > - https://github.com/LemmyNet/lemmy/pull/3982 > > ### Users can block instances > > Users can now block instances, so that their communities are hidden from listings. This is done via `POST /api/v3/site/block` with parameters `int instance_id, bool block`. > > https://github.com/LemmyNet/lemmy/pull/3869 > > ### New sort options > > A new `scaled` sort option has been added. This sort is identical to the `Hot` sort, but also takes into account the number of each community's active monthly users, and so helps to boost posts from *less active* communities to the top. > > https://github.com/LemmyNet/lemmy/pull/3907 > > ### 2FA / TOTP Rework > > Two-Factor-Authentication is now enabled in a two-step process to avoid locking yourself out. Now a secret needs to be generated first with `POST /api/v3/user/totp/generate` (no parameters). The generated token needs to be added by the user to an authenticator app. > > Once this is completed, 2FA can be enabled with `POST /api/v3/user/totp/update`. This takes a string parameter `totp_token` (generated by authenticator app), and boolean `enabled`. 2FA can be disabled again with the same `update` endpoint. Additionally, the 2FA algorithm has been changed to `SHA1` for better compatibility. > > The update disables 2FA for all accounts, so that users who are locked out can use their accounts again, and to ease the transition to the `SHA1` algorithm. > > https://github.com/LemmyNet/lemmy/pull/3959 > > ### Timestamps now include timezone > > Previous Lemmy versions used timestamps without any timezone internally. This caused problems when federating with other software that uses timezones. > > Going forward, all timestamps in the API are switching from timestamps without time zone (`2023-09-27T12:29:59.113132`) to `ISO8601` timestamps (e.g. `2023-10-29T15:10:51.557399+01:00` or `Z` suffix). In order to be compatible with both 0.18 and 0.19, parse the timestamp as `ISO8601` and add a `Z` suffix if it fails (for older versions). > > https://github.com/LemmyNet/lemmy/pull/3496 > > ### 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. > > https://github.com/LemmyNet/lemmy/pull/3872 > > ### New endpoints for export/import of user settings data > > Users can now export their profile settings data (including subscriptions and blocklists) via `GET /api/v3/user/export`. The returned JSON data should not be parsed by clients, but directly downloaded as a file. Backups can be imported via `POST /api/v3/user/import`. > > https://github.com/LemmyNet/lemmy/pull/3976 > > ### Make remove content optional during account deletion > > When a user deletes their own account using `POST /api/v3/user/delete_account`, there is a new parameter called `delete_content`. If it is true, all posts, comments and other content created by the user are deleted (this is the previous default behaviour). If it is false, only the user profile will be marked as deleted. > > https://github.com/LemmyNet/lemmy/pull/3817 > > ### Outgoing Federation Queue > > The federation queue has been rewritten to be much more performant and reliable. This is irrelevant for client developers, but admins should look out for potential federation problems. If you run multiple Lemmy backends for horizontal scaling, be sure to read the [updated documentation](https://join-lemmy.org/docs/administration/horizontal_scaling.html) and set the new configuration parameters. The [Troubleshooting](https://join-lemmy.org/docs/administration/troubleshooting.html) section has information about how to find out the state of the federation queues. > > https://github.com/LemmyNet/lemmy/pull/3605
cross-posted from: https://lemmy.ml/post/5711722 > We are getting closer to the next major release. This version will have many breaking changes, so we are listing them here for app and client developers to adjust their projects. > > As we prepare for the release of Lemmy `0.19.0`, we'd like to provide any app or client developers ample time to upgrade their apps, as well as discover any problems, before we do the release. This will be **at least 4 weeks from now** (but likely longer). > > Server admins can also upgrade to the latest release candidates for testing. Be aware that they are still unstable and shouldn't be used in production. As with any upgrade it is important to have working backups in place. > > It should be possible for clients to support both Lemmy 0.18 and 0.19 without major workarounds. If backwards compatibility is causing you trouble, comment below and we will help to find a solution. > > To test, you can point your app to the following test instance running a release candidate of `0.19.0`: https://voyager.lemmy.ml > > A diff of API changes is here: [lemmy-js-client API changes from 0.18.3 -> 0.19.0-rc's](https://github.com/LemmyNet/lemmy-js-client/compare/0.18.3...0.19.0-rc.13) > > *Note for developers not using typescript or rust*: > > If you'd like to auto-generate an API client for your language, you can try out [@MV-GH's lemmy_openapi_spec](https://github.com/MV-GH/lemmy_openapi_spec), or (if in kotlin), use Jerboa's [script here](https://github.com/dessalines/jerboa/blob/main/copy_generated_types_from_lemmy_js_client.sh). > > ## Major Changes > > ### Authentication > > Previous Lemmy versions used to take authentication as query/post parameters. This is insecure and unnecessarily complicated. With `0.19`, the `jwt` token can be passed either as cookie with name `auth`, or as header in the form `Authorization: Bearer `. > > A major advantage is that this allows us to send proper cache-control headers, with responses to unauthenticated users being cacheable. It also prevents token leaks in web server logs. The login and registration endpoints attempt to set the cookie automatically. If that is supported on your platform, you don't have to worry about the authentication token at all. > > In order for your client to be compatible with both Lemmy `0.18` and `0.19`, you should send auth in both ways. Meaning with each API call, send the old `auth` query/post parameter, as well as the new header or cookie. > > A few PRs detailing these changes: > > - https://github.com/LemmyNet/lemmy/pull/3725 > - https://github.com/LemmyNet/lemmy/pull/3926 > - https://github.com/LemmyNet/lemmy/pull/3946 > - https://github.com/LemmyNet/lemmy/pull/3982 > > ### Users can block instances > > Users can now block instances, so that their communities are hidden from listings. This is done via `POST /api/v3/site/block` with parameters `int instance_id, bool block`. > > https://github.com/LemmyNet/lemmy/pull/3869 > > ### New sort options > > A new `scaled` sort option has been added. This sort is identical to the `Hot` sort, but also takes into account the number of each community's active monthly users, and so helps to boost posts from *less active* communities to the top. > > https://github.com/LemmyNet/lemmy/pull/3907 > > ### 2FA / TOTP Rework > > Two-Factor-Authentication is now enabled in a two-step process to avoid locking yourself out. Now a secret needs to be generated first with `POST /api/v3/user/totp/generate` (no parameters). The generated token needs to be added by the user to an authenticator app. > > Once this is completed, 2FA can be enabled with `POST /api/v3/user/totp/update`. This takes a string parameter `totp_token` (generated by authenticator app), and boolean `enabled`. 2FA can be disabled again with the same `update` endpoint. Additionally, the 2FA algorithm has been changed to `SHA1` for better compatibility. > > The update disables 2FA for all accounts, so that users who are locked out can use their accounts again, and to ease the transition to the `SHA1` algorithm. > > https://github.com/LemmyNet/lemmy/pull/3959 > > ### Timestamps now include timezone > > Previous Lemmy versions used timestamps without any timezone internally. This caused problems when federating with other software that uses timezones. > > Going forward, all timestamps in the API are switching from timestamps without time zone (`2023-09-27T12:29:59.113132`) to `ISO8601` timestamps (e.g. `2023-10-29T15:10:51.557399+01:00` or `Z` suffix). In order to be compatible with both 0.18 and 0.19, parse the timestamp as `ISO8601` and add a `Z` suffix if it fails (for older versions). > > https://github.com/LemmyNet/lemmy/pull/3496 > > ### 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. > > https://github.com/LemmyNet/lemmy/pull/3872 > > ### New endpoints for export/import of user settings data > > Users can now export their profile settings data (including subscriptions and blocklists) via `GET /api/v3/user/export`. The returned JSON data should not be parsed by clients, but directly downloaded as a file. Backups can be imported via `POST /api/v3/user/import`. > > https://github.com/LemmyNet/lemmy/pull/3976 > > ### Make remove content optional during account deletion > > When a user deletes their own account using `POST /api/v3/user/delete_account`, there is a new parameter called `delete_content`. If it is true, all posts, comments and other content created by the user are deleted (this is the previous default behaviour). If it is false, only the user profile will be marked as deleted. > > https://github.com/LemmyNet/lemmy/pull/3817 > > ### Outgoing Federation Queue > > The federation queue has been rewritten to be much more performant and reliable. This is irrelevant for client developers, but admins should look out for potential federation problems. If you run multiple Lemmy backends for horizontal scaling, be sure to read the [updated documentation](https://join-lemmy.org/docs/administration/horizontal_scaling.html) and set the new configuration parameters. The [Troubleshooting](https://join-lemmy.org/docs/administration/troubleshooting.html) section has information about how to find out the state of the federation queues. > > https://github.com/LemmyNet/lemmy/pull/3605
cross-posted from: https://lemmy.ml/post/5711722 > We are getting closer to the next major release. This version will have many breaking changes, so we are listing them here for app and client developers to adjust their projects. > > As we prepare for the release of Lemmy `0.19.0`, we'd like to provide any app or client developers ample time to upgrade their apps, as well as discover any problems, before we do the release. This will be **at least 4 weeks from now** (but likely longer). > > Server admins can also upgrade to the latest release candidates for testing. Be aware that they are still unstable and shouldn't be used in production. As with any upgrade it is important to have working backups in place. > > It should be possible for clients to support both Lemmy 0.18 and 0.19 without major workarounds. If backwards compatibility is causing you trouble, comment below and we will help to find a solution. > > To test, you can point your app to the following test instance running a release candidate of `0.19.0`: https://voyager.lemmy.ml > > A diff of API changes is here: [lemmy-js-client API changes from 0.18.3 -> 0.19.0-rc's](https://github.com/LemmyNet/lemmy-js-client/compare/0.18.3...0.19.0-rc.13) > > *Note for developers not using typescript or rust*: > > If you'd like to auto-generate an API client for your language, you can try out [@MV-GH's lemmy_openapi_spec](https://github.com/MV-GH/lemmy_openapi_spec), or (if in kotlin), use Jerboa's [script here](https://github.com/dessalines/jerboa/blob/main/copy_generated_types_from_lemmy_js_client.sh). > > ## Major Changes > > ### Authentication > > Previous Lemmy versions used to take authentication as query/post parameters. This is insecure and unnecessarily complicated. With `0.19`, the `jwt` token can be passed either as cookie with name `auth`, or as header in the form `Authorization: Bearer `. > > A major advantage is that this allows us to send proper cache-control headers, with responses to unauthenticated users being cacheable. It also prevents token leaks in web server logs. The login and registration endpoints attempt to set the cookie automatically. If that is supported on your platform, you don't have to worry about the authentication token at all. > > In order for your client to be compatible with both Lemmy `0.18` and `0.19`, you should send auth in both ways. Meaning with each API call, send the old `auth` query/post parameter, as well as the new header or cookie. > > A few PRs detailing these changes: > > - https://github.com/LemmyNet/lemmy/pull/3725 > - https://github.com/LemmyNet/lemmy/pull/3926 > - https://github.com/LemmyNet/lemmy/pull/3946 > - https://github.com/LemmyNet/lemmy/pull/3982 > > ### Users can block instances > > Users can now block instances, so that their communities are hidden from listings. This is done via `POST /api/v3/site/block` with parameters `int instance_id, bool block`. > > https://github.com/LemmyNet/lemmy/pull/3869 > > ### New sort options > > A new `scaled` sort option has been added. This sort is identical to the `Hot` sort, but also takes into account the number of each community's active monthly users, and so helps to boost posts from *less active* communities to the top. > > https://github.com/LemmyNet/lemmy/pull/3907 > > ### 2FA / TOTP Rework > > Two-Factor-Authentication is now enabled in a two-step process to avoid locking yourself out. Now a secret needs to be generated first with `POST /api/v3/user/totp/generate` (no parameters). The generated token needs to be added by the user to an authenticator app. > > Once this is completed, 2FA can be enabled with `POST /api/v3/user/totp/update`. This takes a string parameter `totp_token` (generated by authenticator app), and boolean `enabled`. 2FA can be disabled again with the same `update` endpoint. Additionally, the 2FA algorithm has been changed to `SHA1` for better compatibility. > > The update disables 2FA for all accounts, so that users who are locked out can use their accounts again, and to ease the transition to the `SHA1` algorithm. > > https://github.com/LemmyNet/lemmy/pull/3959 > > ### Timestamps now include timezone > > Previous Lemmy versions used timestamps without any timezone internally. This caused problems when federating with other software that uses timezones. > > Going forward, all timestamps in the API are switching from timestamps without time zone (`2023-09-27T12:29:59.113132`) to `ISO8601` timestamps (e.g. `2023-10-29T15:10:51.557399+01:00` or `Z` suffix). In order to be compatible with both 0.18 and 0.19, parse the timestamp as `ISO8601` and add a `Z` suffix if it fails (for older versions). > > https://github.com/LemmyNet/lemmy/pull/3496 > > ### 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. > > https://github.com/LemmyNet/lemmy/pull/3872 > > ### New endpoints for export/import of user settings data > > Users can now export their profile settings data (including subscriptions and blocklists) via `GET /api/v3/user/export`. The returned JSON data should not be parsed by clients, but directly downloaded as a file. Backups can be imported via `POST /api/v3/user/import`. > > https://github.com/LemmyNet/lemmy/pull/3976 > > ### Make remove content optional during account deletion > > When a user deletes their own account using `POST /api/v3/user/delete_account`, there is a new parameter called `delete_content`. If it is true, all posts, comments and other content created by the user are deleted (this is the previous default behaviour). If it is false, only the user profile will be marked as deleted. > > https://github.com/LemmyNet/lemmy/pull/3817 > > ### Outgoing Federation Queue > > The federation queue has been rewritten to be much more performant and reliable. This is irrelevant for client developers, but admins should look out for potential federation problems. If you run multiple Lemmy backends for horizontal scaling, be sure to read the [updated documentation](https://join-lemmy.org/docs/administration/horizontal_scaling.html) and set the new configuration parameters. The [Troubleshooting](https://join-lemmy.org/docs/administration/troubleshooting.html) section has information about how to find out the state of the federation queues. > > https://github.com/LemmyNet/lemmy/pull/3605
Whitehat93875
1y ago
•
100%
Just a heads up, this person is a known troll across lemmy they're well known for their hostile and inflammatory content and just saying things to get a rise out of people, this person also isn't exactly receptive to feedback. Just wanted to let you know since trying to talk with someone like this is like talking to a brick wall.
Whitehat93875
1y ago
•
100%
He's always like this unfortunately.
Whitehat93875
1y ago
•
100%
You were banned because you were arguing for why people shouldn't be arrested for possession of CSAM material, trolling and straw-manning in the replies, and on top of that attempting to seriously and honestly advocate for pedophiles on another community, which is at best borderline illegal (anyone can check the modlog on that one if they don't believe me, I wouldn't make such claims if they weren't true).
So to summerize you were banned for
- Trolling
- Promoting Illegal Activities (Pedophilla and CSAM)
Whitehat93875
1y ago
•
75%
I have not clue, people can be quite toxic and horrible. Also noticed that they reduced his ban, not sure why, defending pedophilia is pretty bad and definitely carries legal risk but it's not my call to make.
Whitehat93875
1y ago
•
100%
Do people think that someone has to use the same email address, or the same username? If someone uses a different email, username, and IP address (don't try and argue semantics it can, always can, and always has been done) then whatever you put into the list can't be applied to them.
Even if you ask for IDs people can fake those, it's illegal sure but so is what these assholes did and it didn't really stop them now did it.
Whitehat93875
1y ago
•
80%
They were banned because they were defending pedophilia (advocating for them to be able to get off to what turns them on) and also trolling very aggressively. You can look at them in the Modlog on the Website, not sure if Apps implement the modlog yet though.
Whitehat93875
1y ago
•
100%
That's good then, was worried for a sec that people could upload images without having an account, that would be very bad and make these kind of attacks insanely easy.
Whitehat93875
1y ago
•
100%
I would definately agree that this would very likely count as cyber terrorism, and if it doesn't it should.
Whitehat93875
1y ago
•
100%
I had no idea how right I was at the time I commented that, since I hadn't scrolled far back enough in his comment history but yeah, way more right than I would've liked 😬
Whitehat93875
1y ago
•
100%
Matrix is a secure chat protocol used by the Devs to message eachother.
A pull request is a way of proposing and contributing code on git-based platforms like github, gitlab, and codeberg.
Whitehat93875
1y ago
•
100%
🤓
Whitehat93875
1y ago
•
100%
Wait I noticed that there's an image button in the application form, is there any risk that that might be abused by users passing by to upload to pictrs in registrations without an account? That could be a big problem if they could.
Whitehat93875
1y ago
•
100%
Lol you do realize blocking on Lemmy means to ignore them, it's not going to silence them or more critically prevent them from downvoting or reporting you like it does on Reddit.
You're just going to stop seeing them, they can keep calling you out for it. You just made it easier for them.
Whitehat93875
1y ago
•
87%
Oh by the way, MAP stuff really doesn't look good on you (that's in your comment history). Yeah maybe you think I'm a terrible person because I think drugs should be treated less harshly but you have literally said in other comments that Pedophiles should be allowed to get off on what turns them on (which I remind you is exploitation of Minors). That is a very different stance than people shouldn't be beaten and arrested for snorting coke, you're literally advocating for people to be allowed to produce and consume abuse material and claiming that it's acceptable for people to be pedophiles, and pursue their attractions instead of getting help. I don't know how you don't see what is wrong with that. Like seriously this is either really bad trolling (way too far) or, you're one of them.
Too bad, I’m “kid agnostic”; they might as well be cars or dragons —drawn or otherwise—, I don’t care whether they’re “kid” or “grownup” cars or dragons.
I think I now know which one it is if that statement from the horse's mouth is to be believed...
Whitehat93875
1y ago
•
100%
🤓
Whitehat93875
1y ago
•
83%
FBI doesn't use pitchforks bud, they have tasers and guns.
Hello I am writing this post because I stumbled across this instance which allows and hosts loli material (which can be classified as CSAM) as per their rules: >The above explicitly does not include drawings, often referred to collectively as “loli”. As these types of sexual depictions of Minors are illegal in many countries it is important that we defederate them as soon as possible to avoid cross-hosting such content on this service. I understand how people feel about defederation but this is not based on opinions or politics but rather an issue related to illegal content, and this content is illegal in countries where the Server is hosted, where the hosting company is located, and where several of the Admins live so this issue should not be taken lightly.