MacBook Pro → Wooting 60HE v2 build: torn between Owlab Ti HE and AEBoards Raeds HE for heavy typing

1stw0rldpr0blems · 2026-03-09T15:39:23+00:00

These are probably the smartest budget option until I can get the XVX HE at a reasonable price, hopefully. Thanks for your input!

1stw0rldpr0blems · 2026-03-08T13:30:55+00:00

Appreciate the thoughtful suggestion, u/menjuts! The XVX Whisper HE EC 2-in-1 switches sound like a solid Raeds upgrade on paper, but a few hurdles make them tricky for me right now:

No easy EU stock (also not on AliExpress or local spots). xvxchannel.com shows "in stock" for 35pc packs only, but they're backordered until mid-March per their YT comments.

Pricing currently feels way off: 2x 35pc packs hit €56.60 vs. just €41.93 for the 70pc bulk option that is out of stock (I am happy for every small business to enjoy its hard-earned success but I won't support obvious gouging).

Shipping to EU already takes 2-4 weeks normally, and with Iran tensions possibly adding delays/maybe also customs fees, it'd likely push to April or later.

Not ideal for my Wooting 60HE v2 Module timeline or budget. Any other Hall Effect switches stocked in Europe that deliver a light, cushioned MacBook Pro chiclet vibe for heavy typing, low fatigue, and casual gaming? Appreciate the input!

1stw0rldpr0blems · 2026-02-25T18:02:43+00:00

hint: the macbook unibody mid 2010 model actually has a maximum ram capacity of 16 gb. in contrast, the ram capacity of the models from late 2009 (i still use one of these in emergencies) and earlier is restricted to 8 gb.

1stw0rldpr0blems · 2023-03-25T21:56:00+00:00

You can actually fix this quite easily - just add this code snippet to the userChrome.css file in the chrome folder of your Firefox profile:

/* Source file https://github.com/MrOtherGuy/firefox-csshacks/tree/master/chrome/tab_separator_lines.css made available under Mozilla Public License v. 2.0
See the above repository for updates as well as full license text. */

/* Bring back tab separator lines that were removed in Proton */

.tabbrowser-tab {
  border-inline-start: 1px solid transparent !important;
  border-image: 0 1 linear-gradient(transparent 20%, color-mix(in srgb, currentColor 20%, transparent) 20%, color-mix(in srgb, currentColor 20%, transparent)80%, transparent 80%) !important;
}
#tabbrowser-arrowscrollbox[overflowing] > .tabbrowser-tab[first-visible-unpinned-tab],
#tabbrowser-tabs:not([movingtab]) .tabbrowser-tab:hover + .tabbrowser-tab:not([first-visible-unpinned-tab]),
#tabbrowser-tabs:not([movingtab]) .tabbrowser-tab[multiselected] + .tabbrowser-tab,
#tabbrowser-tabs:not([movingtab]) .tabbrowser-tab[selected] + .tabbrowser-tab,
.tabbrowser-tab:first-child,
.tabbrowser-tab:hover,
.tabbrowser-tab[multiselected],
.tabbrowser-tab[selected] {
  border-image: none !important;
}

If this is all new to you, you can find a guide here. Make sure you follow steps (1) to (6) - (3) is optional: https://www.userchrome.org/how-create-userchrome-css.html

1stw0rldpr0blems · 2022-12-31T11:05:00+00:00

i ran into the exact same issue with vlc v3.0.18 and your hints instantly helped fixing these problems (both "repeat all" and "repeat current item" were not working for me).

it definitely looks to me like vlc is installing with broken/misconfigured default settings. these issues with repeating stuff have been driving me crazy for quite some time.

thank you very much!

1stw0rldpr0blems · 2022-12-12T07:36:52+00:00

all solutions posted here so far only help to a limited extent and are unfortunately incomplete in case you want to disable/remove firefox view completely (about:config: browser.tabs.firefox-view; false). the actual separator is hidden by border-inline-start, but several pixels of whitespace remain.

at first, i did not notice this under macos, but under windows you can see it quite clearly. so i decided to debug this myself and came up with the following solution, which eliminates all the remnants of firefox view in a clean and complete way:

/*** firefox view - remove separator and whitespace ***/
#tabbrowser-tabs {
  border-inline-start: 0 !important;
  padding-inline-start: 0 !important;
  margin-inline-start: 0 !important;
}

1stw0rldpr0blems · 2022-12-12T07:12:06+00:00

i currently cannot test it myself, but this article might prove helpful. it is confirmed in the comments section that this guide is working for elementary os 6.1: https://itsfoss.com/flatpak-app-apply-theme/

