I just opened an issue about it: https://github.com/LemmyNet/lemmy/issues/4744
Lemmy maintainer
I just opened an issue about it: https://github.com/LemmyNet/lemmy/issues/4744
This, particularly reports are not fully federated.
It was always normalized, but recently there seems to be more backlash from maintainers.
Well written, it would deserve a separate post.
One of the comments mentions that another app can trigger search through an Android intent. So its better to be safe and close any potential vulnerabilities, but this doesnt seem particularly useful for an attacker.
Im a former contributor to F-Droid with various merged pull requests. Looking at the indicated pull request I really doubt that it was an intentional attack. First of all its easy to forget for a new developer to escape SQL parameters, and the docs dont even mention a risk of SQL injection attacks. And of the users pushing for the PR to be merged, one is a long-time F-Droid contributor, and the other also looks like a real human with many contributions in other repos, so no sockpuppets in sight.
It simply looks like standard open source behaviour, for better or for worse. A new user makes a contribution for a highly demanded feature, and users want it to get merged as soon as possible. Maintainers are discussing the big picture of the change and want to avoid breaking changes, without getting into code review yet. The new contributor seems unwilling to make any design changes to his PR, and gets frustrated that it doesnt get merged as is. The potential vulnerability is only noticed half a year after the PR was opened, at which point it was already de facto abandoned. So not an attack, but simply a developer who is new to open source and doesnt understand how the process works.
We applied for funding last August, but unfortunately we are still waiting for it to be finalized. Seems like NLnet is quite overloaded these days.
We only do major versions around once a year so those could still be named, while using numbers for minor versions. Lemmy is more user-facing than react, so it would make sense to have a more user-friendly versioning.
500 Mb symmetrical. It’s more than enough even while running a home server.
Admins and mods can see this in the latest version.
This is already possible.
Has Google never heard of CI to perform such checks?
You could probably make this as a custom lemmy frontend. The main functionality is almost identical.
Im working on this under the name of Ibis. Hopefully I can announce the first release within a few weeks.
Feel free to make open an issue to improve instance blocking. Or better yet a pull request. We are only a few devs with limited time, and hundreds of issues to work on.
There are plenty of Wikipedia articles which are not objective, particularly when it comes to politics or history. Of course federation means there would be many different wikis. That makes sense, for example different countries should have their own independent wikis, instead of using one controlled by a different nation.
Wikipedia has very major problems, but almost nobody is aware of them. Give this article a read to get an idea.
You will have to wait for 0.19 to disable it. Pictrs 0.5 will also add a way to clear old images. See the issue: https://github.com/LemmyNet/lemmy/issues/4053
The activities table is cleared out automatically every week, items older than 3 months are deleted. During the update only a smaller number of rows was migrated so the db temporarily was slower. You can manually clear older items in sent_activity
and received_activity
to free more space.
Actually Im wrong about images, turns out that all remote images are mirrored locally in order to generate thumbnails. 0.19 will have an option to disable that. This could use more improvements, the whole image handling is rather confusing now.
Alright Ive added @[email protected], @[email protected] and @[email protected] as mods and removed the inactive ones.