Conversation
monsieuricon

K. Ryabitsev

I'm considering an archiving scheme for social.kernel.org that would automatically add all public statuses to a public-inbox archive -- not right away, but maybe after a month or so. This should allow us to remove them from the database while still keeping them publicly accessible. From what I've read elsewhere, pleroma's database backend organization is not great, so after a while they start to experience database performance problems. Removing old entries should allow us to avoid this fate while still preserving the conversation record.
1
1
3
vbabka

Vlastimil Babka

Reply to @monsieuricon
@monsieuricon it would be great if bookmarks survived that archiving, i.e. a redirect from the original status url to the archived. But dunno how exactly bookmarks are stored (might be an issue if as a reference in the same db? and what if it's another federated instance user bookmarking a post from here?) and if clients wouldn't become confused.
1
0
0
monsieuricon

K. Ryabitsev

Reply to @vbabka
@vbabka it should be entirely possible. E.g. this page is statically rendered already: https://social.kernel.org/notice/AQ4reII29sqhY7P57I

When we archive off the thread, we'll just set up a redirect to its public-inbox threaded view (e.g. with a message-id notice-AQ4reII29sqhY7P57I@social.kernel.org).

At least that's how it looks in my head.
0
0
2
About social.kernel.org

Terms of service

  1. Please do not use this service in violation of the Linux Kernel Code of Conduct. Doing so will result in your account suspension with the referral of the matter to the CoC committee.

  2. "Repeating"/"boosting" someone else's status on this platform will be treated as endorsement and will fall under rule #1.

  3. You are encouraged to use this platform to promote your work on the Linux Kernel, but there is no restriction on permitted topics (with the exception of anything covered by #1 above).

  4. There is no requirement to post in English, but it should be considered the primary language of communication on this platform.

Privacy notice

The admins of this service have access to all posted statuses. They aren't looking, but if it's something they shouldn't know about, then you should not post it on this platform.

Please see the Linux Foundation Privacy Policy, which applies to this platform as well.

Getting your own account

If you would like an account on this instance, please check that the following applies to you:

  • You are listed in MAINTAINERS or CREDITS

  • OR: You have a kernel.org account or email address

  • OR: You have a long and established history of involvement with the Linux Kernel

If the above is true and you agree with the Terms of Service and Privacy Notice listed above, please use these instructions to request an account: