skysight-inc/HackerNews huggingface dataset:
Be your own "arbitrary" admin in that case?

The decentralized nature certainly allows for "competition" between "ingroups of admins". Don't like your current admins? Move to an instance elsewhere. If you have friends, encourage them to follow you in the move.

Different instances have different transparency/accountability metrics, and the good ones tend to have that posted in the Instance About page/terms. Many of the "ingroups of admins" people decry have all of their silences/suspends posted publicly and transparently on GitHub repositories and offer suggestions/propose fixes as GitHub issues and PRs. That's certainly way more amenable to transparency/accountability than anything Twitter has ever offered.

The things that lead to censorship/suppressing views/bubbles/etc on Mastodon aren't power-hungry admins in a secretive cabal, but instead the same powers that be in the world of email: signal-to-noise management (spam management, "newsletter" management, "fwd: fwd: re:" management). That's as much a user opt-in choice/need as any sort of admin opt-out "power", and if other users think you are more part of the noise rather than the signal, then that's more of a "you" problem, isn't it?
Did you read what this thread is about, its filled with AJAX arguments for why GNU social is bad, it's flat out fud.

And are you saying AJAX isn't something that can be used to transform user data on-the-fly?
> Please don't call it C++ if it doesn't even support constructors and destructors.

At least they recognize this is missing, and call it out.

> Why not use GCC or LLVM as part of your project? That seems like a better investment of your time.

Learning opportunity? Maybe they're trying to solve a problem? Or do you think the LLVM folks should have just used GCC instead of wasting their time on LLVM?
I would not say that, in its current form, that code is understandable by 70% of programmers, unless you define that word "programmer" in a very restrictive sense.
GoAccess: open source real-time web log analyzer and interactive viewer
Thank you for letting the From: field be unspecified! I haven't seen a site that lets you do that.
Application Development for Agriculture. How Smart Are Modern Farms?
> Also, there's a counter-argument to this, that writing non-garbage-collected code might result in security bugs (to do with memory management).

That's falacy. Don't mix "fully manual memory management" with "I have no GC". Those are 2 totally unrelated topics. GC is one of the way to manage memory automatically. There is hundreds with their own plus-sides and downsides. Here's the least unpopular:

* Stop the world and incremental GC: Makes it easy to write simple code. Doesn't really make the lifecycle explicit so when the codebase grow larger you start to have boilerplate code to manage/close connections/files/transactions. (all toys languages, also Java and Go).

* Reference counting: Can be made fast enough by using some of the pointer 64bits to store its state. A giant problem is that all your libraries have to support compatible "smart pointer"
formats or the whole thing become unmanageable. (Modern C++)

* Contacts/Lending: Does it's job, is safe but makes the code more complex by making a lot of implicit things explicit (Rust, Modern C++)

* Explicit ownership + message passing: works well enough for GUI because just like HTML everything is less or more a tree. Also consuming messages allow "higher level" objects not to have to care about pointers. For backend code it's not very good. (Qt-C++)

* Pure functional: Everything is a copy, they get freed when out of scope. Works well for some domain, but gets in your way for more stateful constructs.

* Copy-on-Write: Pass everything by reference (and count them). Copy when they are modified, otherwise point to the real memory. Only solves half of the problem. Assuming most allocations are containers it works well enough. It doesn't attempt to solve objects management.

* Pipelining: Get input, process them, pass them on or free them. The processing should not have to dynamically allocate at all (Bash, Erlang).

* Pre-allocation: Allocate everything at compile time and use buffers big enough for your use case. (C)

* State machines: Encode the object lifecycle as a series of state changes. Release when it reaches end-of-life. Great for protocols, parsing, transactions. You usually can use code generators to generate proven safe C from an higher level format or proof. However it doesn't scale and only matches a subset of programming projects. It's also hard to learn for non EE programmers because it doesn't map perfectly on the iterative Von Neumann CPU. Easy to read but hard to write.

