skysight-inc/HackerNews huggingface dataset:
Yeah but it's yours. Replacing it is so much harder for you than it is for corporate IT which buys laptops by the pallet.

If you'd lost a work laptop ever than yeah I could see not wanting to lose another one, but the mere possibility of losing one isn't anywhere near being "the person who is always losing their work laptop".

Losing my personal laptop would be a big deal for me. Losing my work laptop, while still not ideal, is just what IT calls Tuesday.
Hopefully a good place to ask:

My family name .com is still available. That should be very rare in 2023. The name has only 4 letters.

It is also a word that is hard to pronounce in the english speaking world and I hope to get a reasonable price with that argument. Chances for a company with that name are slim and I also have no company or business in that name (normal employed software dev that I am)

The squatter in question has a form up asking for contact details and initial offer.

How would I go about doing that and what should I expect price wise?
ProjFS can solve some of the same use cases, but is different by design. It is basically local file storage with a virtual backend that can provide files and data to the local file system. Once files are local, the provider is not asked when files are accessed or modified. The provider can monitor changes and synchronize them with the backend (with chance of conflicts). The provider also needs to manually update the local view when the backing store has changes. It appears to be built for OneDrive. It is way more efficient for many use cases, but also requires more effort to synchronize and resolve conflicts.
> For anyone reading this who thinks all companies are like the one that parent described, I want to share that it is not true. There are plenty of companies who based their collaboration with their workers on other mental models than cogs-in-the-machine.

It's even more complex. While top management might give a rough direction, even within a single company different managers may create way different environments.
Pretty much a week after starting any web development job, you discover that 95% of making a site fast is simply reducing the number of times it has to call the database.

Typically, this means caching everything as much as you possibly can.

This is the same reason why Wikipedia can’t just roll out a cookie-based “revert to old look” option for logged out users. It would require caching every page twice since you’d need a file prepared for both skins. The reason they can have skins for logged in users is because they already bypass the cache for logged in users (to allow for individual user scripts and stylesheets to be run, among other things). Even then, things like article text and category lists are still stored in various database caches, hence why there’s a “Purge cache” option available to logged in users.
Yes. There is a (third party) GitHub page documenting a lot of the hidden code features, which you may like to check out. The excuse constantly given for all this arbitrary behavior is that "this is what it takes to build a high quality community". Considering this has resulted in what is just 'big-kid reddit', I strongly disagree with this position, but I guess if nothing else all these rules and unaccountable exercises of power serve to cultivate an orthodoxy that is strongly sympathetic to the leadership, which is I guess the true goal. YCombinator is not in the business of hosting a social network so it's not reasonable to expect anything from them really.
Since there's some confusion about this:

- The AI Act regulates both 'high-risk AI systems' and 'foundation models' and applies different requirements for them.

- 'foundation models' are essentially defined in the act as "very large scale and expensive generative ai models that will probably only be offered via API" (my words). The reason the act wants to regulate them is so that USERs of foundation models have a chance to make their downstream use case complaint if that use case is high-risk. For example, if I'm a health insurance provider and I'm using a chatbot enabled by GPT4 in my health insurance sign-up flow, then my system may be high-risk and needs to be compliant. I need access to some information aobut GPT4 (e.g. expected error modes, potential biases etc) to do that.

- The wording of the act makes a point of highlighting that your run-off-the mill open source generative AI project will not constitute a 'foundation model'. The exact scale at which a project will become a regulated 'foundation model' is not yet clear, but it can be assumed that it will be at least tens of millions of dollars. If you can spend that much on compute an researchers, I think you can spend a few k on becoming compliant.

