Notices by Fluffy :soft_peek: (hurricaneweasel@mastodon.world)

@apps
This really is a complex issue. :soft_hmm: I'm glad you are making so much progress to completely fixing it.

@apps
Sure. I'm glad I can help a little bit. :soft_nodders:

My TOP 3 improvements of :fedilab: over the last year were...

1. Reverse timeline reading order
2. Reload all timelines at once
3. Fix timeline being offset after restart

It also became faster, and much more stable for me.

What were your favorite improvements?

#Fedilab

@calvin
For Mastodon, this isn't implemented.
https://github.com/mastodon/mastodon/issues/4106

Since you're on Pleroma, you might need to activate it in the extra settings.
@apps

@apps
I can't imagine that this would work. I glued it together, bit by bit, and fitted it to my needs. Everything is hard-coded (for example my token), and it runs on my little Lenovo laptop server behind the shoe rack. :soft_sweating:
@deutrino

@apps
That would be a good workaround. I made the website, so it can register as an app. I can share to it from Fedilab. The URL of the post is prefilled. I choose the slot and schedule it. The next free slot is used (it leaves the slots for my own post free). It only takes seconds.
@deutrino

@apps
At this point Fedilab works so well for me, there is not much I'm really missing, more stuff that would be nice to have. :neocat_heart:

I think [1258](https://codeberg.org/tom79/Fedilab/issues/1258) (Add ability to preview drafts) would be a really good feature, since you'd be able to spot mistakes with markdown or emojis before posting. :neocat_thinking:

@deutrino
Yes, I ultimately built this system on my server, since it was hard to manage boosts with Fedilab and the issue on Mastodon's site didn't move.
https://github.com/mastodon/mastodon/issues/15219
@apps

@apps
I've send a PR for this. :soft_nodders:
@Aprazeth

@apps
I can only reproduce the ones already reported. Also, the app doesn't get cleared from RAM as often anymore. I close it cleanly four times a day with Samsung Modes. Cache is kept for one day. Battery consumption is pretty much ideal, considering I scroll through about 2k posts a day. I only clear the cache every now and then when art timelines get confused, but that is a niche issue. My verdict: major success. :blobcatthumbsup:

@AestheticFemboy
Couldn't you deactivate it, send a follow request, and reactivate it? :soft_thinking:
@apps

@apps
Enjoy your break. :woozy_beach: :blobcat_longlong:

@apps
Thank you for your hard work! :neocat_heart:

@aaron
There was a fix in 3.40.2.
https://codeberg.org/tom79/Fedilab/releases/tag/3.40.2

If there still is a bug with the current version, please open a new issue. We can link the old one. Thank you. :neocat:
https://codeberg.org/tom79/Fedilab/issues/1091#issuecomment-5873305
@apps

@apps
https://codeberg.org/tom79/Fedilab/projects/52934

I collected some wishes for improvements in error handling (scroll a bit to the right). This would fit well there. :blobcatthumbsup:

@apps
The release notes show which version it should work with. And even if something went wrong, neither the hashtag nor Codeberg was flooded with complaints. This is a huge project, and it's impressive how you handle it. And Fedilab is free, so don't worry too much. :neocat_floof_happy:

@apps
Huh? :blobcatwhat: I didn't notice any problems or complaints.

@a1ba
Is your server still being attacked? :blobcateyes: It took about a day for your post to arrive here.

@a1ba
Oh no. :neocat_sad: I hope you can fight them off. Good luck.

@a1ba
Temporary using Cloudflare is not an option? (That's probably a dumb suggestion, because I don't really know much about servers, except what I learned from setting up my tiny manga server. :neocat_googly_woozy:)