Papers › Efficient-FedRec: Efficient Federated Learning Framework for Privacy-Preserving News...

Efficient-FedRec: Efficient Federated Learning Framework for Privacy-Preserving News Recommendation

12 Sep 2021EMNLP 2021 11arXiv:2109.05446archive 2025-07-28

Jingwei Yi, Fangzhao Wu, Chuhan Wu, Ruixuan Liu, Guangzhong Sun, Xing Xie

News recommendation is critical for personalized news access. Most existing news recommendation methods rely on centralized storage of users' historical news click behavior data, which may lead to privacy concerns and hazards. Federated Learning is a privacy-preserving framework for multiple clients to collaboratively train models without sharing their private data. However, the computation and communication cost of directly learning many existing news recommendation models in a federated way are unacceptable for user clients. In this paper, we propose an efficient federated learning framework for privacy-preserving news recommendation. Instead of training and communicating the whole model, we decompose the news recommendation model into a large news model maintained in the server and a light-weight user model shared on both server and clients, where news representations and user model are communicated between server and clients. More specifically, the clients request the user model and news representations from the server, and send their locally computed gradients to the server for aggregation. The server updates its global user model with the aggregated gradients, and further updates its news model to infer updated news representations. Since the local gradients may contain private information, we propose a secure aggregation method to aggregate gradients in a privacy-preserving way. Experiments on two real-world datasets show that our method can reduce the computation and communication cost on clients while keep promising model performance.

PaperPDFConference PDFCodeCode Syntology ranMethod as code

In Syntology View this paper on Syntology, its page in Syntology's graph. That page adds which of its functions are also present in other papers' code Syntology holds, with dates, and its dated run record as JSON and a README badge. It also lists the repositories linked to the paper, the abstract and the calls for agents.

Open this paper in Syntology's Atlas, the map of the papers in Syntology's graph and their citations.

For agents, on Syntology's MCP service (how to connect):

Code

