interdimensionalmeme

Oops, I clicked a random tab, now I can't find my previous tab.

Surely there is a keyboard shortcut to go back where I was ?

Note : I have 2185 tabs open in 21 windows

Hi,

I really miss the old version of the website "weatherspark" It had an absolutely fantastic weather dashboard.

It was a old google-finance-like graph that you could scroll, to zoom in and out to increase the timescale, or left to right to shift the date at the center of the graph.

The lines on the graph shows, current temperature, historical temperature and prediction temperature.

There were bands around the temperature that would indicate temperature averages and records for the date period on screen.

If there were precipitations, it would show as another line the amounts.

In that simple graph you could get the sense of the local weather, what it's been and what it will be, this week, this month or 25 years ago with just your mouse.

With all the weather data being collected by government and available on public APIs, is there any open source self-hosted software that has an effective interactive data visualization user interface as weather spark of old ?

Here is what it looked like, all in a single graph with NO pageloads !

I have heard the dismissal, I have been told I don't matter, I have been told I'm a edge case.

But I'm telling you wayland, I chafe at you taking away my optionality.

Sometimes I ~need~ that feature, and when I need it, I need it bad !

I understand that the IBM money pouring into wayland is super happy about the linux world losing network transparency for apps, stripping power users of their inconvenient toys.

But I'm telling you, I need it.

No, waypipe isn't it.

~~Also, no longer having distinct window managers from the compositor give me serious bad vibes but this isn't what this is about~~

I am looking for an open hardware PCB Ready to send files for oshpark, seedstudio or jlcpcb like places

A PCB with the following features

wired of an MCU supported by mainline QMK/ZMK/VIA and or VIAL correctly wired for bluetooth/2.4G and wired battery powered USB-C port surface mount diode and individually addressable LEDs

Has anyone ever made such an open hardware PCB ?

Last month I purchased a keyboard, it is physically very nice and has all the features I listed above, except it runs it's own unmodifiable proprietary firmware, so the whole thing is garbage.

Pity because physically this keyboard is everything I wanted

I need fine grained, automated cookie controls I have tried these addons

Cookie Manager Cookie Quick Manager Cookie AutoDelete

And the problem is always the same.

It is TOO DIFFICULT to only have one exception for one cookie in one account container

Creating containers for every single website is also extremely tedious and buggy.

And deleting all cookies all the time, means I am re-logging in into everything all the time, often a 5 to 10 step process not counting 2 factor and it is VERY annoying

Hi,

I've been searching for the right switches for a while now. And I have a box full of keyboards I don't like to prove it.

I found a keyboard I like but it's got the wrong switches on it.

I got a mathew yg108, that seems alright, though I have firmware trouble with it so far.

The keyboard came with switches as follows

Brown switch:Operating force:45g Pressure Force:55g
Operating Travel: 2.0mm Tactile Travel:1.2mm Total Travel:3.40±4.00mm

The tactile feels like almost nothing, almost like linear switches and while it's great for gaming, I like having way more resistance than that.

I know a keyboard that has the switches I like. It was a victsing pc315a

No idea what switches this uses but they have a lot more resistance at the activation point

Anyway, I tried my luck buying switches that looks like they might be like that

I got a set of outemu branded "orange" switches

here are the specs

I received them and installed one of them

original switch

new switch

new switch behind

switch hole

And after all this was said and done... I cannot tell the new switch apart from the other ones ! Feels exactly the same ?

Do I just need a stronger spring value ? I had a 45 or 55 gram switch Now it's almost 60 gram switch

How high to these values go ?

What is the next tactile standard switch force I can search for after 60g ?

What does the victsing keyboard use ?

So far I love it, it's the nicest keyboard I've ever had but how do I flash my new firmware ?

This page has the original firmware

https://www.mathewkb.com/china/yg108-firmware/

But I want to put QMK/ZMK/VIA/VIAL I don't know which one I want and I don't know how.

