sandstrom
Joined 17 years ago
Karma
2,544
Submissions
735
Member since
Mar 23
::1
View on Hacker NewsRecent submissions
Comment · 4 months ago
I totally agree.
If one needs to put metadata in commits, usually better to just put it in a Git trailer.
https://git-scm.com/docs/git-interpret-trailers
`Co-authored-by: Alice` is a common one, but you can have anything in there.
Comment · 1 year ago
I understand forking is sometimes needed, but it's also somewhat discouraging to see that the differences couldn't be reconciled.
As long as people are aligned on advancing the Ruby ecosystem, I think it should be possible to cooperate even if there are disagreement in other areas [which political party you support, differences in personal opinions, etc].
Maybe it'll be resolved eventually, just like Merb <> Rails, Bundler <> RubyGems and RubyTogether <> RubyCentral were eventually merged. That's what I'm hoping for!
Comment · 1 year ago
This is the part that I think most politicians simply don't understand.
I've been trying to argue this point with my government several times (some MPs even replied friendly, so they'd actually read it, but still don't understand or believe it).
Comment · 1 year ago
Does anyone working at Github know why 'semi-linear' merge isn't supported as a merge strategy in the merge queue (and regular PRs)?
I Gitlab and Azure DevOps (also owned by MS) supports it, and even talked to an employee now working at Github, that implemented this in Azure DevOps.
More background: https://github.com/orgs/community/discussions/14863
With a semi-linear merge strategy, you rebase (without --fast-forward) before merging, so the history ends up looking like this:
* c8be0c632 Merge pull request #1538 from my-org/api-error-logging
|\
| * 80ecc4985 Fix security warning, bump nokogiri
| * 750613638 Log and respond with more detailed validation errors in the API
| * 0165d6812 Log code and details when rendering an API error response.
| * 1d4daab48 Refactor email validation result to include a descriptive message
| * 635214092 Move media_type logging into context_logging
|/
* 1cccd4412 Merge pull request #1539 from my-org/profile-clarify
|\
| * 87b342a32 Rename profile default to migration target
| * 2515c1e59 Fix disallow removing last profile in company
|/
* b8f3f1658 Merge pull request #1540 from my-org/customer
|\
| * 064b31232 Add customer-specific taxed allowance reduction
|/
* 3cf449f94 Merge pull request #1528 from my-org/console-logging
|\
| * 99657f212 Don't log to rails console in production
|/
* 8c72e7f19 Merge pull request #1527 from my-org/gemfile
Comment · 1 year ago
Does anyone know if immutable also means I cannot delete a release? (even after say 3 years)
Because I'm guessing allowing deletes would also make re-publishing possible, which would probably defeat the purpose. However, having them stick forever can also be annoying.
Comment · 1 year ago
"What are your main use cases for search or log indexing?"
To me, storing and searching logs is quite different from most other search use-cases, and it's not obvious that they should be handled by the same piece of software.
For example, tokenization, stemming, language support many other things and are basically useless in log search. Also, log search is often storing a lot of data, and rarely retrieving it (different usage pattern from many search use-cases which tend to be less write-heavy and more about reads).
I know ElasticSearch has had success in both, but if I were Manticore/Typesense/Meilisearch I'd probably just skip logs altogether.
Loki, QuickWit and other such tools are likely better suited for logs.
- https://github.com/quickwit-oss/quickwit - https://github.com/grafana/loki
Comment · 1 year ago
For anyone who's interested, two other popular contenders for replacing Elasticsearch are Typesense (https://typesense.org/) and Meilisearch (https://www.meilisearch.com/).
(both are also trying to replace Algolia, because both have cloud offerings)
Comment · 1 year ago
This would be very useful.
Basically, the 'translate this' button you see on Twitter or Instagram next to comments in foreign languages. This API would make it trivial for all developers to add that to their web apps.
Comment · 1 year ago
I honestly don't understand the arguments Mozilla have against it.
Safari/webkit is positive (though no official stance yet):
https://github.com/WebKit/standards-positions/issues/339#iss...
Comment · 1 year ago
This is not auto-translation.
Rather, it's an API developers can use to add inline translation to web apps.
For example, under a comment in your app, you can (a) detect the language, and (b) if it's different from the current users/browsers language, offer to translate it with a small link (c) if the user clicks the link, the content is translated to their language.
Comment · 1 year ago
On this topic, I have to recommend Hush! It is an excellent free, open-source and well-maintained app for iOS.
Comment · 1 year ago
> When Amazon allows any of the millions of ephemeral clone-storefronts to sell shady or illegal stuff, would you rather have the authorities spend years chasing ghosts or have Amazon change their rules to make sure such illegality and abuse aren't possible in their marketplace?
I'm fine with a law saying Amazon is liable for fake storefronts etc. Sounds reasonable. I'd also favor requiring e.g. Uber or Airbnb to provide authorities with data to prevent tax fraud from operators in such marketplaces.
But to me saying Google's advertising product should enforce how the individual websites work [fingerprinting], is to me more in the direction of "an electricity provider should enforce how people live their lives in any home provided by such electricity…"
Comment · 1 year ago
I guess it depends on what you read into it.
But when I read this it seems like they are unhappy with Google no longer enforcing their view of fingerprinting:
We think this change is irresponsible. [...] We are continuing to
engage with Google on this U-turn in its position and the departure it
represents from our expectation of a privacy-friendly internet.