sandstrom (u/sandstrom)

sandstrom commented on Gem.coop gem.coop/... · Posted by u/mbStavola

sandstrom · 2 months 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!

sandstrom commented on EU Chat Control: Germany's position has been reverted to undecided mastodon.social/@chatcont... · Posted by u/doener

littlecranky67 · 3 months ago

Can someone please explain to me how that law will prevent anything or anybody from encrypted messaging, if I can just whip up a website and use javascript plus websockets/webrtc to implement encrypted chat? Like, yes, you can prevent the FANANG from implementing it, but criminals will just use the secure one...

sandstrom · 3 months 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).

sandstrom commented on The origin story of merge queues mergify.com/blog/the-orig... · Posted by u/jd__

sandstrom · 3 months 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

It makes it easy to look at the Git history both at the 'PR level' kind of like a change log (`git log --merges --decorate --oneline`) or dig down into each PR to see all commits.

sandstrom commented on GitHub immutable releases (public preview) github.blog/changelog/202... · Posted by u/sandstrom

sandstrom · 4 months 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.

sandstrom commented on Manticore Search: Fast, efficient, drop-in replacement for Elasticsearch github.com/manticoresoftw... · Posted by u/klaussilveira

snikolaev · 5 months ago

Hi everyone — I'm one of the maintainers of Manticore Search. Huge thanks to @klaussilveira for submitting this — we really appreciate the interest and the thoughtful discussion here.

A few points that came up in the thread and are worth clarifying:

- We do get compared to Elasticsearch a lot. While we support some of its APIs, Manticore isn't a drop-in replacement. We've focused on performance, simplicity, and keeping things open-source without vendor lock-in. Our own SQL-based query language and REST endpoints are part of that philosophy. - @mdaniel was right to question the "drop-in" wording — that's not our goal. - As @sandstrom pointed out, tools like Typesense and Meilisearch are part of this evolving search space. We see Manticore fitting in where users want powerful full-text and vector search capabilities with lower resource overhead and SQL capabilities (we support JSON too though)

We'd love to hear from you: - What are your main use cases for search or log indexing? - Which Elasticsearch features (if any) are absolutely essential for you? - Are there performance comparisons or scaling challenges you'd like to see addressed?

Happy to answer any questions or dive deeper.

sandstrom · 5 months 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

sandstrom commented on Manticore Search: Fast, efficient, drop-in replacement for Elasticsearch github.com/manticoresoftw... · Posted by u/klaussilveira

sandstrom · 5 months 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)

sandstrom commented on Web Translator API developer.mozilla.org/en-... · Posted by u/kozika

sandstrom · 6 months 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.

sandstrom commented on Web Translator API developer.mozilla.org/en-... · Posted by u/kozika

RockRobotRock · 6 months ago

https://github.com/mozilla/standards-positions/issues/1015

sandstrom · 6 months 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...