But I'm hoping I can do so without using the manufacturer's software ?

When I plug it in while usblogview is enable I get the following logs

10 years ago I went to private trackers that had extensive collections, everything with dozens of seeds. And you coukd seed whatever you download and it just wouldn't get downloaded. It would use up your hdd space on the seedbox whipe nobody could download them either as tgat would wreck their ratios and get tgem banned.

I was so disgusted I never even tried join otger private trackers, time wasters the lot of them.

Also I've seen some disgusting thieves SELL ratio fixing at outrageous prices.

Of course intellectual property is stupid garbage idea. But pirates selling shit is so much worse. Even worse than the continued demonic existance of Disney.

Another strategy was to downloaded whatever just got posted and seed that before there were too many seeds.

A kind of ratio pump and dump rugpull.

Such shitty behaviour enabled by the pretense that space and bandwidth are limited ressources and then waste both of them to create an invisible paywall.!

The 12 step 2 factor login process 4 times a day really pisses me off. ESPECIALLY that last screen where you are logged in but it makes you press another NEXT as punishment for not staying logged in all the time.

Really super annoying how they are using such manipulative behaviour to punish those who protect their privacy

One frustrating trend I’ve noticed in many open-source projects is maintainers closing issues as quickly as possible—often in a dismissive and even confrontational manner. It sometimes feels like a game, where the goal is to shut down as many issues as possible rather than foster meaningful discussion.

But here’s the thing: issues aren’t just demands for the maintainer to do work. They serve a much bigger purpose in open-source projects:

✅ They help users realize they’re not alone—people with the same issue can come together, share insights, or even hire someone to solve it.

✅ They serve as documentation—a record of what’s been discussed, what problems exist, and what solutions have been proposed.

✅ They create opportunities for new contributors—someone trying their hand at coding might pick up an issue, or someone with the same problem might decide to implement a fix.

✅ They signal what users actually need—even if the maintainer doesn’t plan to fix something, an open issue can indicate demand to potential contributors.

But when an issue gets shut down immediately, all of this breaks down. Closed issues don’t appear in GitHub’s default search, meaning 99% of people who might have seen it now won’t. This leads to:

• Duplicate issues because users can’t find past discussions.
• Missed opportunities for new contributors to pick up low-hanging fruit.
• Users feeling unheard, which can make them disengage from the project entirely.
• Preventing others from seeing the issue and potentially contributing.

So why do some maintainers do this? Why Maintainers Close Issues So Aggressively

There are a few common reasons:

🔹 Burnout & Overload – Many maintainers are drowning in issues, and closing them fast is a survival mechanism.

🔹 Entitlement Fatigue – Dealing with demanding users can make maintainers defensive and dismissive, even toward good-faith issues.

🔹 “Keeping the Board Clean” Mentality – Some maintainers see issues as a to-do list, not a place for discussion. They close anything that doesn’t fit their personal roadmap.

🔹 Power Trip – Let’s be honest—some people just like saying “no.” They get used to shutting things down and enjoy exerting control.

🔹 Lack of Interest – Not every maintainer wants new features or community discussions. Some prefer to build things their own way and reject anything that doesn’t align.

Of course, every project is different, and maintainers have the right to decide how they manage their issue tracker. But closing everything by default discourages contribution and community involvement. A Better Approach?

Instead of aggressively shutting things down, maintainers could:

✅ Leave issues open for discussion, even if they don’t plan to act on them.

✅ Use labels like “help wanted” or “waiting for contributors” instead of closing things outright.

✅ Let issues sit for a while to gauge community interest. If nobody cares, they’ll fade naturally. If people keep commenting, that’s a sign it’s worth keeping open.

✅ Recognize that open-source isn’t just about code—it’s about community. The issue tracker isn’t just for them, it’s for everyone who might contribute.

What’s your experience with this? Have you seen issue-closing behavior that helped or hurt a project?