Finagle
the-algorithm
| Finagle | the-algorithm | |
|---|---|---|
| 24 | 266 | |
| 8,749 | 10 | |
| 0.1% | - | |
| 7.2 | 10.0 | |
| 17 days ago | about 2 years ago | |
| Scala | ||
| Apache License 2.0 | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Finagle
-
Features of Project Loom incorporated in Java 21
Not sure about now but a few years back the company I worked for was heavily vested in Finagle [1] using Future pools. I'm sure virtual threads would only enhance this framework. Also, Spring and it's reactive webflux would probably benefit as well [2].
[1] https://twitter.github.io/finagle/
[2] https://docs.spring.io/spring-framework/reference/web/webflu...
- Twitter Finagle: Backoff.scala
-
Twitter (re)Releases Recommendation Algorithm on GitHub
Don't really see how "enterprise scala" has anything to do with this, scala is meant to be parallelized , that's like it's whole thing with akka / actors / twitter's finagle (https://twitter.github.io/finagle/)
-
We switched from Scala 2 to Rust
So biased. Twitter dropping Scala3 is simply untrue, ticket is there and still is open https://github.com/twitter/finagle/issues/932
-
Introduction to Bazel for Scala developers
Thank you. I only took a quick look, but this looks like a goldmine of info if you are interested in using bazel to build a scala monorepo: https://github.com/twitter/finagle
-
Server Stack Options for Scala
Finagle
-
Elon: "[Twitter's] recommendation algorithm was using absolute block count, rather than percentile block count, causing accounts with many followers to be dumped, even if blocks were only 0.1% of followers."
And the engineering team are far from imbeciles because they built one of the worlds' best cache and RPC microservice components. As well as the fact that up until Musk took over the website was running just fine (other than your issue with product decisions).
-
Pretty incredible thread where Elon confuses how GraphQL works, thinks the Android client itself is making one thousand requests, and then publicly fires an employee who corrects him.
Bro it's their fucking project lolhttps://twitter.github.io/finagle/
-
Elon Musk publicly feuding with and firing his developers on Twitter
RPC generally means server side calls, probably this https://twitter.github.io/finagle/, and XHR is not RPC.
-
Pretending to know what you're talking about
not familiar with twitter internals but it would be atypical to use gql for internal communications even if you expose it as a public api. twitter also develops a widely-used RPC system https://github.com/twitter/finagle
the-algorithm
-
"xAI will open source Grok"
> Wasn’t the tweet recommendation system “open sourced” as well? Does this guy know the difference between open source and “open source”?
What do you mean? There exists only one binding definition of open source
> https://opensource.org/osd
and either some product does satisfy it, or it doesn't. As far as I am aware
> https://github.com/twitter/the-algorithm
does satisfy the open source definition, so your sarcasm looks demagogical to me, but I am very willing to learn something new.
- Recommendation algorithm manipulation via mass blocks
-
Leaving Twitter
I'm not a Twitter user so if this is a dumb question I apologize.
This sounds like a pretty serious allegation. How do you know this is true? Is it in the source code?[1]
[1]: https://github.com/twitter/the-algorithm
- The new X button doesn't close the website
-
Twitter has officially changed its logo to ‘X’
There is already a bug report for this: https://github.com/twitter/the-algorithm/issues/1876
-
The look of a man who has royally screwed up
There is a way for Meta to fuck this up. The Algorithm is licensed under GPL, which is a copyleft license. That means any derivative works based on it must also be licensed and open sourced under GPL. If Meta doesn't do that, they may be on the hook.
- The irony
-
Twitter sends Meta cease-and-desist letter over new Threads app: Sources
And I believe the source for that was effectively opened up to the world: https://github.com/twitter/the-algorithm
- Twitter is threatening to sue Meta over threads. Here’s the letter Twitter sent Meta
What are some alternatives?
gRPC - The Java gRPC implementation. HTTP/2 based RPC
hn-search - Hacker News Search
Netty - Netty project - an event-driven asynchronous network application framework
the-algorithm-ml - Source code for Twitter's Recommendation Algorithm
OkHttp - Square’s meticulous HTTP client for the JVM, Android, and GraalVM.
Mastodon - Your self-hosted, globally interconnected microblogging community
Akka - Build highly concurrent, distributed, and resilient message-driven applications on the JVM
apple-notes-liberator - Free your Apple Notes data from Notes.app
Finatra - Fast, testable, Scala services built on TwitterServer and Finagle
Async Ruby - An awesome asynchronous event-driven reactor for Ruby.
Lagom - Reactive Microservices for the JVM
marvin - ✨ Build AI interfaces that spark joy