In anticipation of Lemmy’s upcoming 0.19 release, and to work out any final issues, we’re going to deploy a test release on lemmy.ml within the next few days.
We’re doing this testing on lemmy.ml only, so that we can encounter any issues before the release, and to make sure the upgrade process is smooth for other production servers.
Some of the following will happen during the process:
- Apps will likely break (only for lemmy.ml)
- Lemmy.ml may experience some downtime for the upgrade to complete (ideally no more than an hour).
- If anything goes wrong, we may have to restore from a database backup, meaning content made in between backups may be lost.
If all goes well, we’ll have an official announcement for the release after this testing period.
I apologize for the difficulties this might cause. At most this will be a week of hair-pulling, but its vital that we catch any issues before telling other servers to upgrade.
Screw community names, I want instance agnostic URLs for posts and comments.
Right now
lemmy.ml/comment/123456andlemmy.ml/comment/123456are two different comments, and there is no simple way to find one comment on another instance (so you can interact with it from your logged in account). What we should have islemmy.ml/comment/123456@lemmy.worldto point to a comment made on another instance, then you can just change the instance name after the@to find the comment (or post) on any other instance.Comment IDs are not unique between instances so you simply cannot change just the part after the
@to link to the same comment but accessing it from another instance.You can always take the comment’s full URL and put in in the search field of your instance, this will show that particular comment in your instance so you can interact with it from there.
How can two urls that are exactly the same point to different content?
Perhaps they meant something like lemmy.world for the second URL.
Perhaps