skysight-inc/HackerNews huggingface dataset:
> One survey suggests that U.S. workers were logged into their employers’ networks 11 hours a day in 2021, as opposed to 8 hours a day before the pandemic.

A mentor of mine many years ago gave me the best advice: work sane hours, and live a life outside of that. He'd hold me accountable too, and say "It's 5:30, we got here at 9:00, we're going now" (half seriously).

The rules I work by:

1. Work 8 hours per day, 5 days per week.

2. When 1 isn't possible, work a 40 hour week.

3. When 2 isn't possible, average a 40 hour week per month.

4. When 3 isn't possible, talk to management about the problem and find a solution.

5. When 4 doesn't work, find a new job.

I have never needed to get to number 5, fortunately, but I hold myself accountable to do so. I have a family and they are my life. My job exists to support my life.
Are those cinema projectors or more like video projectors? The cinema ones are more heavy duty and not changed so often.
I listen to my tinnitus.
Even then, ELF is only available down to depths of hundreds of metres, not kilometres.
I have both. 90% of my tests are normal unit tests that use mocks or fakes as needed to test the things I care about. 9% are integration type tests that validate broad behaviors with my app’s direct dependencies in an ephemeral environment managed via docker compose (usually anyway). 1% is a couple end to end tests that validate the whole system at deploy time and beyond.
Teams is designed for a world where the problem that Slack solves is viewed as a feature. Looking at them as comparable instant messaging tools is to completely miss the point.

The underlying philosophy with Teams is top-down control: the assumption is that the organisation structure can adequately predict what communication patterns between its members should be allowed.

The underlying assumption with Slack is that the organisation members should be able to set up productive communication patterns without needing top-down control, and that having to impose that control is a bug.

