[-] leetnewb@beehaw.org 2 points 1 day ago

ShieldsUP is fine. Also check out: https://www.routersecurity.org/testrouter.php

You could also just port scan yourself with something like nmap.

[-] leetnewb@beehaw.org 16 points 3 weeks ago

Apple has turned out to “prevent the chrome monopoly” far more effectively then firefox has.

Turns out that owning the platform (Android, iOS) counts for a lot. I like having an independent option.

[-] leetnewb@beehaw.org 12 points 1 month ago

Technically true, but FOSS isn't "free" in the sense that someone is contributing labor to build and maintain the software. Free to use, but not free to make. I personally wouldn't expect or shame a person for using FOSS without contributing. But if you make a profitable business off a FOSS project, it seems reasonable to expect some form of contribution back to the project - not because it is technically required, but because who better to sponsor a project than someone profiting from it?

[-] leetnewb@beehaw.org 15 points 3 months ago

Sad news. Here is a link to an impact study (PDF), which describes many (all?) of the projects that benefited from funding. But a few you may recognize include Lemmy, Kbin, and Mastodon:

https://op.europa.eu/en/publication-detail/-/publication/257ae66f-23c7-11ef-a195-01aa75ed71a1/language-en/format-PDF/source-324755022

[-] leetnewb@beehaw.org 15 points 8 months ago

I always find responses like this funny. You know how old you are, but (mostly) nobody reading the comment does. You could be anywhere from 11 to 50!

[-] leetnewb@beehaw.org 17 points 10 months ago

I mostly blame Apple for walling off the default text messaging app on the iOS platform. It is ridiculous to me that we are over 10 years into the smartphone era and are stuck in a duopoly with two players that would rather degrade communications between platforms than prioritize interoperability for some base level functionality. I hope that Beeper's campaign forces regulation that puts an end to the insanity.

[-] leetnewb@beehaw.org 56 points 1 year ago

You can point out back and forth violence going into the 1800s. Nobody has clean hands in this conflict.

[-] leetnewb@beehaw.org 33 points 1 year ago

I think the headlines play on mushrooms for outrage and clickbait. It makes readers feel better that there is something tangible that can be "controlled" rather than a hard to define cause of someone's seemingly functional brain misfiring badly.

[-] leetnewb@beehaw.org 25 points 1 year ago

Another article said he did shrooms 48 hours before the flight.

[-] leetnewb@beehaw.org 12 points 1 year ago

The ADL was barely covered in the article. It was mostly anecdotes of jewish college students being or feeling attacked for outwardly expressing identity. I don't think you meant it this way, but leading by questioning the ADL's behavior seems to miss the point.

[-] leetnewb@beehaw.org 30 points 1 year ago* (last edited 1 year ago)

Selfishly, I would like to see beehaw remain on the fediverse. I enjoy the community, the curation, and desire for strong moderation. It is a great window to the broader fediverse link aggregator community. Beehaw's ideals and structure clearly appealed to many Redditors and the like. The concept of federated communities seemed appealing, and beehaw is an important voice in the evolution of the moderation of a federated network.

However, the sacrifice that the admins have had to put into making the platform survive while the software finds its uncertain way through a mountain of growing pains seems unsustainable (just my pov through the last 3 months) - not just on the technical side. There's that saying - when you find yourself in a hole, quit digging. It's hard to see how moving from Lemmy to something more sustainable, if it exists, would be the wrong move.

Painful decisions rarely come with a flashing light that scream "now's the time" - but the loss of your major technical contributors sounds stunningly close.

Edit> fixed a typo or two

[-] leetnewb@beehaw.org 16 points 1 year ago

The rise of distributed computing was at a time that CPUs didn't really throttle down. CPUs in general were just a lot more power hungry. But if you had to leave the computer on for some reason and had spare CPU cycles, it made sense to contribute them to a distributed computing project - the power was being spent anyway and it seemed like a good cause. Today, modern CPU sip power and throttle down and you are actively driving power consumption by taxing the CPU. There is a much less favorable cost/benefit equation today, but in terms of the cost of the power consumed AND the climate cost of the power consumed.

view more: next ›

leetnewb

joined 1 year ago