Lemmy maintainer. Interested in politics, video games, and many other things.
- 68 Posts
- 781 Comments
As far as i can tell, the only difference is that the deleted comments from MyLin are missing on lemmy.ml. That could be a problem with Mastodon federation, but anyway it shouldnt matter much.
Hmm i was inspecting the HTML in Firefox, but if i curl the source and look at it directly, it looks quite different, with a <title> element in the <body> as you say. @dessalines@lemmy.ml can you look into this?
Storage requirements depend entirely on the amount of images that users upload. In case of slrpnk.net, there are currently 1.6 GB of pictrs data. You can also use s3 storage, or something like sshfs to mount remote storage.
You are wrong, it uses the title attribute which is valid html, and not the title element. Maybe Lynx doesnt support that attribute on a elements, I dont know.
Btw you need to add a newline after each quote so that its rendered correctly as markdown.
Pictrs (image hosting software which we use for Lemmy) supports s3 as storage backend, so you could use that. However, migrating from local disk storage to s3 storage is currently not working and is being fixed. You might want to get in contact with the dev (asonix), hes very helpful.
The reason I recommended sshfs is that you can use it with any server, or even a desktop or raspberry pi. This approach is much cheaper than s3 afaik.
La unica instancia española que conozco es forum.nobigtech.es, pero esta muerta.
Your best option might be to setup sshfs to mount a folder from another server, and use that to store images.
https://www.cyberciti.biz/faq/how-to-mount-remote-directory-filesystems-with-sshfs-on-linux/
This will usually be rather slow, so you should also setup a cache for images in nginx.
That sounds overly complicated. Why do you open Lemmy in your browser, when you can directly connect with your client to the API of any instance?
And if you do use the browser, theres the fedilink icon which has the link you need. If that isnt rendered properly in your browser, send me the details and i can open an issue for you.
If you are writing a client, there is really no reason to browse instances using browser/lemmy-ui. Instead you can directly connect with your client to the api of any instance. Then when you want to interact with any object (eg vote, write a post, subscribe), you take the value of ap_id field (on post, comment) or actor_id field (user, community, site), and pass that to resolve_object.
What resolve_object does is essentially the command below, and then transform the data to store it in Lemmy db. Note that each fetchable object has an id, and that is where you can resolve it.
curl -H 'Accept: application/activity+json' https://lemmy.ml/post/472799 | jq
https://lemmy.perthchat.org/api/v3/resolve_object?q=https://lemmy.ml/post/472799
This fails because it was posted on lemmygrad.ml, which is blocked on perthchat.
To fetch comments, the url should look like this: https://sopuli.xyz/comment/104283
Im really losing track what you are arguing here. If you want to change the site rules of lemmy.ml, you should specifically suggest what the new rule(s) should be, and explain how that would improve the instance. Otherwise there is no point in continuing this discussion.
But to be honest, you are not even registered on this instance, so I dont think you should have any right to influence the rules here.
- •
- hilabete bat
- •
- •
- github.com
- •
- 2 hilabete
- •
- •
- 3 hilabete
- •
- •
- 3 hilabete
- •
- •
- 6 hilabete
- •
- •
- 7 hilabete
- •
- •
- weblate.yerbamate.ml
- •
- 10 hilabete
- •
- •
- 10 hilabete
- •
I think thats just the number of websocket connections, so its possible that someone is browsing the site without login. Or you might have it open on multiple devices or multiple tabs.