Hillsides are great
kukkurovaca
joined 2 years ago
This is surfacing a fundamental division between mindsets in federation: the people who say don't worry about which instance you're on are bought into the promise that federation can "just work" like email. But the reality is that if you care about moderation at all (like, even to the extent of being for or against having any of it) then sooner or later you're going to have to make harder decisions about instances.
It's pretty normal for long-term fediverse users to change instances several times over the course of however long this stuff has been around. It's unclear to me whether any existing Lemmy instances would be a good fit for me in the long term TBH and I would expect that to be true for some time, as so many instances are still figuring things out internally.
Defederation decisions like beehaw made are extremely normal and rational. With their level of moderation staffing and for their user base, they determined it was unsustainable to remain federated with instances that were generating more moderation workload. If it wasn't them today it would be another instance tomorrow; this will keep happening.
Also, I see a lot of folks saying this is lazy for beehaw, but it's important to understand that from their perspective, this problem wouldn't arise if moderators here were keeping a cleaner house and preventing bad actors from using the platform. (Not saying either take is entirely correct.)
In a sense, moderation best practices on the fediverse are inimically hostile to scaling the fediverse up to new users. (And if you ask folks with smaller but prosperous instances that have healthy internal vibes, they'll probably tell you this is good.)
This is much more fraught on Lemmy than it is on Mastodon, because you're building communities hosted on a particular instance and there's not currently a way to move the community. So, if I were to start a community here and then finally decide a year from now that this place is too big a defederation target to stay on, what do I do?
Similarly, to avoid endless duplication of communities, folks have been encouraged to participate with existing communities instead of starting a new one on their own instance everytime. But anyone here who has gotten involved with communities on Beehaw will now no longer be able to do so unless they move to a different instance. (Which may be hard, as open instances that are easy to join are the ones that are harder for small instances to handle, which is what caused this in the first place.)
Some of those folks are going to create their own alternative communities on their servers, which to any third-party servers not in the loop on the defederation drama will be potentially confusing. This has the potential to create a cultural tend toward polarization of community norms between everything goes and what we see on Mastodon as content warning policing, but of which are, to me, undesirable.
The best case scenario is that the majority of large communities end up being hosted on instances that have sufficiently rigorous moderation standards and sufficiently robust moderation staff to not impose an unsustainable workload on smaller instances. Then as long as everyone who's not a nazi federates with those instances, things should go smoothly...ish. But that's hard both because "sufficiently rigorous" is different for everyone and because moderation labor doesn't grow on trees.
If you build using nice!nano controllers, you can get batteries that fit neatly under the (socketed) controller, you can just tuck it in there loose or tape it in place. If you use those batteries, which are very small, it's best to build the board without any power-drawing features, such as LED illumination or OLED display. Most PCBs that are designed for batteries will put contacts in that vicinity, or you can wire the batteries directly the nice!nanos.
If you build this way, there's no impact on the external size or portability. If you want to use larger batteries, you will need to make room in the case for them, if you're using a case. [I have some chunky batteries taped to the bottom of my caseless Kyria, which is obviously not doing anything good for portable use or aesthetics, but it does work.)
If you haven't used ZMK before, that will be a bit of a transition. ZMK is great, and in some ways it's a much more elegant solution than QMK, but it can be a little tricky to get used to at first and if anything goes wrong, troubleshooting is usually more annoying.
For portable use, a PCB that supports a power switch to disconnect the battery from the controller is kind of essential IMO, since without a hardware switch, there's no way to turn the board off or put it to sleep. So if it's in your bag, it'll constantly be waking up and connecting to your phone if paired.
Case (I have not bought any, I’ve just made a wooden panel, cutting it ad hoc), but I may buy one in the future or 3D print one, let me know what you think about it.
This looks great. You can also use adhesive-backed foam for a really low profile (while not scratching up your desk)
When I keep them pressed they are not recognized and I have to repress them. I don’t think it is a firmware issue, because I have tried different configurations in ZMK and now all of them fail with the same keys, independently of whatever character I map on those keys. I am thinking that it maybe due to some diode that may be missoldered or some pin in the controller, because the first days it worked fine.
Could be some cold joints, it's not unusual for them to work fine at first and then start to fail later on. Check the soldering on the affected keys and diodes and reflow anything that looks supect. You can also ask in the SplitKB discord to find out which controller pins should be checked based on the keys where you're seeing issues.
Lately I've been really enjoying Black and White's Elkin Guzman Strawberry Catiope and Hydrangea's El Paraiso decaf (which is incredibly good if you like fruit-forward coffee and are looking for decaf).
I also have some less funky coffees on hand from Flower Child, but I haven't been doing those as espresso lately
The one from the ceramic cup felt more bodied, while the one from the wine glass felt lighter and more acidic.
Yeah, I think that temperature is very likely to play a role specifically in this aspect mentioned by OP. The glass would have dumped heat much faster, and perceived acidity normally increases as the coffee cools.
Defederation is an inevitable fact of life for a federated ecosystem and it won't always be for things where everyone agrees (just look at the fediblock tag on mastodon). The important thing is that instance owners have clear criteria for how they defederate from other instances and transparency about their reasons for having done so, so that their users and other instances have the correct expectations for their future behavior.
It's early days for a lot of instances and probably many of us will end up migrating to other instances as it becomes clear which ones make decisions that suit our values.
What I do worry about is the fact that folks are setting up communities wherever they first land and Lemmy doesn't yet have tools for migrating a community between instances (correct me if I'm wrong about that). That seems like a ticking time bomb in some ways.
The US also runs concentration campus, has slave labor, forced sterilization, torture, genocide, violently repressive police, persecution of religious minorities, etc. etc. etc. Hence why it's a red flag (no pun intended) when people in the west have A Lot To Say about China and just China.
::slaps top of any country:: you can fit so many human rights violations in this bad boy
(I have a lot more complaints about the US than China, but that's because I live in the US, not because I think other imperial powers are exempt from criticism.)
See keycodes here for toggling between bluetooth output and usb output:
Personally I really like the Himalaya for the most part, except for the converter. (Which is why my recommendation is for the Jaipur)
In terms of guzzling ink, this is both normal and necessary for a flex nib, at least up to a point. Without sufficient ink flow, the pen will railroad, which is the most common failure mode for flex/semiflex pens.
In terms of "softness", is the issue with the tactile feel, or that it flexes too easily (which most flex users would consider a feature, usually), or that it lacks sufficient springback to get hairlines? I don't find the FPR's ultraflex nibs to be extremely soft relative to other flex nibs, but there is also sample variation to consider.
If you write with a very heavy hand, this could be part of the problem, in which case there might just be a period of adjustment to using a lower amount of force.
One thing you might try is adjusting the nib and feed, for example, you might try setting it up so that the nib sits a bit further back in the section. This will reduce the amount of flex you can get, but might improve consistency. Heat setting the feed also often helps performance, but if you arlready have more than adequate flow, this might be unnecessary.
Re: ink, good performance in a flex pen will vary from ink to ink, and basically the trick is to find a fast-flowing and viscous ink that is not prone to excessive feathering. Personally, my favorite ink for flex writing is J. Herbin Lie de The.
When searching for DIY Keywell models, use "dactyl" in your search terms for most results. Most DIY Dactyl builds are handwired, although there are some models that make use of flexible PCBs such as the ones from BastardKB. (My keywell board is a TBK Mini from them.)
Re: the number of keys, this is pretty personal. Most ergo mech users are using something in the ballpark of a 60%, 40%, or 35%ish layout. (My objection to the Glove80 is that it has way, way too many keys for me)
Most ergo users have numpad on a layer. (Here's how I have my layouts)
If all the new trolls are coming from two instances, and defederating those two instances will keep the load manageable for them, why wouldn't they?
This kind of decision is a big problem for scaling up Lemmy as a reddit replacement and welcoming huge volumes of new users, but I don't think that's Beehaw's goal and certainly not their responsibility.
The tricky bit is figuring out how to set up fediverse-wide communities in places that most (non-troll) users won't be cut off from them.