Syntology 11 code samples harvested from 1 repository linked to this paper: 10 ran (of which 2 constructed an object rather than computing a result; 9 with no instrument failure: 0 honoured, 0 violated, 9 with no contract checked; 1 where Syntology's instrument failed) · 1 unverified. Where Syntology's instrument failed: 1 where our contract draft was wrong; failures of Syntology's instrument, not of the code.

By repository: official repository: 11 samples from 1 repository, 10 ran (9 with no instrument failure; 1 where Syntology's instrument failed). The run record, sample by sample. “Ran” means executed on a synthesized input, not that the code is correct or reproduces the paper.

Levels written between 2026-09-22 and 2026-09-25 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

yjw1029/efficient-fedrec officialmentioned in paperpytorchMITSyntology: 11 samples, 10 ran (1 instrument-failed) · 1 unverified report

Repository list and official/mentioned flags are the archive's, frozen 2025-07-28. Reachability, where shown, is from one Syntology probe window (2026-09-16 to 2026-09-18); repositories not probed show nothing. GitHub stars are not tracked.

Code Syntology ran Syntology

11 samples harvested: 10 ran (of which 2 constructed an object rather than computing a result; 9 with no instrument failure: 0 honoured, 0 violated, 9 with no contract checked; 1 where Syntology's instrument failed) · 1 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Syntology's record for this page has not changed since , the first build that kept a record date for it; when this build read Syntology's graph is in the build record. That date is not when the samples ran.

1ran · our draft was wrong
9ran
1unverified

Licence: 2 of the 11 samples are pointer only, meaning Syntology does not serve that copy's text. For 2 of them, this paper's copy is under a permissive licence and cleared, but the stored copy of the same code that Syntology serves is not; the licence label's tooltip gives Syntology's recorded reason. This page shows no code text for any sample; each one links to its file in the repository.

Harvested from yjw1029/efficient-fedrec. “Ran” means the sample executed on a synthesized input. It does not mean the output is correct, and nothing here reproduces the paper's results. A line beginning “fixture:” under a sample that ran gives the arguments Syntology's fixture called the sample with, each as name:type/rank/element kind (? where none was recorded), and the type of what the fixture's run returned, exactly as the harness recorded them; the arguments and the returned type were recorded by two separate runs of the same fixture. No output value is shown, and a returned type says nothing about whether the output was right. “Level recorded” gives the UTC date when Syntology's graph wrote the sample's verification level, not when the code executed; where the level was written before Syntology's graph kept that date, the row says “level recorded, date not recorded”. “Honoured” and “violated” refer to a contract Syntology drafted from the code itself. “Our draft was wrong” and “the contract check could not run” are failures of Syntology's instrument, not of the code: the sample ran on Syntology's synthesized input, and then the drafted contract did not describe it, or the check itself raised an error (RAISES), lacked a dependency (DEP_MISSING) or ran out of time (TIMEOUT); hover the label for which. A metamorphic tier, where shown, is evidence of the output's shape, not that the sample implements the method.

Each sample ends with its code_sha256. A sample's code_sha256 is Syntology's identity for that exact code. It is printed in full (16 hexadecimal characters for every sample in this build), and get_code(code_sha256="…") takes it exactly as printed. An agent calls it on Syntology's MCP service (how to connect); click an identity to copy that call.

Repository labels, per sample. official repository: The archive marks this repository official for the paper. named in the paper: The archive records that the paper mentions this repository; it is not marked official. community (archive-listed): In the archive's code links for this paper, not marked official and not recorded as mentioned in the paper. found in paper text by Syntology: Syntology found this repository in the paper's own text; whether it is the authors' implementation is not asserted. community: Not in the archive's code links for this paper; a community repository Syntology harvested. Samples are grouped by repository: a repository marked official first, then by how directly the repository is tied to the paper, then in the archive's order; never by how many ran. Licence labels name the repository's licence as recorded at harvest. “Pointer only” means Syntology does not serve that copy's text, for one of six reasons: no licence file was found; the licence was not identified; the licence is recorded as permissive but that copy's record is not marked cleared; the licence is outside the permissive list Syntology serves text under (MIT, Apache-2.0, BSD and similar); this paper's copy was not located, so its licence is not recorded; or this paper's copy is cleared, but the stored copy of the same code that Syntology serves is not. Some licences outside that list permit redistribution, such as WTFPL, and GPL-3.0 under its conditions; they are simply not on the list. Hover a licence label for the reason. File links open the file on GitHub at the default branch, which may have changed since the harvest.

A function or class name links to its page when the name occurs in the harvested code of at least 5 papers; the name is a string, not an identity. A census tag appears when Syntology's census ran implementations with that name on one shared input per bucket: it gives how many were compared, from how many papers, and how many distinct outputs they produced, and names this sample's bucket when this sample was one of them.

yjw1029/efficient-fedrec official repository 11 samples, 10 ran (1 instrument-failed) · 1 unverified
AdditiveAttention in 5 papers src/model.py ran fingerprinted MIT (permissive) · 310a5ec45864d3e6 · report fixture: signature x:Tensor/3/float, attn_mask:Tensor/2/float · returned Tensor · level recorded 2026-09-24
Model in 227 papers src/model.py ran fingerprinted MIT (permissive) · 604e71e4f92b0a6e · report fixture: signature candidate_vecs:Tensor/3/float, clicked_news_vecs:Tensor/3/float, targets:Tensor/1/int, compute_loss:bool/0/bool · returned tuple · level recorded 2026-09-24
MultiHeadAttention in 124 papers
census: 9 implementations from 7 papers, 9 distinct outputs across 3 buckets, one shared input per bucket
src/model.py ran MIT (permissive) · dcee9ec72e705723 · report fixture: returned MultiHeadAttention · level recorded 2026-09-22
ScaledDotProductAttention in 46 papers src/model.py ran fingerprinted MIT (permissive) · 3ebcb23875c37434 · report fixture: signature Q:Tensor/3/float, K:Tensor/3/float, V:Tensor/3/float, attn_mask:NoneType/0/? · returned tuple · level recorded 2026-09-24
UserEncoder src/model.py ran MIT (permissive) · 22afc11538def1e4 · report fixture: returned UserEncoder · level recorded 2026-09-22
dcg_score in 9 papers src/metrics.py ran · our draft was wrong fingerprinted MIT (permissive) · 43e79e8e0904d5d8 · report fixture: signature y_true:ndarray/1/int, y_score:ndarray/1/float, k:int/0/int · returned float64 · level recorded 2026-09-22
mrr_score src/metrics.py ran fingerprinted MIT (permissive) here; the stored copy is pointer only · 47a7b89c55c76c60 · report fixture: signature y_true:ndarray/1/int, y_score:ndarray/1/float · returned float64 · level recorded 2026-09-24
ndcg_score in 5 papers src/metrics.py ran MIT (permissive) here; the stored copy is pointer only · aaa4cece9f41ea15 · report fixture: signature y_true:ndarray/1/int, y_score:ndarray/1/float, k:int/0/int · returned float64 · level recorded 2026-09-24
newsample src/data.py ran fingerprinted MIT (permissive) · e0f74a777d9e24fa · report fixture: signature nnn:list/1/str, ratio:int/0/int · returned list · level recorded 2026-09-25
process_news preprocess/adressa_raw.py ran MIT (permissive) · 558d0c9a902a60a9 · report fixture: signature adressa_path:PosixPath/0/? · returned tuple · level recorded 2026-09-25
process_users preprocess/adressa_raw.py unverified MIT (permissive) · e5d695c2647144a5 · report

Method as code Syntology

What Syntology's graph records as this paper's claimed method, lifted into code: each assembly names its bricks (functions and classes), each with its own role and its own verification level. An assembly is not a check that the code implements the method correctly or reproduces the paper's results. Levels are each brick's own verification level in Syntology's graph (level 0: no recorded run), listed brick by brick and never combined into one level; “ran” means the brick executed on a synthesized input, not that its output is correct, and the instrument figure counts failures of Syntology's instrument, not of the code. Where a model read the code against the paper's claim, each assembly's label verdict is one model's judgement, kept in this page's JSON twin; it is not calibrated, so no card prints it.

1 assembly on this paper: 1 harvested, 0 generated.

harvested Assembly for Efficient-FedRec (graph method: Efficient-FedRec). 5 bricks; individually on a fixture: 5 ran (of which 2 constructed an object rather than computing a result; 5 with no instrument failure: 0 honoured, 0 violated, 5 with no contract checked; 0 where Syntology's instrument failed) · 0 unverified. The assembly has not been run end-to-end.

  1. Model entry · level 1 · ran · 604e71e4f92b0a6e
  2. UserEncoder model · level 1 · ran · 22afc11538def1e4
  3. AdditiveAttention model · level 1 · ran · 310a5ec45864d3e6
  4. MultiHeadAttention model · level 1 · ran · dcee9ec72e705723
  5. ScaledDotProductAttention model · level 1 · ran · 3ebcb23875c37434

Each brick ends with its code_sha256, Syntology's identity for that exact code; click one to copy the get_code call that returns it. For agents, on Syntology's MCP service: assembly(arxiv_id="2109.05446") returns these assemblies with each brick's role and wiring (how to connect).

Tasks

Federated LearningNews RecommendationPrivacy Preserving

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

Report a problem or propose a change · a person checks every report against the paper or source before anything changes; decisions are listed on /corrections