downvotetruth

Just be sure to have no regrets.

Prior:

https://news.ycombinator.com/item?id=40280760

https://news.ycombinator.com/item?id=40453822

Tried using msty today and it refused to open and demanded an upgrade from 0.9 - remotely breaking a local app that had been working is unacceptable. Good luck retaining users.

If an implementation had NVidia's Heterogeneous Memory Management implemented, then 192 GB RAM DDR5 + GPU VRAM would seem to be close.

CPU cache has never been sold as an independent upgrade. Wonder if a marketing study has ever been done on whether products with names that have been anthropomorphized sell better than those that have not such as random access memory vs storage. Maybe the appeal of being able to buy something illegal like human body parts or slave(s) [drive(s)] seems like it would have a cool factor for some consumers that has some how outweighed the disgust by others.

On the contrary, our civilization has never before had to deal with so much shit.

GPS should be expected to be an option given its prevalence, the consideration that the supplement(s) are required to be derived using an electronic device - a telephone does not work without electricity, and the urgency to implement.

Emergency services should as is be required to use GPS or similar, especially in the U.S. given the existence of the United States National Grid (https://geodesy.noaa.gov/NCAT/), as house numbers may be not be available for a variety of reasons. Previous discussions:

https://news.ycombinator.com/item?id=21196402

https://news.ycombinator.com/item?id=20970664

https://news.ycombinator.com/item?id=37359256

https://news.ycombinator.com/item?id=31829267

https://news.ycombinator.com/item?id=27015046

If the goal is to be the most progressive, it should not and rather tax land owners as much as necessary to balance the government's budget directly proportional to land value and get rid of building height restrictions.

Radar Chart - Custom Label appears to have illegible markings and the "February" label gets cut off to Februa in other radar charts.

Specifically, for the contiguous United States how many days into the future the Weather Service’s forecast of the daily high temperature is accurate within 3 degrees Fahrenheit.

The intent for the boycott is not to prevent oral transmission from drinking milk, but rather to force herds to be tested to stop the respiratory spread of bird flu within state borders. Also, ultra pasteurization has additional negative effects compared to pasteurization; see for more: https://www.ncbi.nlm.nih.gov/pmc/articles/PMC10063903/

Sir, the poll was created to be specific to dairy. ;)

Adding as a comment as the text of URLs do not embed in an anchor element in the text field of a submission: Related: https://news.ycombinator.com/item?id=40861226

Poll: Untested Bird Flu Dairy Boycott https://news.ycombinator.com/item?id=40861796

Penrose has published many papers on ghosts of black holes from another universe (see https://www.livescience.com/63392-black-holes-from-past-univ... for commentary), but 0811.2723 does not have Penrose as an author or state a reference to him by name.

HN as is does not reliably detect duplicates even with query parameters untrimmed; see the point above about ?id=123&comments=1 and ?comments=t&id=123. Further, even if there was an exact match on the query params in a certain order, the REST standard makes no guarantee on what resource(s) are returned on subsequent identical calls such as when an addition is added with ?topic=Conjecture or ?topic=Theorem as they are by design meant to indicate the uses like filtering or sorting. So, it's not possible to rely on identical uniform resource locators with query params to detect duplicate resources. It would be an incentive for those sites that want to be able to have more frequent visibility of specific resources on aggregator sites with duplicate detection to conform to the standard. Note detection != blocking. Those non-conforming are not being forced to change and it could be argued that visibility would be enhanced by preventing ambiguity of discussion on specific resources. If the title is set as required at the time of submission, then that field could be different and as discussed above any set of relevant URLs with query params could be added to the text field to specify resource(s) on a non-conforming site to bypass a duplicate check along with a [suggested not required] helpful description of what was seen at any query param URL at the time of submission. Obviously, the resources at non-query param URLs may change too depending on the whims of a site owner, but are suppose to be unigue resource IDs by REST.

It does matter how URLs should be structured as that defines and constrains the text that is accepted by the designated input element otherwise without such any plain text translatable to a resource would be acceptable thus the need for rules to determine valid URLs.

> HN exists to share articles

Not to argue one way or another for that claim, but assuming it were true then enforcing a no query param constraint would allow greater visibility for the shared content as again it would prevent the specified case(s) of allowing it to get buried by submissions duplicating the link. Also, it seems pointless to go against the REST standard of using path params to identify a specific resource or resources while using query parameters to sort/filter those resources; disallowing direct linking to a filter does not make direct links to articles impossible. It is true that HN itself relies on query parameters to link resources that goes against the stated REST standard.

https://example.com would be the submission & https://example.com/read_blog_post.php?id=1234 an added comment or preferably the text (first comment) field. Yes, this would almost surely cause the 1 URL per year HN submission rule to be violated, but the expense is being unable to at least attempt to force a unique constraint on the URL as the query params are not required to be in order like ?id=123&comments=1 and ?comments=t&id=123 both being valid leading to the combinatorial growth in URLs pointing to the same content and hindering exact URL matching and filtering. Given that, search engines are also unlikely to favor that site structure when indexing over a scheme such as https://example.com/read_blog_post/id/1234 There is still the possibility if a host wanted to get around such a restriction the server could create virtual directories to allow the same reordering as the query params, but that could be detected and the site flagged if necessary.

Dang or mod please remove the "?xf26hn" text from the end of the URL so it is able to used to find the past posts by scripts:

145 points 1 year ago 105 comments https://news.ycombinator.com/item?id=34482226

19 points 4 hours ago 5 comments https://news.ycombinator.com/item?id=40798224

Further suggest that HTML query params be disallowed in submissions; if URLs with params are relevant they can be added as comment(s).

(2018)

Death is inevitable too, but not wise to welcome it.

Phone # requirement is a bigger blocker.

Seems fair.

If only he could speak. At least he's still taking nourishment.

Lost as to why there is a tests folder yet the test function marked with the #[test] attribute is being added to /src: https://github.com/rustcoreutils/posixutils-rs/pull/132/comm... edit: Since the change was to the grammar saved in a separate .pest file, which is separated from the procedural code, then would that make the test an integration rather than a unit test as the "parse_program" function is public?

Be fun to see a 70" flatscreen strapped to a cargo bike. The process of having to rent an additional propulsion cart is not in my experience a trivial matter.

What about the disabled / wheel chair bound? Is there an exception for them too? That is a great way to game the system. Hire "disabled" delivery drivers.

Even the very wise cannot know all ends.