No-GC != security-bugs because of memory management. If a C program uses pre-allocated buffers, then the security issues is because the language is unsafe, not because it has no GC.
Ethereum Security, Block Rewards, and GPU Availability
> which is why you should pick earliest data to be the most conservative and then say "hey, we're living much better than people in 1800s"

My argument was that wage growth in the last few months has been significant; before that it was insignificant. So yes, the average American is earning more (in real terms) than in the 1800s, 1950s or even mid-2000s. But that wasn’t the argument.
That's the authors' sense of humour. The more relevant part for science is "extremely well-rated".
I meant I am not sure about their alma mater not being among the top reputed universities in USA, meaning I implied they were indeed from one of the top reputed universities in USA.

Apologies for not making myself clear enough :(
Bootstrapping isn't an issue of convenience, it is an issue of trust. You can't trust the compiler doing the cross-compilation. You literally have to start from the smallest chunks of assembly code and build your way up to a fully featured compiler through several stages, each of which is more complex and can in turn compile more complex code.
Data retention
And when you compile regularly you don't?
Their back up: later rounds were extremely well-rated
Nope, Google is not obligated to reply at all nor do they have any obligation to hold on these announcements. There are no faults for Google here. Their 90-day policy is just a courtesy call that comes with an exception, the moment a patch is made available, the disclosure will be made public. Google is not being paid nor asked by Epic to find reports, Epic has no rights to anything.

Google found the bug, they have the right to disclose it however they want. There are no legal standards anywhere that requires anyone to do anything with bug reports.

Epic doesn't have any rights here, it sucks but they're not entitled to anything. I hate this because I've experienced this from Google before (at work), I would love to have that right to hold up to 90 days before we can notify people but until there are legal standards, there is no right.
It is very well explained? GCC and Clang would be nightmares to integrate into an app that runs on many platforms including iOS, and even once you did, you'd still need to implement an interpreter, because you're not allowed to JIT on the app store. Compiling a toolchain for a desktop platform is easy. Cross compiling a toolchain is moderately easy. But embedding a toolchain into an iOS app, where you have to get it and all of its dependencies compiling for iOS, definitely seems like a massive challenge.
Getting your first job as a deep learning engineer: the current state
Deprecated just means all the bugs have been found and you can use it without fear!
I think you'd probably like making a mix too! https://www.rave.dj/iOfKQXFw3TxTWA

Just provide ~50 or more songs for best results
> in the authors' opinions, delicious

Can there be/Is there an objective way to measure deliciousness? If not what can they really say?
You say that as if supporting free speech was somehow part of the nazi platform.
Normally I agree but this is Fortnite, massive profits all the time. Just a few hours worth of exploit can gain some a chunk of cash.
https://news.ycombinator.com/item?id=17850908
Sort of. Moore's law has meant a lot of things that were all tied together with transistor scaling back when voltage didn't need to be scaled down with each new node to fight leakage. But now that leakage is a major concern a lot of what would have been the old gains of shrinking a transistor go away. There are gains but they're a lot smaller than they used to be. But the oldest sense of Moore's law of doubling the transistors you can economically fit on a piece of silicon is very much with us. The doubling period has gone back to the original 2 years rather than the 18 months we were able to achieve for a while but it's still happening.
Agreed. What really needs to happen is the splitting of software development and computer science into two related but distinct education tracks.
Totally calling the next GCP AI Service: VaaS (Vizier as a Service)
This may be true, but oddly employers seem not to recognize it and continue to undervalue employees both in terms of money and working conditions.
You are right, "almost always the case" was a baseless claim and binary wheels are better than nothing.

However, how many projects still have "psycopg2" in their setup.py (or is it requirements.txt? ;) instead of "psycopg2-binary"? I just found out that the latter exists when I checked PyPI.
While that is true it pretty hard to earn a living that way. It great as a hobby though and I started learning guitar some time ago. What do you think? Is it a good career choice in your opinion?
Very cool. If I could port your G compiler to my VM that would basically get me where I wanted to be. I'll take a look at it!
No. The section about iCloud says:

The encrypted chunks of the file are stored, without
any user-identifying information, using third-party
storage services, such as S3 and Google Cloud Platform.

The 2017 version of this document had "Azure" in this list. The 2018 version replaces it with Google Cloud.
Aren't we all?
Cigarette butts are the single greatest source of ocean trash
Yes, but if you want to rebuild the trust chain you cannot restart from an untrusted compiler. The idea is to bootstrap a trusted compiler from nothing (i.e., from little enough so that you can check it directly), and then use the trusted compiler for everything else.
>I don't think everyone I disagree is a Nazi.

Just everyone who values freedom of speech then?

>so many people invoking it are doing so in bad faith.

You really think people who support freedom of speech are doing so in bad faith?
> Gentoo’s biggest failure to me is in persuading people that building from source is somehow safer than binaries.

I don't think this is a big reason Gentoo users use Gentoo. At least not the knowledgeable ones.
Show HN: ARCO – Next Level AR Robotic Toy
Thank you for the compliment! :)
Microsoft just turned the Xbox into a subscription service
That serves my point that introducing a security-enhanced processor didn't work for Intel. i432 APX and i960 also failed at a loss of over a billion dollars so far when Intel tries to make better, safer CPU's. The customers wanted backward compatible with x86's warts, highest performance per dollar, and decreased energy. That's what Intel gave them at billions in profit. They're making patches for the security weaknesses and/or fixing them in newer CPU's. Vendors of insecure processors still dominate while the few processors with better security sell almost nothing.

