kim ed3035699f [bugfix] fix lo paging value not always being set (#4407) ... the "lo" paging value wasn't always being set when loading statuses from the database. this seems to (potentially) fix an issue in tusky with list timelines showing repeated posts. Reviewed-on: https://codeberg.org/superseriousbusiness/gotosocial/pulls/4407 Co-authored-by: kim <grufwub@gmail.com> Co-committed-by: kim <grufwub@gmail.com>		2025-09-04 18:06:26 +02:00
..
domain	[feature] Move to code.superseriousbusiness.org	2025-04-26 15:38:43 +02:00
headerfilter	[feature] Move to code.superseriousbusiness.org	2025-04-26 15:38:43 +02:00
timeline	[bugfix] fix lo paging value not always being set (#4407)	2025-09-04 18:06:26 +02:00
cache.go	[feature] scheduled statuses (#4274)	2025-08-12 14:05:15 +02:00
db.go	[feature] scheduled statuses (#4274)	2025-08-12 14:05:15 +02:00
invalidate.go	[feature] scheduled statuses (#4274)	2025-08-12 14:05:15 +02:00
mutes.go	[performance] add statusfilter cache to cache calculated status filtering results (#4303)	2025-07-01 16:00:04 +02:00
size.go	[feature] scheduled statuses (#4274)	2025-08-12 14:05:15 +02:00
statusfilter.go	[performance] add statusfilter cache to cache calculated status filtering results (#4303)	2025-07-01 16:00:04 +02:00
timeline.go	[feature] Move to code.superseriousbusiness.org	2025-04-26 15:38:43 +02:00
util.go	[feature] Move to code.superseriousbusiness.org	2025-04-26 15:38:43 +02:00
visibility.go	[performance] add statusfilter cache to cache calculated status filtering results (#4303)	2025-07-01 16:00:04 +02:00
wrappers.go	[chore] update dependencies (#4386)	2025-08-21 16:41:50 +02:00