What phone do you have? I just upgraded last night and everything appears to be working like normal. But I did notice that you appear to have a smaller screen size than I do. First I’d try adjusting the display size and see if that helps. You can find that setting (on a pixel) under: Settings -> Display -> Display Size and Text.

You can also try adjusting the accessibility settings and increase or decrease the font size to see if that helps. Which you can find in the same menu above.

Lastly, you might try enabling developer settings and adjusting the smallest width:

Edit: none of these should be final solutions but to help troubleshoot what’s wrong. You can then use what you find with these three options to raise a ticket and hopefully the developers can then narrow down the actual root cause.

https://github.com/LemmyNet/lemmy/blob/d909f3455ddb89d45f35c78c4ce96bd0896469b1/crates/api_common/src/utils.rs#L302

If the honeypot is set the request is simply discarded.

FYI: https://en.m.wikipedia.org/wiki/Honeypot_(computing)

But there should also be a separate endpoint to get an auth token. (I don’t remember it off the top of my head). Then your bot should store that somewhere and send it as the auth parameter in every request.

You can always try constructing the URL manually. I know this sucks, but it might be a workaround.

https://lemmy.ml/c/[email protected]

Long story short you just have to go to lemmy.ml and then add /c/ followed by the community name @ the instance it belongs to.

The one that begins with https is obviously just a full URL and will take the user directly to that instance rather than staying on their home instance. And the one that starts with /c/ is a relative path. While it might work, if the community/user it points to is on the same server as the user, they might encounter errors as it might try and navigate to https://lemmy.world/c/[email protected] which is undefined (may or may not work).

I don’t know of any documentation off the top of my head but currently there’s

User links: @marsara9@lemmy.word

These will translate to https://<your instance>/u/marsara[email protected] assuming your not on lemmy.word. If you are it will just be https://lemmy.word/u/marsara9.

And community links: !fediverse@lemmy.world

These will follow the same pattern but will have /c/ instead of /u/.

There’s been proposals to add others but that’s all that exists at the moment.

Problem is finding the difference between repost bots and bots that are helpful like automod and link redirectors.

Maybe. 2nd idea I’ve got is that if no one is replying after say 24hrs and something like 75-80% of your posts are as such and you have at least 100 such posts, you get added to the list?

Main concern I see about something like this is false positives and how someone real could end up getting blocked.

I definitely want to think on this some more but it might have some legs.

…I wonder if there’s a programmatic way to detect these bots? Some sort of analysis on their posting behavior?

If they’re playing nice they’ll have the bot flag checked in their profile, and then maybe build a list of any bot that creates posts? As most of the “good” bots just reply to comments? Anyway just thinking out loud. But I’m thinking I could easily add a public API to my search engine that just returns a list of “posting bots”…

The target folder may be quite large. You can look at the dependencies for my project but my end binary is only a few MB.

I don’t see anything wrong initially. Can you also test with something like postman? It’ll allow you to control the headers etc… that you send.

You can also compare to what I have here and see if that helps: https://github.com/marsara9/lemmy-search/blob/b6c88355aba49abca52862473650526821ee165a/server/src/api/lemmy/fetcher.rs#L123

Not that I’m aware of. I already opened a request on the backend to have an API to provide a since= property. But ultimately found a workaround for my needs (not applicable here).

Last I checked AWS is a fairly expensive option to host a Lemmy instance. You can still do it, but there’s much cheaper options out there.

I know this doesn’t answer your question really but may explain why there isn’t a lot of details on using AWS as a host.

Thanks for the callout. For anyone using that site, I have a list of bugs I’m hoping to get fixed in the next couple days that should fix a lot of the major issues (broken links, etc…).

The project is open source so you can see what they are logging, if you can read the code.

But simply some things that are logged:

• IPs are logged but I don’t see them being associated with a user account. This looks to mainly be for rate limiting.
• What posts/comments you’ve looked at are logged. This is so the UI can gray out posts you’ve already seen or mark replies to you own comments as read.

From what I can tell neither of these data points are federated so only the instance your logged into has that information.

** Don’t use this as an exhaustive list. These are just the two items you specifically asked about and what I’ve seen looking through the code so far. **

HTML + JavaScript frontend. Rust backend with a postgres database.

It’ll be open sourced once I can get the MVP ready.

Would the canonical tag make any sense for Lemmy? The problem is, if you search for something your preferred site / URL is your instance. So the canonical would be different for every user?

I’m using the public API to grab every post / comment and then I essentially replace the content with only the unique words. Then when you go to search it just looks for any post or comment, in my database, that has the words you typed in. Finally I sort based on the number of upvotes.

Right now it only craws a specific instance that you point it to. But as long as that instance is federated it /should/ get everything. But eventually I plan on using that instance’s list of federated instances to scan everything and lighten the load on any one particular instance.

Edit: I thought about tapping into the existing database but the existing database is more geared towards serving content but not necessarily searching. The database that I’m building you can search but I drop so much of the original data that using it for content is worthless.

I’m doing tests in the next couple days. But I’m trying to build a search engine specifically for Lemmy.

• It should in theory work similar-ish to Google / Bing.
• You can filter by instance, community or author.
• it only indexes Lemmy posts and it won’t keep duplicates.
• It’ll also open any link you find in your instance.
• You’ll be able to self host it and point it to any instance you want as well.

I’m hoping I can open it to the public in a week or so.