The Slack approach requires discovery and working in the open, to a certain degree, so that what the research calls "weak links" can form between individuals in disconnected parts of the organisation. Teams (at least, wherever I've seen it) is actively hostile to this: you have to invite, to be invited, to already know who to speak to. Slack - when done right - radically changes how the organisation integrates with itself.

I have, of course, seen it done very wrong: if you come from a Teams world you'll likely want to lock Slack down so that it can't provide its main benefits; the instance I'm on right now blocks public channel creation, which is bonkers if you understand the problem area.

If your org is small enough and has enough of a mixing function outside the digital tooling that it doesn't need a helping hand, then there's not much in it, but past a certain size and it's not even close.
Italy: newspapers used to have a page or two with the movies and times at each theater of the city for today and the next few days, plus prices. You could always find a friend with a newspaper, or somebody would buy one to check the listings. Then they started to give away smaller newspapers for free at subway stations. I can't remember if they had movie listings but the sales of established newspapers took a hit. It was the time when everybody started to have a phone on their pocket or in hand to play games.
It's a bit more nuanced. Let's keep it simple and say you produce 3 data sets when browsing and clicking on results: search queries, DNS queries, HTTPS queries.

If it takes a correlation of the 3 datasets to identify you, then it is better to use 3 different providers.

However, if any one of those datasets is sufficient to ID you, then it is better to choose a single provider.
>> this particular category has someone who enforces a huge list of arcane rules.

> [...] I think a few months with new eyes will show why those arcane rules exist. Losing that tribal knowledge just means the sub will re-experience the same growing pains [...]

I also predict that most people will not even recognize that what they are witnessing is a repetition of what happened before. I think the math of growing a community means most users have joined after the rules (that make the community a decent place to be) were established.
I don't think you are getting my point ... waste and water treatment and power generation are things that go down in cost with scale. Trying to get waste treatment and water purification and power generation to operate at the scale of a few 100s of people isn't viable.
To be fair, Slack also suffers from the "write-only medium" problem.
The big challenge with XSLT was that the basics were verbose but easy - just pulling fields from the xml and putting them into a template. But then you ran into things that's simple with other solutions, like re-formatting dates and ended up with either humongous functions or biting the bullet and including multiple pre-formatted versions in the XML, and the moment you start down either of those paths you start to dislike XSLT pretty quickly.

In a way modern React etc. frontends can be seen as a "fix", in the sense that at least it means most sites effectively have APIs, whether or not they officially expose them to users, but without the pain of XSLT. If they support server side rendering as well, they're getting close to what we were doing.

And that was the original driver for the site design I mentioned - every URL was an API endpoint with a well defined set of expectations, letting you effectively explore the API by browsing the site as normal until you had sliced and diced the data the way you wanted and then just add a parameter to get it in the format you wanted (just as you can with Reddit - e.g. append ".json" or ".rss"). And I try to do that as much as possible still.
New Report: Generative AI threatens consumer rights
the parent's point was to compare the set of reserved keywords in the two languages

types do not enter the discussion
That’s a whole other can of worms! The difficulty of versioning stored procedures is such a detriment to effectively using all that power.
I cannot count the number of python and perl tests leveraging mocks that we inherited that after we dug into them, there tests were asserting that 1=1 exactly as you say. "Make the db return hello, insure we returned hello; yay, framework works?".

Unit tests should validate error paths are properly exercised and that we handle expected results appropriately. It is wild how often this is not expressed in unit tests.
The web page still has a statement on Year 2000 compliance. Quaint.
Can you do more of a write up on the software side? How does proxmox get an internet connection for updates, if OpnSense is virtualized?
lemmy.world seems… slow
> why the hell there are people interested in this? Is this clinical sadism? I don’t see how we, or they, are given an evolutionary advantage by being like this.

Some people are doing this for a living. See Guantanamo Bay.
I have to say, watching this car crash in real time has ironically made me browse reddit more, just to watch the drama unfold. It's the same with twitter, these community sites have become so big, that the actions they take themselves are newsworthy.

The way this is unfolding, I can imagine this being a case study in a future revision of 'how to
win friends and influence people', on completely what not to do. If that book is worth it's salt, then reddit's management complete unwillingness to work with its community, and constant lies, leading to virtual riots on its sites, should result in it's total collapse.
Thanks, yes - might well be the CryptoHack suggestion. If so it's certainly been redesigned since I last looked.
Interesting article. I didn't know about JSP Model 2.

Another detail that's not mentioned, but very useful for understanding the original pattern, which is described in [1], is that controllers had a specific and unique responsibility in the original system where the MVC pattern was defined: The system gives the input focus to a controller, not to a view, so you can't accept keyboard input without a controller. So, unlike pretty much every other GUI toolkit, it's not a matter of having the view delegating input to a controller as a matter of good design, but rather that the controller is simply the way that the system provides the input to the application – you have no choice in the matter. This also meant that there was one controller per widget that could receive focus (corresponding to each HWND in win32), not just one controller per screen.

The same document also contains answers to some frequently debated questions about the true, proper and orthodox way to do MVC: Should the view subscribe to model or should the view updates be mediated by the controller? Should the model represent the pure domain logic or also contain view-level state? Should the model be a simple value object or also contain domain logic? It turns out the answer is: All of the above! The original MVC in Smalltalk apparently used all of these options in different applications depending on the circumstances.

[1] https://web.archive.org/web/20100921030808/http://www.itu.dk...
No, if reddit does that they lose a giant amount of traffic. And reddit search sucks they should improve it first if they want that. But also for many things you do not necessarily search for reddit but just search a question and reddit turns up in search results. If that goes away, reddit will have less visits and become way less usefull for many things
Milwaukee harvests sewage sludge into Milorganite fertilizer.

https://en.wikipedia.org/wiki/Milorganite
Yeah, there are valid ways to use the data. Looking at the parent again perhaps I was misreading it; I was responding to the idea that you could find the correlation and just go straight from there.
Lemmy seems to be OK. I clicked on https://lemmy.ml/c/apple and was entertained and informed rather than the content being about the protest, or about how great some new platform is.

Someone that can hack Swift and likes money:

please make a Lemmy app. Currently there's nothing in the iOS App Store. I will pay 5 dollars. Probably other people will too.
Carrying the work device? That’s the expectation where I work. The norm. What if something happens?

Mine still gets put down and ignored when I’m done my day.

People hate this.

People hate that I’ve disabled my notifications too, but when I ask “do I respond in a reasonable amount of time?” the answer is always “yes”.

Be the change you want to see, and all that, I guess.
go's error handling is not catastrophic, it is very good
This is a great idea and I think I heard a few good ideas and even thought of my self a few, about how Reddit could be more profitable. Which is weird, why they went with the API model. It's really suspicious. It's like they want to raise its value fast and dump it. It really looks like the want to sell Reddit.
Why should 1 person or instance own rust? Why should they be linked. They aren’t the same thing. The namespaces are rust@programming.dev and rust@lemmy.ml so on obviously they aren’t the same thing.

You’re confusing instances with communities. Instances are servers. People create and mod communities. They shouldn’t be linked because they have different mods and rules.
the mods and power users must fed up with Reddit probably contribute 80 percent of the content, even if they are a minority. Without content what exactly is Reddit? nobody will fill this void because of the nature of a lot of these subs. I mean you really gotta be obsessive a little to continuously moderate weird niche subs like birds aren't real.

A lot of subs will probably switch to bare minimum policing, which is to say only site wide rules which basically turns every sub into a free for all like /r/worldpolitics.

You think it's easy to replace 4 to 10 moderators across 8000 subreddits? I sure you, it most definitely is not.
India’s IndiGo places record order for 500 A320 Family aircraft
> If you're going to add a dependency you may as well just use a "real" language at that point.

Not necessarily. It's still easier to manipulate shell programs in fish[0] than it is in Python since fish was made explicitly for that. Calling external programs, using pipes, process substitution, etc. are easier in a "proper" shell language.

[0] Or any bash alternative of your choice: nushell, oils, xonsh, elvish, etc.
Gaming consoles do expensive 3D rendering. 2D must be much cheaper, otherwise the Sony phone couldn't do it.
That's why I used to do when living in Tokyo. I would look on Google maps and find any interesting looking water feature (I like looking at large bodies of water) and then just drive in that general direction.

Sometimes it ends up being a dud[0], and sometimes you find something amazingly beautiful [1][2][3][4]

[0]: https://goo.gl/maps/FoE51Cc8KzJVCocn7

[1]: https://goo.gl/maps/z5CMS4NpTAukgNct9

[2]: https://goo.gl/maps/ZEBCbw6d1h1YWFAYA

[3]: https://goo.gl/maps/A6ZHCT97z2kdrxas9

[4]: https://goo.gl/maps/SxLk2S4D1jFkDhU69
This might be the solution. RSS readers could serve as a general link aggregators (like HN), but with immediate listings of the latest content from your favorite sites. Too bad most just prefer to get rid of RSS entirely.

On the other hand, I don't necessarily dislike the email model (especially when having dedicated address just for newsletters) but it's much less comfortable than RSS and quite limiting from the publishing standpoint (given how far behind emails are behind modern Web).

Personally I still try to have RSS in all my content websites (with full content) as I'm primarily thinking about reach rather than ads. The ones that I haven't implemented RSS for yet, are just because it was more challenging or required more effort when integrating with e.g. CMS or something.
Aaron Rodgers’ Online Sports Database Aims to Crowdfund $1.25M
The light bulb moment for me learning git, which I don't see get mentioned nearly enough, was this:

Stop thinking in terms of branches, and start thinking only in terms of commits. Pretty much every git operation makes so much more sense when you consider your repo just as a tree of commits (technically a DAG), rather that trying to reason about what it does to the branches. Branches are really just pointers to commits which can change over time, and most git commands don't really care about them.
“I cannot conceive of any vital disaster happening to this vessel,” said Captain Edward Smith, commander of the Titanic.
Author here. What many people claiming "RSS is dead" for the last 20+ years mean is that RSS-as-feed (for written content) is not mainstream, and that's somewhat true. Most podcast listeners don't have a proper RSS reader apart from their podcast app. Also, big platforms removing existing RSS support is often taken as another sign of RSS dying.

What's interesting is that this particular post had been posted by someone on HN before I've shared it anywhere. So it got through RSS right onto the HN front page. This is what I meant with "thriving, especially among tech users".
Even more reason not to pipe the little water we have right into the ocean.
GPT4 produces dubious Rust code all the time for me, especially when I point out mistakes. It gets into a cycle of doubling down on mistakes and degrading into more and more bizarre solutions and gets into a loop of repeating itself.

It gets the rough outline of a solution OK but very easily gets lost if the problem requires 2 or 3 levels of what I guess I'd call nested analysis. Or rather, it's fine for creating a surface solution, but it gets lost in the weeds quite easily for things like type system or borrow checker problems.

Because it doesn't reason -- it (re)produces patterns.
U.S. withdraws some charges in Sam Bankman-Fried case
You should close the lid before flushing anyway... Stops bacteria spraying around
I am able to implement complex logic without using this new "functions" feature, I am considering using it with the agent implementation, but might not need to as the new GPT4 version improves on it's JSON handling so that is already plenty robust for my needs..
"Some other software" that uses/adds users and groups on the system, is not part of the implementation of users and groups in the system.
That isn’t 100%. Instances can be blocked from federating. For instance if you are on lemmy.world you are no longer getting beehive posts because beehive disabled federation with lemmy.world

I think kbin has the best interface and I am hoping they get “multireddits” implemented soon so you can combine communities from multiple servers into a single view
During the Digg migration, the main criticism I remember is that Reddit was ugly but still usable. For casual users of the fediverse, I think the criticism is that kbin, Lemmy, and Mastodon are actually too confusing to understand and therefore unusable, which is a key distinction.
In the end someone has to pay that cost anyway. Overbuild your intermittent sources (and then throttle them when there's oversupply), invest in baseload power (e.g. nuclear), keep using fossil fuels (and pay the environmental/health cost), build storage or curb demand (the case you mention).
Yeah, tried the same with Lemmy. A list of half done of dead communities, all of them with zero explanation of why and how.

Then i read about the codebase and people were struggling with SQL so performance is bad - i mean what? is that really the state things, where's the talent working on this?

I'm honestly surprised that both the design, performance and docs of these alternatives are this bad in 2023.

If this has to work you need an extremely simple and well designed landing page with a super simple explanation of how this works, the creation of a user should work on more or less all instances, and you should be able to easily meta search for the communities you want and get an easy overview quickly.
The question is whether the problem happens a lot or rarely. I’m saying Kubernetes is a bad example of the problem happening a lot because it’s a ton of code (which yes, is poorly written), and CockroachDB is a good example of it happening a lot because there is less code and it’s at a higher quality.
Just a commentary that if you could save a bunch of companies 70x then that is the easiest sell in the world. I WISH I could do something like that because I would be a billionaire haha.
4 Die in Fire That Began at E-Bike Shop Near Chinatown
Just told you, there's no delete button.
I’m a wealthy local with a wealth management bank account. It took me 7 weeks and I had to file literal volumes of paperwork with help from an accountant to open a bank account when I moved home.
Giving people money they need to survive conditional on them doing work that isn't economical is that.
Ah, that would probably be Llanfair­pwllgwyngyll­gogery­chwyrn­drobwll­llan­tysilio­gogo­goch.

See: https://en.wikipedia.org/wiki/Llanfairpwllgwyngyll
There are plenty of line of business systems that even today integrate by putting a request document on an ftp server, then polling the server for a response document.

These systems are there for the same reason COBOL and RPG are alive and well.
The Dunning and Krueger approved way.
We got hold of the phone number of a free taxi phone at the cinema in my town, and instead of reading the paper to see what was showing when, we'd ring the taxi phone and ask people what was listed on the "now showing" board, people were surprisingly happy to recite it to us.
Not so sure about podcasts. At least where I am from (Italy) a great deal of podcasts are either Spotify exclusives, or consumed mostly through Spotify, or bundled in some producer-specific app (e.g. the state-owned radio does this, and doesn't provide feeds).
In the 1980s I worked for an arcade company as in the guy who collected the coins not manufacturer or developers of them. We also had some grey poker (not legal not illegal). I was on call one week each month at the time the pager was huge. Literally paged as in the person called a number and then that service called the page with the number saying it in a voice call over a radio.

Then early 2000s I worked for government lottery and was on call one week out of three. It was a cellphone I think we got voice or text but then later email.

Then a tech at a casino where I had a cellphone with email and it was constantly going off. So life was good up until about 2005.

For government lottery I got paid three hours for any time up to three hours. Then after that it was regular pay. So if I got the job done in 30 min I made money if not it was just a regular pay.
Normally 200% capacity cost quite close to 200% of the capital investment.
Generally you want to use what your users use. Running common adblock lists as a dev can help identify /weird stuff/ early.

Plus genuinely the privacy list is good. Just not when it stops the ability to build good.
I am astonished that people just start to realize this.
And what the point to make `if err {return err}` in most of cases? I've read a lot of code and error handling logic almost never in caller location.
Gonna dig this. Cool. Why Rust btw?
Well depends on your definition of evil. If it ever becomes the expectation for a 9-5 admin job that you have to reply to your boss when he sends an email at 2am, while you're asleep, I'd call that evil.
Yeah, that's roughly aligns with what I've experienced. RSS is beneficial to publishers when reach is the top priority (e.g. it's a company marketing blog or the ads are "embedded" directly into the content).
As far as I can tell, the QLED screens on the market are not based on the QLED technlogy that article is about, and the lifetimes given in that article are obviously far too low to build a usable television set with. They claim non-uniform degradation between different colours with blue in particular dropping to half the initial output after just 20 hours - that's nothing compared to the life of a TV set. Samsung QLED TVs seem to use standard LEDs in the backlight with a seperate quantum dot layer that improves colour accuracy and gamut.
https://exploding-heads.com/
OLED panels willl always suffer from burn-in in some form. What I meant by "is it a thing" is "will users ever experience it to a detectable degree". I guess the answer here is "No" then.

I've seen the video where the guy leaves a bright high-contrast static image on his Nintendo Switch OLED for 10,000 hours before finally seeing a small amount of burn-in, but that's not the level that should concern average users. Was just curious if typical large screens fared any worse than the new Switch.
This is when people design their type system which decrease performance by a factor of 6. Such as with python or typed racket. Of course people are getting angry at types, when

* it's getting slower,

* there are no run-time guarantees,

* there are no compile-time errors.

With normal type designs you expect a performance win of about factor 6. With compile-time checks in place you can get rid of previous run-time checks. Also with const values.

A type is a *guarantee*, not some hint. Compilers are always better to produce type hints than users, if someone types his variables and functions these must be guarantees of course.

They need to improve safety, documentation and run-time performance.
Even with dynamic languages where the compile-time cost is added to the run-time cost, it should still run faster, not slower. Even with added compile-time type checks.

When I added types to perl5 before all the others started with their attempts, it became faster and safer. Then my eyes started watering when ruby, racket and python did it wrong, whilst perl6 and php did it right.
Apigee and Kong API Gateway Comparison
The point is with two devices, you don't actually have to carry both around at the same time. You can leave your work device at work or in a drawer.
Seems like a way to curb costs..It is quite common that plex server enthusiasts will run their entire piracy automation over good always-on VPN services and that requires port forwarding to do so. AirVPN still does it and I have had an account with them for far longer than any other VPN service.