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.
Hi @synlogic@toot.io 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 have tried a couple of different "daily planner" type strategies (Bullet Journal, etc...), but none of them seem to stick. I'm looking for ideas on how others are able to organize their daily/weekly/whatever to see if any of them would make sense for me (or maybe even trigger inspiration to take parts from ideas and make my own). I'm pretty sure whatever I go with would have to be digital (carrying a physical notebook with me was part of the reason Bullet Journal didn't work), but I'm not opposed to trying an analog technic again. Also, depending on the strategy I could probably "convert" it to digital and use Obsidian or another tool (I'm an iOS user).
I replied on this in a Matrix room already. I won't retype my whole reply here. Essentially, IMO GPL stifles innovation as it forces everyone to use the same license and for everyone to release their code. This might be a good thing when it comes to concerns over competition (eg Threads vs everyone else), but it is a bad thing when it comes to building a community around a platform (theme developers can't sell custom themes because they also have to publicly release their code under GPL. Plugin developers have the same issue. Technically, 3rd party apps should be releasing their code as well). Yes, there are many people who enjoy contributing to open source (myself included). However, there are also many that want to be recognized (financially) for their work. GPL ignores the latter. The fediverse already has a mechanism to guard against some corporation coming in and taking the code from a platform and building a commercial product on top of it - defederation. We don't need GPL to "protect" us from anyone here).
NOTE: I also am not a lawyer. I might have some things wrong w/r/t GPL. However, I'm old enough to remember when it was actually an important OS license and when it was truly needed. I don't believe that is the case any more. LGPL might be fine, but the rest of the variants should only be used after extremely careful consideration and not just as a default.
How does everyone feel about it? Should I keep it? Turn it off? Change it's frequency? (If so, to what?). It feels like it's the biggest poster here and I don't know if that is a good thing or not? I see some responses to it (which is good), but I also see a few that don't get responses. If it's just about the prompts it is giving I could try tuning that as well. Please let me know what you all think.
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)
I got my ADD diagnosis today (no "h" as I don't meet the criteria for hyperactivity). It felt validating to hear a doctor say what I've felt for a while now.
Something else to consider here would be some kind of batching. A system doing this check should group users together by instance and make a single call to that instance. Something like: "Hey, I have this list of users from your instance. Are they all still active? A, B, C, D..." Reply: "From your request, here is the list of users that I found in my database: A, D". Now the calling system would know it should remove all data for users B & C.
lazyguru @discuss.online Site admin for discuss.online.
I'm a software engineer by day. I play games casually. I'm married with 4 kids, a dog, and 2 cats. I don't like sand. It's coarse and rough and irritating and it gets everywhere.