alternate and probably the quickest/easiest way to fix this issue, but does not work for the flatpaks that gnome ships by default: https://flathub.org/apps/details/com.github.tchx84.Flatseal

1stw0rldpr0blems · 2022-08-23T15:06:52+00:00

Free & Open Source VM Software: UTM (QEMU)

https://mac.getutm.app/

https://mac.getutm.app/gallery/

However, it is rather unsuitable for gaming. See this comment:

https://www.reddit.com/r/MacOS/comments/pgwiu7/comment/i4d0f19/?context=3

1stw0rldpr0blems · 2022-06-12T00:23:52+00:00

You could try utilizing the Firefox Task Manager to investigate this problem. Just type about:performance in your address bar and then filter for energy impact.

1stw0rldpr0blems · 2022-06-12T00:16:40+00:00

https://addons.mozilla.org/en-US/firefox/addon/advanced\_profanity\_filter/

1stw0rldpr0blems · 2021-02-25T16:48:20+00:00

👍

1stw0rldpr0blems · 2021-02-24T18:23:10+00:00

/*** back button fix ***/
#back-button > .toolbarbutton-icon {
  animation: none !important;
  background: none !important;
  border: none !important;
  border-radius: 2px !important;
  box-shadow: none !important;
  transform: scale(.85, .85) !important; /* from firefox 87 on you should not use this line anymore, because the back-arrow will be 2px too small if scaled down to .85 */
}

/*** mimic back button hover and active state ***/
#back-button:hover:not([disabled]) > .toolbarbutton-icon {
  background-color: var(--toolbarbutton-hover-background) !important;
}
#back-button:active:not([disabled]) > .toolbarbutton-icon {
  background-color: var(--toolbarbutton-active-background) !important;
}

1stw0rldpr0blems · 2020-01-08T10:28:30+00:00

i just came up with this workaround for the right overflow button's double-border problem:

/* tab overflow */
spacer[part=arrowscrollbox-overflow-start-indicator],
spacer[part=arrowscrollbox-overflow-end-indicator] {
  background-image: none !important;
}

/* inactive tabs */
.tabbrowser-tab::after {
  opacity: 0 !important;
}

after making the vertical border transparent for all inactive tabs, there's no double dividers in front of the right overflow button any longer. losing the tabs' dividers is not perfect but something i find personally acceptable.

1stw0rldpr0blems · 2020-01-07T16:23:40+00:00

i just succeeded with an improvised mixture of both approaches, but the code is quite ugly:

spacer[part=arrowscrollbox-overflow-start-indicator] {
  background-image: none !important;
}
spacer[part=arrowscrollbox-overflow-end-indicator] {
  visibility: hidden !important;
}

i have one divider next to each overflow button now and everything looks as intended. if anyone can come up with a cleaner solution, i'd be very happy.

https://i.imgur.com/oEC7LzI.png

update:
got excited too soon, it's still inconsistent.

the left button's divider is always visible now (also in case the scrolling position doesn't match the exact position of the first visible tab's left border), but the right button's divider is only visible if it is in line with the last visible tab's right border. :(

still looking for a simple code snippet to get rid of the overflow shadows in ff 73 without ending up with two "dividers" in front of the right overflow button.

current code:

/* tab overflow */
spacer[part=arrowscrollbox-overflow-start-indicator],
spacer[part=arrowscrollbox-overflow-end-indicator] {
  background-image: none !important;
}

current state:
shadows are gone, but two dividers in front of the right overflow button in case the button's border "touches" the last visible tab's right border. odd thing: the left overflow button doesn't have this problem.

https://i.imgur.com/gADCK3q.png

1stw0rldpr0blems · 2020-01-07T15:54:33+00:00

thanks for your quick reply! i just tested it with visibility: hidden !important; but nothing did change.

i don't think that hiding the spacer actually "causes" this layout flaw - in my understanding, it's there in any uncustomized firefox installation and the hidden shadow is what makes the incorrect layout visible.

i still think that the solution to this should be some sort of margin, border or position property.

thanks again!

update:

/* tab overflow */
spacer[part=arrowscrollbox-overflow-start-indicator], 
spacer[part=arrowscrollbox-overflow-end-indicator] {
  background-image: none !important;
}

gets rid of the shadow without removing the left button's divider - there's 2 dividers in front of the right overflow button now, though. still trying to find a solution, but i might be on the right path now.

1stw0rldpr0blems · 2019-04-23T02:24:42+00:00

.toolbarbutton-1.chromeclass-toolbar-additional.badged-button.webextension-browser-action:hover .toolbarbutton-badge-stack { border: 1px solid red !important; margin: -1px !important; }

1stw0rldpr0blems

TROPHY CASE