- The technomancers article confuses requirements for High-risk systems with those for foundation models. (It also gets some of the high-risk requirements completely wrong, but that's another discussion.)

- The stanford HAL website does a great job with the facts! I really value seeing thoughtful contributions to the discussion like theirs. (Especially from an American institution!)
Are there tax implications to doing the work? I don’t understand the need to do the caculation.
So to be clarify, I understand from this comment and other in this thread that you are talking about a mostly CC system, with coherency messages and the full MESI transition; The only relaxation is that you allow an additional Stale state. I don't see what you gain here, you still need to send RFOs for every write (including plain reads) to not yet exclusive lines as you can't delay sending invalidates to other caches on a fence as otherwise two cores might be writing to the same cacheline at the same time.

I guess this improves the false sharing scenario as you can read from data on a stale line if the data you care is not the one that actually caused the line to go stale and a barrier is needed to fully invalidate it, but the cost is that your release barriers, instead of being cheap purely core-local effect, now have to cross the coherence fabric. This can move the cost from a dozen of cycles to hundreds.
As tolerant as Lewis was, he couldn't avoid revealing some of his early biases through his descriptions of brown girls as objects of temptation in The Pilgrim's Regress.
Sure. I use RethinkDB, which works well, but has been pretty much abandoned at this point. It's a good database, but it wasn't "in fashion" like many worse solutions were.

I am working on replacing it with FoundationDB. I want to have a fully distributed database with strict serializable semantics (see https://jepsen.io/consistency), and there is very little out there that gets the job done. FoundationDB is really impressive and works really well. I'm worried that it isn't "fashionable", though.

As for access patterns, I'm not sure if I understand the question, but I'll offer one thought: if you're writing an app, you don't need a "query language'. You'll quickly learn what your queries are, and the right approach is to restructure your data to fit your access patterns. Your "queries" will be written in your programming language of choice, not in the databases "query language".

I feel that the idea of a "query language" is stuck in our heads back from the days when the boss would come and tell you to produce a custom report from the database. It's just not how app databases are used these days.
Well, their Common Lisp setup was hilariously broken, not by fault of the language IMO...
Understand Feature Flags by Practice with Unleash
I found this insightful piece that explores the benefits and best practices of utilizing feature flags, with a focus on Unleash, an Open Source feature flag platform.
Some years back, the RIAA floated a proposal that would make you pay every time you listened to a song. You would never actually own music, you would just pay for it every time you listen to it like you were a radio station. It's just greed.
This hasn't been the case for quite a time https://github.com/LemmyNet/lemmy/issues/1773
I worked at a company with story point estimations, two (or for some, more) daily standups, twice a week planning and ticket estimation, retros, and who knows what else (e.g occasional scrum of scrums for a feature nobody understands, across teams and domains, with around a 100 people, with breakout rooms and presentations of all the teams' "commitments").

Every time I fought the double daily standups, the pointless plannings (where we plan when we know nothing, and by the time we get to work on the tasks, everybody forgets what they agreed on), I failed.

Once I wrote a script to fetch all the relevant data from Jira to figure out whether or story points give better estimates than simply counting up the stories (because of course Jira makes this as hard as possible for you to find out). I went through the channels, discussed it with different people, at every turn I added more info to the report demonstrating the pointlessness of story points, at each turn the data supported my argument stronger and stronger, across all our teams, for sprints going back years. After weeks of discussing it, we kept the story points, because "upper management wants numbers".

Now, I work at a company where we keep things close to the agile manifesto, we adapt as we go, and we aren't forced to play stupid planning poker, and we have twice a week a short sync call (15 minutes).

For as long as I have the choice, I'll not work for a company with Scrum and story point estimations.
Brave on desktop and Android now upgrades all sites to HTTPS
Similarly to carbon costs and derivatives, we can go as far back as we want (carbon cost since big bang, since factory, or from the store) or examine the consequences into the future or alternative timelines (opportunity cost).

It is an interesting idea, and a good thought experiment.

If we are going to quantify everything, we could also quantify the enjoyment of the item as a negative cost, saving us from stress or health or other expenses through its enjoyment. We do it with opportunity cost, so why not in the other direction.

In this case, from the top of my head. Buying a book and not reading it yet:

- Can provide value by showing that book on my shelf (despicable, but true for some)

- Can make me feel good by knowing I am contributing to the author income, or by knowing when I am bored I can reach for the book without intermediate steps. This benefit is immediate.

- Can be one step in a chain of steps bringing one closer to a set goal: preparing to find a new job by learning something explained in the book.

- Can help build long lasting beneficial habits like focus or language mastery.

- If buying the book in a shop, it can bring opportunities for social interaction, that are difficult to quantify.

So the value of buying a book is not necessarily the one explained by this model. We can choose other models where the book provides "some" value immediately.

IMO what we quantify is not objective, but a reflection of a perspective in itself.
I am from the EU, not an American. I am not anti regulation in general. An example of where this has happened before was with GMO's:

> In 2006, the World Trade Organization concluded that the EU moratorium, which had been in effect from 1999 to 2004,[12] had violated international trade rules.[13][14]

We had a moratorium for years and even now we have the most stringent GMO regulations in the world. This crippled GMO research in Europe.
ah! Reading about Vale, I was actually thinking about Vala, now I see! (I barely know Vala, just from compiling some GTK/Gnome related code).
Pick a different TLD and don’t fund squatters.
As usual the financial sector is responsible for basically all the financial problems.
> There is nothing wrong with developing software and selling it.

Sure, but the FSF (and others) may have an opinion on the license given to the paying customers, in order to not restrict them.

Otherwise, spot on; Open source is not a business model: <https://news.ycombinator.com/item?id=32287432>

<https://news.ycombinator.com/item?id=31293455>
DevOps Is Bullshit (2022)
Can't say D3 had any sense of progression either because you simply did the same rifts with a bigger number attached to them. You got bigger numbers on your gear and then added some numbers to the rift level.

Compare that to finally reaching hell Diablo in Diablo 2... or scratch that... finally getting past the blacksmith in act 1 hell :)
usa was literally putting backdoors into nist crypto protocol standards and these chips are called shady because they are from china
Ok how about this

It’s capitalism for any business / platform that gets big

And has shareholders that want profits
Isn't everything that's happening with Reddit ultimately because of the pursuit of profits above all else?

For me that's as capitalistic as it gets.

It's the same frame of thought geared towards employees.
This is not even accounting for the fact that outside of business practices, they have completely alienated developers, by showing them they will take their words out of context, adversarially try to pit users against them and give them 30 days to comply or else. Why would anyone want to enter in a business agreement with a company that does this, before even looking at price?

Also: reddit pinky promises to implement mod tools they've been pinky promising for more than 5 years. Back when overwatch 1 came out, I became a mod for /r/overwatch_memes (now dead, the subreddit without an underscore ultimately was better) and even modding this subset of a subset of a gaming community would have been impossible without the API. Several moderation features that I ended up developing a bot for (using the API), reddit had been promising to implement for some time, and none of them are currently implemented. If you've been a mod all this time, you know that reddit promises to mods are completely empty. It's been fine until now because you could rely on other tools but modding anything with regular users without these tools is impossible without significantly restricting rules on allowed content.
This is not memory safe. Having generational pointers to do epoch checking on dereference is a stochastic mitigation. It is equivalent to PAC or Chromium MiraclePtr but with even less defense against adversarial attackers, because any infoleak of the generation allows for forging of UaF pointers.

The "high RAII" concept is also not actually misuse proof. There doesn't look like there's actually anything preventing the user from calling free themselves instead of RemoveShipFromDisplayCache. The types are linear, but the final sink is always free which doesn't encode the full usage semantics.
DevOps; A decade of confusion and frustration (2021)
> What part of the phrase “unforeseen consequences” did you fail to understand?

Sorry, I didn’t see need to address paranoid fears.

> I really don’t get it. So this particular product doesn’t meet your wants. Big deal. They are millions of products that don’t mean my wants, you don’t see me crusading on the bloody internet asking for them all to be changed. I just don’t buy them.

I really don’t get why me wanting product improved mobilizes internet on a crusade against my valid complaints about absurd limitations of platform.
> Email providers very explicitly do care.

That wasn't what I was asking though – I was asking whether a user should care. Why should I care who else uses my email provider, if I never interact with them?

> You can be banned from gmail for especially egregious things for example.

Gmail will only ban you for "especially egregious things". The Mastodon Server Covenant clause 1 calls for banning people for things which Gmail would not consider "especially egregious". A big difference.

> Generally speaking, yes. We went over this before with Cloudflare

I don't consider who a CDN's other customers might be when deciding which CDN to use. I'm sure many CDNs provide services to websites advocating viewpoints which I view as foolish, even reprehensible–but I don't see what relevance that has to my own decision as to which CDN I should use for my own site.

> Many subreddits have bots, automod etc that will ban people that are from certain subreddits

I think that kind of behaviour is toxic, and I would never knowingly participate in any subreddit that did that. But, in any event, that's a community-level issue, not an instance-level one, and as such I'm not sure what it has to do with the topic of federation.
> run the business on that basis

How do people live on only 500k a year.... They dont buy a private jet and a $50million house.

Reddit does not have to spend half a billion dollars every year to satisfy their users (which is what its entire valuation was in 2014).
I'm self-taught and have been at it for about 15 years. I write this being conscious of the possibility that 15 years ago this may have been easier than now. Regardless, I went the "sideways" route back then. Started in QA and moved into more and more programming heavy roles as I went. Took a few hops: QA -> [stint in freelance web dev] -> Build engineer (a lot of scripting, but I tailored the role to include more heavy programming and tools work) -> Tools engineer.

From there the doors were pretty open. I worked across core tech, engine, backend, frontend, etc. I think it's been long enough, with enough experience, that the lack of degree isn't really a factor. Once recruiters see you have a decade of shipping code, a degree isn't really at the forefront of the mind. But that initial step took some sideways maneuvering.
Can't wait for this stuff to become so good and polished behind a UI, so that I can just point it to a folder of videos and see what comes out.
Yeah, i use rclone to mount my box account to my z:/ drive.

Really handy for my backups that are stored there, it's a bit slow though. But that's why there is a cache.
The only thing I've learned from this comment thread is sbuk REALLY stans for apple.
I actually agree with this. This is the status quo on Silicon Macs. But let's not pretend that there will be untold levels of caterwauling when Apple choose not to document any of it. Also, in my experience, the majority of people with "advanced tech knowledge" (that is as iky as the phrase "power user") are exactly those who I'd want to keep out. They'd likely be the ones doing stupid things for their friends and family to make the device "better" (read "work how they want it to).
If you think Android is "almost a monopoly" then how do you figure that Apple is responsible for breaking that monopoly? Surely it's Microsoft's responsibility. Or perhaps Blackberry's. Or is it Nokia's?

If Android really is a monopoly, perhaps the solution is to break up Google — not to force someone other than Google to turn their product into an Android clone.
> But the companies involved show no signs of changing, and you keep handing them money and your complaints are toothless.

Are they? EU will force iOS into getting sideloading, like they forced them into adapting USB-C.
And, recently discovered too, inflammation-induced neuron mergings.
Why only Trillion dollar mega corps?
Again, if you "pass laws about whom their citizens can trade with" isn't that having jurisdiction over a foreign company?
You are missing the point? The hard part isn't to create the tech, it is to build a community, get a massive user base and get user that write interesting comments. There are plenty of Reddit clones, but they have to compete with each other and Reddit.
I have a weird feeling that since they sold the domains to Squarespace, Google might sell off Workspace to them too.
> That's how it is on Reddit too no? You visit and post a comment on subreddit A, somehow mods in subreddit B will find out and pre-emptively ban you.

I've been avoiding Reddit recently, but when I used to use it – I never agreed with that kind of behaviour, and any subreddit which does it is one I don't want to be part of.

However, that said, that's community-level not instance-level, and so I'm not sure what that has to do with federation.
People might feel misguided with the submission title not mentioning that. I liked the pictures though !
Check out Luma it's an iPhone app that makes it really easy to create Nerfs and render out videos from them. Although I don't think it handles long paths like this method yet.

https://lumalabs.ai/
it's called "normal country". It turns out that there are so many laws that we are breaking the all the time.

Examples:

https://lawlinguists.com/break-law-every-day/
https://mccreadylaw.com/blog/breaking-law-every-day/
https://www.rd.com/list/weird-laws/
https://brittontime.com/2021/01/08/top-10-ways-people-breaki...
It's also usually the type that can never admit their own mistake and instead will push into failure because they think admitting to mistake and changing course makes them look weak
Oh! I probably shouldn't write comments before coffee. What happened was that I saw the sign-up page and assumed it was just for creating an account, rather than accessing the web builder. I should have realized what was going on when the same login screen appeared in the downloaded app.

I'm familiar with Webflow and the design tokens make sense to me, but I don't think it's a natural abstraction for non-web developers. I saw that you're ex-Webflow, I just meant to express a general frustration with how existing builders deal with reusable styles - it totally makes sense in the context of targeting devs who already know the Webflow UX. For what it's worth, I've been working on a site builder for the past few months and ended up with a similar solution, so this criticism is partly a projection of my own struggles.

Anyway, thanks for replying! The project looks great, I look forward to see what you end up with wrt versioning and animations.
Disagree, what incentive does Apple have to listen for feedback from people who are not even in their ecosystem?

Our household is pretty much Apple exclusively.
Well, if I was Huffman, the question I would be asking is can I bring revenue up so much from api and other things that I can now employ a lot of mods?

He might have made that call already, and it might be possible.

Facebook works with paid mods after all.
The mistake is that reddit thinks moderators use the API for convenience and not by necessity. Previous protests against reddit didn't last long, because they were against things that fundamentally didn't matter outside of ethics, while this is, especially for moderators, a significant ask for their already unpaid labor. Moderators, emboldened by user support, are on strike because this affects them personally in a big way. The interpersonal bullshit spez in particular has been pulling was just the nail in the coffin for users who weren't quite sure who to support.
...you think dev wouldn't notice if the product they are making changed direction ?