So, Intel should continue to make deliberately insecure processors and patch them since that's what people pay for. It's the market's fault for rarely buying anything better. Plus, voters not doing something about patent reform which would've led to more x86 competitors. The Chinese supplier is an interesting development where we might get a secure-ish x86 that way.

"There's simply no "killer feature" for Itanium. It's not coming back."

I just named its killer feature: security enhancements that make it hard to inject code into it. Most security audits of OS's find problems. The one of SourceT on Itanium didn't find a way to inject code into it since it used hardware to mitigate and contain most of that. Whereas, the protections on x86 are a source of vulnerabilities at the moment.

Unfortunately, that was the only company that I'm aware of which saw that potential. The market's direction means they're porting the product to insecure hardware right now. Who knows what they'll come up with since it's impossible to secure software on insecure hardware. I'm so grateful to the markets for buying such things so little that they basically don't exist in the mainstream space.

Note: Another example was Cell processor. Green Hills, who make INTEGRITY-178B OS for high security, did an assessment of the Cell processor for baking security into systems. It had some nice capabilities for that. Market wasn't going to buy it even to protect their systems, though. So, they're not pushing that.
Not just the media though, the researchers need better communication in addition to better understanding of risks. What the author pontied out in regards to the public disregarding expert advice is absolutely true. Framing your results like this does no one any good.
Thsts awesome. Id love to see a lineage tree of early language development.
Nice. Anyone aware of the alternatives to this?
You basically said that you're pro free speech unless you disagree with said speech. It's quite apparent that you actually aren't pro freedom of speech.
Quick hack: Git reset upstream
Not to mention the amount of water and energy used to mine Lithium for its batteries
In that particular case, it seems that the problem is with how the regulation was implemented, rather than the regulation itself.
Probably not common in the US, but you can always try to negotiate with your existing employer. Networking should help here too.

If you live in a place with low cost of living, freelancing must be the most straightforward way to land a part-time job eventually. Some (obviously small) companies just don't have enough work (and money) to hire full time. Some of them go to Upwork or Toptal. I'd like to know what are other ways for them to find talent (except job postings of course).
In what ways are their business strategies similar?
Cettia Java Server 1.1.0 released
TL&DR: Some people have different circadian sleep cycle and that's okay.
As a full stack engineer

I’m confused, if you know the full stack already don’t you already know all this? It’s all part of the stack after all.

