eviltoast.org has been upgraded to lemmy and lemmy-ui 0.18.1. Release notes copied below.
Release v0.18.1 Release · LemmyNet/lemmy · GitHub
What’s Changed
- Remove
actix_rt& use standard tokio spawn by @cetra3 in #3158- Add TLS support for diesel-async database connections by @sunaurus in #3189
- after 30 days, replace comment.content and post.body with ‘Deleted’ by @vijaykramesh in #3208
- Add separate Post check for is_valid_body_field by @Neshura87 in #3263
- feat: allow all admins to purge content by @TKilFree in #3271
- Update DB local_user.theme type to text by @scme0 in #3266
- Allow wildcard imports in schema.rs by @Nutomic in #3293
- Leave no apk cache in Docker image by @PeterDaveHello in #3327
- Fix lemmy UI environment variable in docker-compose.yml by @aman207 in #3299
- Respond with
Content-Type: application/activity+jsonby @perillamint in #3353- Add Liftoff to README.md by @wiki-me in #3357
- Adjust the config check to be a separate faster to compile binary by @cetra3 in #3313
- Compress API responses by @dullbananas in #3343
- Site Metadata: resolve relative URLs for embedded images/videos by @orottier in #3338
- Item URL should point to post URL by @simmel in #3345
- Remove networks from docker-compose.yml by @Nutomic in #3356
- Fetch community outbox and moderators in parallel by @Nutomic in #3360
- Feature add three six and nine months options backend by @c-andy-candies in #3226
- Hot rank update batching + deadlock avoidance by @sunaurus in #3175
- Fixing the release script. by @dessalines in #3295
- Limit password resets by @sunaurus in #3344
- feat: re-added captcha checks by @TKilFree in #3289
- Add “show_nsfw” to the Community API. by @tgxn in #3363
- Fixes #2900 - Checks slur regex to see if it is too permissive by @ninanator in #3146
- Run cargo update as part of release script by @Nutomic in #3369
- Remove redundant calls to
Iterator::collectby @dullbananas in #3365- docs(api): Add api-common info on generating TypeScript bindings by @Kissaki in #3330
- Fix missing sorting types by @c-andy-candies in #3370
- Fix cargo warnings by @sunaurus in #3397
- Update activitypub-federation crate to 0.4.5 (fixes signature expiration) by @Nutomic in #3379
- Added gitattributes to normalize all files to lf by @njshockey in #3386
- Fixing release script. by @dessalines in #3398
- Automatically manage database when running scripts/test.sh by @dullbananas in #3389
- Fix concatenation of audio captcha wav files by @minorninth in #3350
- Update federated posts to not cache sensitive images if not allow by local site by @lemmus-org in #3253
- Improve errors / debugging by not stripping, log trace if requested by @phiresky in #3425
- Fix: added missing quotes to max-file in docker-compose.yml by @drumlinish in #3442
- Remove PerformApub trait by @Nutomic in #3423
- Mark follow as pending when subscribing to remote community (fixes #3384) by @Nutomic in #3406
- Use serde(skip) instead of skip_serializing, add placeholder values by @Nutomic in #3362
- Add awesome-lemmy to LemmyNet? by @dbeley in #3413
- Fix awesome-lemmy owner by @dbeley in #3469
- Add Open links in new tab setting by @Dogeek in #3318
- Dont compare db string errors (fixes #1393) by @Nutomic in #3424
- Adding rest of community sorts. Fixes #3374 by @dessalines in #3376
- Remove excessive content_type header configuration by @perillamint in #3470
- Do not decrement comment score twice when removing then deleting. by @JPMoresmau in #3196
- 300 comment limit. by @dessalines in #3306
- Remove not needed anymore http-signature-normalization-actix dependency by @pijuszczyk in #3458
- Fixing clippy. by @dessalines in #3471
- Improved validation of display names (Fixes #3436) by @Josephos in #3437
- fix(posts): return error on invalid community name by @Dhawos in #3418
- Add feature for enabling json logging by @lemmus-org in #3462
- Adding a person.admin index, and featured_local/community indexes. by @dessalines in #3479
- Add Prometheus endpoint and metrics by @andybug in #3456
- Cache federation blocklist by @Nutomic in #3486
- improve performance of community followers inbox query by @phiresky in #3482
- upgrade markdown-it to fix panic by @phiresky in #3490
- Use fixed prettier version for CI by @Nutomic in #3507
- Fixes wrong community moderator ordering. by @dessalines in #3495
- Make sure hot rank sorts for post and community filter by positive hot ranks. by @dessalines in #3497
- Allow cross-origin requests by @diamondburned in #3421
- Change security contact mail by @Nutomic in #3506
- Only allow http(s) scheme for urls (ref #3505) by @Nutomic in #3508
- improve admin and mod check to not do seq scans and return unnecessary data by @phiresky in #3483
- Update prettier to 3.0.0 by @dessalines in #3509
- Upgrade crossbeam-channel by @Nutomic in #3512
- Make hot rank not crash on future by @phiresky in #3517
- Revert “Make sure hot rank sorts for post and community filter by positive hot ranks.” by @dessalines in #3521
Yup, it’s one of the main downsides so far. There’s not really a good built in way to discover remote communities yet.
There’s the lemmyverse link and a few similar apps that all aggregate communities into one list, using one of those is easiest imo for now.
I think I can finish the script I was working on to import all or most communities so that they show up in the search results, but the subscriber count will still only reflect the local users and not the real count.
Got it. Thanks. I’m still learning a lot about how this works. It is a bit confusing!
Sorry if this is a dumb question, but how do I subscibe to communities that don’t show up in the search here? I can’t figure it out.
Edit: nvm i got it. Yea if you could just pull in all communities with users over like 15 or so, that would be great!
Wait something is still weird. I’m not seeing comments on other communities that I manually added. I can see them if i visit the instance directly but not through evil toast when loged in. Do you know what’s going on?
As far as I’ve seen so far, posts and comments only start showing up from the time you subscribe to a community. When you manually search for a specific community and subscribe to it, I think it does pull the last 20 or so posts, but not the comments for those posts. There’s no backfill or history fetching in lemmy.
The script I’m using to pull in popular communities is the same as searching for each community it finds, so it doesn’t actually subscribe or pull posts either. I might try that for a few days though and see what happens, I’m not sure how much it’d cause the disk or network to explode.
Wait let me get this straight. If i subscribe to a large community, it only pulls in the last few comments and then it shows comments going forward? It doesn’t show historical comments?
Is this by design of Lemmy? If so, that sounds like an odd design? Like say I join a techsupport community and I’m trying to search for how to fix something. I won’t be able to see all the old helpful comments unless I search for it on the actual instance it’s hosted on while NOT logged into an account on eviltoast? Seems like an odd design choice? Is it designed this way because Lemmy is still scaling and the devs didn’t want to overwhelm small instances with data?
You’ve got it right, I agree is kind of weird, but it looks like it is by design (so far): https://github.com/LemmyNet/lemmy/issues/2825
I’m waiting for some sort of “remote” search, I think that’d solve a lot of weird issues if we could get results from more than just the local instance.
Yea. I just don’t see how lemmy can possibly be a replacement to Reddit unless it pulls in historical comments/posts.
I agree. In its current form, it’s somewhat more similar to something like twitter (or mastodon) vs reddit, at least for newer small instances. I doubt they’ll make it so everything gets federated everywhere by default since that’d be pretty bandwidth and disk intensive, but it’d make sense to at least be able to show those historical threads.
https://www.search-lemmy.com is trying to index all lemmy instances. https://github.com/marsara9/lemmy-search/issues/20 is open to track opening those search results inside your home lemmy instance. Maybe lemmy-ui or one of the other frontends will end up integrating with it so that you can search for anything and have it pull the results into the instance you’re using?
Also it incentivizes people to join really large old instances like lemmy.world or lemmy.ml rather than new smaller instances like yours. That isn’t right…