

Full post is visible from lemmy.world, too: https://lemmy.world/post/2064026


Full post is visible from lemmy.world, too: https://lemmy.world/post/2064026


Yeah, better use the linter too, that way it’s limited to 80 characters


What Dart looks like when written by ActionScript programmers


I didn’t think we would have ads so soon on Lemmy, lol


which suggests a lookup table
No, it only suggests an additional field in the Post table
since there’s no assurance that any instance is aware of any other instance
It already works like that, but slightly worse because post IDs aren’t the same across instances. If you search a newly-created community from another instance here, you just won’t find it until it’s synced, despite its URI being unique.
Thinking about it, it would be possible to have an URI for posts like post:${id}@instance.com, similar to how user URIs and community URIs are made. This way, you could open /post/1772651 on lemmy.world or post:1772651.world on, idk, lemmy.blahaj.zone or something.


And the post on lemmy.world: https://lemmy.world/post/1086238
I think we need UUIDs so we can reference posts across instances
Yeaaah if this community is going to get stale, older than my mom moldy reposts first thing in then I’d rather dip out of that one for now


I’m trying out an Android client as well - https://github.com/dessalines/jerboa
It seems to work well. I’d be interested in making a client myself, but it’s a lot of work!
Seems dead