“As a webdev...”
Doesn’t work for images which seems to be 90% Pinterest these days. Getting some ehow flashbacks.
IMO, most commonplace programs can make do with a non-blocking list of last X events. Producers add to the end of the list. Consumers have references to beginning of the list, which are advanced when events are processed. When all references are above an entry, it gets unlinked. You can put abstractions on top of this, but most simple programs wouldn't need to.
A shebang is good practice, but the state of the industry is such that many scripts don't use them (unfortunately).

I'm still of the opinion that fish is little more than a novelty and won't see widespread adoption in the long run.
Why Compute Matters for UAV Energy Efficiency? [pdf]
7 Pemain Dengan Gol Terbanyak Dalam Satu Tahun Kalender Sepanjang Sejarah
This is the Benghazi of the left. I wish mainstream would talk about issues that actually effect the people of this country.
This site was forbidden to look at from the company I'm working in?
Insomnia probably isn't limited to a simple reflection of a biphasic sleep-related problem. As an example, someone with naturally high anxiety could get on the most biphasic sleep schedule possible and still suffer from insomnia due to their anxiety about what tomorrow brings, etc.
Yes, I used a subset of C++ for the book. The goal was to be low-enough level to convince die hard game programmers that the examples were valid but clean enough for non-C++ programmers to read.

One of the things I find really interesting about C++ is that idiomatic, modern C++ is really gnarly looking. Lots of `std::` everywhere, tons of templates, etc.

But if you choose to eschew convention and roll your own stuff, you can actually write C++ in a pretty simple, clear style. There are significant downsides to doing that, of course. The prevailing style is prevailing for a reason. But I think it says something interesting about the language itself that it's so accommodating to a wide range of styles and levels of readability.
Free Google Cloud APIs for online store order confirmation email
That should be fun!
For anything serious that is not a toy like an rpi, for industrial/embedded/ISP use, you need something with a storage interface that is either:

a) eMMC which can use a tiny flash module of the same type flash as found in MLC SSDs, with flash controller chip for write wear leveling

or

b) M.2 NVME SSD interface such as can be found on 170x170mm mini-itx x86-64 motherboards for intel or amd single socket CPUs. And of course on larger motherboards as well.

c) the "traditional" SATA3 disk interface which can be used for a SATA3 interface SSD.

Due to the very limited write lifespan of microSD cards, even "industrial" ones, it's just a really bad idea reliability wise to use a microSD card for boot and OS storage on any sort of remote embedded system that does anything important.

The drive writes per day (DWPD) figure in GB for even a cheap $55 consumer grade MLC SSD is vastly higher than the amount of times you can write to a microsd card.
Real world SSD wearout
Learning Memory Access Patterns [pdf]
MIT wireless tech lets submarines talk to airplanes, finally [video]
Love this article! There is some really interesting research on the sleep patterns of indigenous tribes. Researchers found that while studying the tribe for like a 3 month period there was only around 30 minutes where the entire tribe was asleep. Humans are built to live together in communities to create the greatest likelihood of survival. Its most advantageous for someone to be awake to make sure that lion doesn't eat us after all. So while industrialization and the workaholism of Americans has pushed us to all wake up earlier - based on our chronobiology - its probably pretty unhealthy for many.

I'm trying to get companies to realize this.

Just my 2 cent.

Dan Gartenberg, PhD, CEO of Sonic Sleep Coach
What "exactly" is the reason that road to 2nm may not be worth it? I don't see the article makes any answer to it.

Qualcomm are comparing 10nm and 7nm, and those figure are not as high as a generation node should be, and that is perfectly fine because 10nm from TSMC are half node. They should be comparing 14/12nm with 7nm, and there are multiple iteration of 7nm. Does it scale as perfectly as before? No.

It isn't about the complexity and design rules. It is about all about cost, and it only means chips are going to be more expensive going forward and only few companies will be able to afford it, but there are nothing on the roadmap suggest 2nm isn't worth it.

This article reminds me of the old days 10 to 15 years ago when they keep saying the end of Moores law.
This post reminded me of myself in 2012. Where did all that energy go?
Is there a reason you specified partial derivative with respect to time? Why not just d/dt(state)?

