Rediggit for Lemmy has been renamed to Lemonberry...now with dark mode
Cross-posting this from https://lemmy.ca/post/1271596 [https://lemmy.ca/post/1271596] due to the current federation situation: > A new version of my Rediggit theme for Lemmy has dropped, and with it comes a name change… > > Rediggit is now Lemonberry, to better reflect the separation from Reddit. > > I’ve also added a much-requested dark mode, adapted from Lemmy’s default darkly theme. Those familiar with the Reddit Enhancement Suite’s dark mode should find this pretty comfortable. > > If you have no idea what any of this means, Lemonberry is a flexible, full-width light and dark theme for Lemmy. It is just one of many user-made themes for this community. These themes can be installed and enabled with the use of a CSS injector browser add-on, such as Stylus (Firefox [https://addons.mozilla.org/en-US/firefox/addon/styl-us/], Chrome [https://chrome.google.com/webstore/detail/stylus/clngdbkpkpeebahjckkjfobafhncgmne]). UserStyles.world [https://userstyles.world] is a good place to start exploring the available themes. > > The latest version of Lemonberry is optimized for Lemmy v0.18.1 only and is available on GitHub [https://github.com/thayerw/lemmy-lemonberry] and UserStyles [https://userstyles.world/style/10440/lemonberry]. I will likely keep the optimizations in sync with only the larger instances as Lemmy development is changing rapidly, and it’s proving difficult to maintain compatibility with older versions. > > You can also find older versions of the theme, and additional screenshots, at the GitHub [https://github.com/thayerw/lemmy-lemonberry]. > > Cheers
Tried to search for this artist’s internet presence and all hits either require a user account or don’t work at all…some days, the web really sucks…
Twitter:
Instagram:
madebynelson.co:
“Unified branding” kinda misses the entire mark of “federated but decentralized” that this network of services is supposed to be all about.
I don’t think it does. Decentralized doesn’t mean every instance must appear unique from one another, though they certainly can if that is their wish. There’s no reason why a group of common instances shouldn’t want to provide a unified approach to branding their platform.
You’ve mocked up a really clean looking theme, but I’d never use it personally because it’s light-mode and it would burn the eyeballs out of my head at night.
Thanks, the theme is just my usual rediggit for lemmy (the dark variant is coming soon). The point of the post was just to highlight the navbar logo concept.
Experimenting with unified instance themes
Thought I’d share some ideas I’ve been floating, to implement a unified branding across all instances. Instances could opt-in for a unified identity with the platform, using an official trademark and their instance address embedded below it. Instances that use “lemmy” in their second-level domain name would simple append their .tld (such as .world), or use .sld.tld when “lemmy” is accessible from a subdomain (such as .dbzer0.com). Seemingly unrelated domain names, such as beehaw.org [http://beehaw.org], would just omit the leading dot. The navbar background itself could be further customized by the local instance. I imagine something like a watermark of a globe for lemmy.world, or a watermarked maple leaf for lemmy.ca [http://lemmy.ca], etc. Obviously this is a very rough take on things (including the art style), and I’m just brainstorming ideas at this point. What are your thoughts?
It isn't just Lemmy.world, and isn't limited to v0.17 either. Lemmy.ca, which has been running v0.18 for days, is also not seeing a lot of federated content, nor accurate community subscription counts from other instances, including lemmy.ml and others running v0.18. I'm posting this from my .world alt because .ca is showing zero comments in this thread.
There have been several not-so-friendly comments made about the issues by someone in [email protected], calling out the site admins of .world and .ml for not sharing their server logs, and the overall silence on the issue. The user's concerns are genuine, but I don't agree with their behaviour.
I suspect the devs were/are completely overwhelmed by the mass influx of redditors these past two weeks. I assume someone is looking into it, but frankly I wouldn't blame anyone if they chose to step away for a few days. I think a lot of folks (particularly "the masses") forget that these are largely volunteer efforts, by people with day jobs.
Lemmy.ml [http://Lemmy.ml] front page has been full of nginx errors, 500, 502, etc. And 404 errors coming from Lemmy. Every new Lemmy install begins with no votes, comments, postings, users to test against. So the problems related to performance, scaling, error handling, stability under user load can not easily be matched given that we can not download the established content of communities. Either the developers have an attitude that the logs are of low quality and not useful for identifying problems in the code and design, or the importance of getting these logs in front of the technical community and trying to identify the underlying patterns of faults is being given too low of a priority. It’s also important to make each log of failures identifiable to where in the code this specific timeout, crash, exception, resource limit is encountered. Users and operations personnel reporting generic messages that are non-unique only slow down server operators, programmers, database experts, etc. There are also a number of problems testing federation given the nature of multiple servers involved and trying not to bring down servers in front of end-users. It’s absolutely critical that failures for servers to federate data be taken seriously and attempts to enhance logging activities and triangulate causes of why peer instances have missing data be track down to protocol design issues, code failures, network failures, etc. Major Lemmy sites doing large amounts of data replication are an extremely valuable source of data about errors and performance. Please, for the love of god, share these logs and let us look for the underlying causes in hard to reproduce crashes and failures! I really hope internal logging and details of the inner workings of the biggest Lemmy instances is shared more openly with more eyes on how to keep scaling the applications as the number of posts, messages, likes and votes continue to grow each and every day. Thank you. Three recently created communities: [email protected] [/c/[email protected]] [https://lemmy.ml/c/lemmyperformance] – [email protected] [/c/[email protected]] [https://lemmy.ml/c/lemmyfederation] – [email protected] [/c/[email protected]] [https://lemmy.ml/c/lemmycode]