Cooper8

Does the BW-16D1HT offer good performance for 4kbluray playback as well as ripping? Looking at it it seems price competitive with the stand-alone players, and if it is good it would make financial sense to buy a dedicated pc and enclosure as an alternative to stand-alone player assuming it can drive HDR and Atmos

Awesome, this is huge news.

One of the biggest and most underrated things you can do now to prepare for a job search os have your current coworkers and managers endorse the skills you listed above on your LinkeIn profile. This is powerful both because it validates your resume (for real people and AI reviewing it), and gives recruiters a way to find you. With your skill set you should have plenty of people coming to you asking if you are interested in work without even pursuing applications yourself.

What kind of CAD software are you proficient with? What type of designs have you mostly focused on?

https://www.dptechnics.com/en/products/walter.html

this looks promising

https://www.qualcomm.com/developer/software/qualcomm-linux

hmmmm, sounds like a mix of open and closed source, but a good starting point.

Good point, and it will have high speed wireless.

There must be a 4g antenna chipset that is Linux native for industrial use.

me at the rave

glad to see this info getting slated on an official channel.

I appreciate the fundamentals of the effort, and I also wonder whether this will trigger an IP strategy response from the major manufacturers.

It seems like a complementary FOSS chipset project would go a long way. I look at Linux native hardware like the SteamDeck and wonder, what hardware is lacking from this stack to make this device a phone?

Definitely true.

“you could block logged out users but that would impact many lurkers”

“regardless you might not be logged in at all, you should still be allowed to browse content”

Fundamentally, what I’m suggesting is a fork in the road. Either an instance admin can set up to eliminate scrapers by making the instance private to only registered users,

or they can maintain their instance as public and deal with more arcane methods to attempt to eliminate scraping.

The issue is that if the infrastructure isn’t in place for the instance operator to decide to make their service private, then everyone is opted in to the Scrapers vs Countermeasures war with no alternative.

Privacy and encryption just work, it seems like not building the infrastructure to enable the network to function with them in place is a mistake.

To me, and to many users, what we want is fast load times, quick federation, and reliable service, all things that benefit from reducing traffic load to only registered users.

Fediseer seems like a good solution, essentially a whitelist vouch system with touching at second hand.

Regarding the media hosting, again it seems like something that could rely on a method of identifying the user request directly with their user account before responding to the request. Cookies could be an option for this, though they are falling out of favor. Alternately, and more securely, it could be a cryptographic handshake where the user’s home instance and the instance hosting the post generate a public key using their two private keys for the user, and the user provides the public key when making pull requests from the federated instance. The keys could be batch generated when an instance first federates content with another and then assigned to user accounts the first time the user makes a pull request through a link from their home instance to the federated instance.

Secure Scuttlebutt Protocol already deved the encryption methodology that could be cross applied for a lot of this: https://ssbc.github.io/scuttlebutt-protocol-guide/ though I am of course not suggesting SSP be adopted whole cloth, and there are a bunch of other OS projects with encryption that could be used. This is just the one that comes to mind.

(edit: also I am in favor of finding methodologies that work whether CloudFlare is used by the instance or not, obviously CloudFlare has advantages but as we have seen also is a vulnerability of the network.)

The thing that confuses me is, wouldn’t a whitelist for federated instances and request frequency throttling at the account level solve this issue?

I suppose this would require that the client not have a public front end that keeps full navigation functionality, but for a smaller instance that seems like an easy sacrifice to make in exchange for stability.

“But then how will new instances get federated?” maybe they have to actually talk to the admins of other instances to get vouched in to the whitelist. Just because the network is distributed doesnt mean it needs to be fully inclusive by default, and in fact it explicitly isn’t.

I’m assuming I’m missing something super basic that makes all this not enough, bots spoofing the requests with the credentials of a whitelisted instance maybe?

Seems like maybe the instances should have encrypted keys that handshake each other with batch requests.

Am I on to something or just wildly gesticulating?

the downvotes are for “neat”

aren’t I glad I just bought an Onn instead.

Unfortunately the Big Beautiful Bill gutted the US utility scale Solar industry, and while it makes up a relatively small percentage of total solar installations, I do wonder if it has had follow-on effects.

The US is hitting an energy crisis, electricity rates are skyrocketing, any failure to build out any source of power seems perverse.