Hi @[email protected] appreciate it, but we have no budget for paying contributors (we aren't even covering base costs let along paying ourselves). This is an open source project where we don't have any plans to monetize the platform itself (we might consider building things down the line that are paid add-ons, but nothing that would be essential for running your own instance self-hosted)
I don't know how you feel as I've never personally experienced losing a job, but I emphasize with what you might be going through. I've had friends and family that have gone through it (or going through it now). You are not your job. You are sooo much more. Losing a job may suck, but you will recover and be better from it (even if it takes time).
Thanks. That's actually a bit helpful. I think I'm similar to you on the "tick the box" feeling
I hear you on the lack of controlled/curated environment. I know that with a scheduled routine I'm least forgetful, but my brain starts screaming about the "monotony" of the routine.
Hmm, the stack/heap approach IS interesting. I might try giving that a try.
Re: exercise, it wasn't what I was asking about but it's still a good reminder. I try to take daily walks, but I could be better at other exercise in general (I paid for a sit/stand desk and always forget to adjust it to stand mode so I end up sitting all day)
The restaurant pagers is sheer genius. I can already envision the "why is that thing blinking? Oh yeah I need to do X" trigger. Unfortunately I doubt it would work for me because of the time predictability requirement (probably a big reason I struggle with planners in general I imagine), but still... my mind is blown on that one
So... when was I "in the zone"/hyperfocused? This questions clearly is for the wrong audience 😂
About 20 minutes before I'm supposed to go to bed. I then don't realize until about 90 minutes AFTER I really should have gone to bed 😳
Hmm... this feels like a repeat?
We are aware of an issue with some clients not being able to sync (receiving 502 errors, etc..). It does not appear to affect all clients and the web view is still working. We will update this post as we know more and when we have resolved it.
Updates:
09-Sept 11:19 PM UTC We attempted to roll back from Lemmy v0.18.4-beta.8 to v0.18.4 (as well as even earlier beta versions) but the service failed to start. We've reverted back to v0.18.4-beta.8 for now and will continue investigating the cause of the sync issues.
10-Sept 3:30 AM UTC And... we are back, where we started. If you hadn't noticed, we were down for almost 2.5 hours while we tried to rollback the database migrations introduced in the beta releases so we could go back to the stable v0.18.4. When that failed, we tried to restore from the backup we took just prior to the rollback attempt. When that failed, we used Digital Ocean's restore to point in time and created a new DB cluster and switched to it. So... we are back on v0.18.4-beta.8 again, with the expectation that 3rd party clients are still broken. Unfortunately, we are not sure what we can do about this as we believe it is something in Lemmy that is breaking it. The mitigation we have put in place to avoid this going forward is that we no longer use the "latest" tag when loading a docker image and now hard lock to a specific version. We will update that version in a more intentional manner going forward.
10-Sept 4:15 AM UTC After some additional digging through the Lemmy diff for beta.5 to beta.8 (and then looking through the PRs that were merged to create this diff), the issue is indeed with the Lemmy code and is even called out in one of the PRs,. What this means is that the 3rd party clients that are not able to access the site will need to update their code to fix things on their side (or else they will be broken when v0.19 is released and all other instances update to it).
16-Sept 11:23 PM UTC Both Sync and Mlem have now released new versions that resolve connectivity issues. If there are any remaining clients we suggest you reach out directly to them to ask them. We'll be unpinning this post in a few hours
27-Sept 10:30 PM UTC We have made the decision to update to the RC (release candidate) for v19 as the beta we were previously on was missing some much-missed admin tools that we need to run the site with. This update appears to have affected 3rd parties again (I have tested Mlem and Memmy and get errors about authentication, however they still seem to load?). There also appears to be an issue with the home page loading that we are currently looking into how to resolve. As before, we don't anticipate any way to roll back. To steal a line from my daughter's favorite movie: Keep Moving Forward
28-Sept 12:03 AM UTC We found an issue with the markdown parsing that was causing the homepage sidebar to throw errors. We've resolved the issue and will update the core developers of Lemmy.
03-Oct 1:28 AM UTC We have implemented a workaround that should have fixed all apps. Please let us know if you are still having issues with an app (we may not be able to add a workaround for it, but we would like to at least track the ones not working)
view more: next ›
Yes, the about site needs a lot of work. The demo site is using the Lemmy frontend but Java Springboot backend. The whole intent of the first milestone release is to be a drop-in replacement for Lemmy. It's after that where we will differentiate with things like better moderation/admin support, etc... The federation service will be built in Golang. And yeah, we need to do a lot more work on outlining what work needs to be completed in the form of issues. Those 8 for sure are things that need to be done though.