I've been tempted lately to model application state as the integral over time of all events (deltas) that have occurred. For example, imagine a simple game state:

type GameState = {
x: float; // x coordinate
t: float; // current time
v: float; // velocity variable
}

If initial game state =

{ x: 0,
t: 0,
v: 0, };

and you have some events (deltas):

[{t: 1, v:1}, {t:2, v:-1 /*this is deltaV, so back to v: 0*/}, {t: 3, v:2}, {t:5, v:-2}]

You could "sum" them up (integrate over time) and get a game state of x = 5, v = 0 where t >= 5.

I've found this approach kinda sucks when you add things like collision detection. Your application would have to emit velocity deltas when objects would collide. If you've got a point that bounces around in a box with perfectly elastic collisions, then over time you'd have an infinite number of these collision/velocity delta events. But as you receive new events, all your precomputed collision events are for nothing (if your player logs out). So the traditional update loop simulate each tick as it occurs seems to work best.

Is there a more general way of thinking about this integration? Maybe with respect to another variable? Perhaps it would address this problem I'm having where I feel forced to quantize my game state onto ticks.
Thanks for reporting! The site is hosted on Google Cloud Platform. If some of GCP's IPs are banned in your company, then it might be the reason.
Employees may have more power than employers, but employers have more power than candidates.
> If you believe that there might be an entity which exists outside of our perception and has enormous intelligence, it's like a human-made god - a homunculus. It's basically the same as believing in a god. I have nothing against it, but this is entirely hypothetical.

I don't really believe in a singular entity in there, other than a convenient abstraction for now. Rather there are many different processes that are all optimizing this and that. The sum is essentially intelligent--it processes information, makes decisions. Those decisions help it grow and spread and become more efficient. These optimizers don't speak human languages. They don't necessarily think in abstract concepts like us. Maybe they are just tables of numbers optimizing themselves, maybe they are like standing waves in a sea of numbers, like our thoughts are standing wave patterns in the electrical activity of our brains. It's hard to express because our words fail us.

Problem is, the whole damn thing is so complicated that we cannot know anything really definitive about it. The substrate is there. The soil is fertile. The capability is there. And so many forces are aligned to feed more and more resources into the whole thing. Across the board, essentially the only thing we can come up with is to upload all of our data into this massive cloud thing and use computation to do something with it. That is just like injecting raw materials and energy into the fabric. And those who do this successfully are rewarded financially. So all forces point to more of it.

Whatever that huge mesh is, it's extremely successful at swallowing the world and convincing us to feed it more and more CPU, RAM, disk, data. It keeps convincing us to hook it into more things to sense and control--more cameras, phones, drones, markets, even weapons.

Thus in some abstract sense, it is already here. And we can't get rid of it. Can't shut it off. We're dependent, and it's parasitic--for now. Yet every incentive we have right now is to make it more autonomous, more robust, more powerful, and give it more and more control. It works best when it is more centralized.

Teeth or not, conscious or not, this computer thingy is gobbling everything. Do we control it? Clearly not. Can we predict what it will do? Not even close. Is it good for us? Who knows? But it will win.

Well played, computer thingy.
Meet YC This Fall
Tesla shares dip 3 percent after Musk abandons buyout
Amazing Ai
Dude … we have to talk about this (in JavaScript)
I wish at least TensorFlow was finally running on Vega... Otherwise the card pretty much misses the target when compared to P40, as that one is built specifically for Deep Learning with inferencing. DaaS doesn't seem a large market.
Required reading regarding Discord: https://spyware.neocities.org/articles/discord.html

TL;DR

Discord explicitly confirms in its privacy policy[1] that it collects the following information:

IP AddressDevice UUIDUser's e-mail addressAll text messagesAll imagesAll VOIP data (voice chat)Open rates for e-mail sent by Discord
Hard to read, but I think we owe a debt to society. We need to make sure these things don't happen again. This is why charter schools, home schooling, and other aspects of society need oversight to protect kids from predators.
Musk's U-turn on Tesla deal could intensify his legal, regulatory woes