Rails 운영 데이터 복구: 6,000건의 백필 작업에서 배운 교훈

운영 환경에서 update_all을 사용한 단순 데이터 수정은 진행 상황 파악이 불가능하고 데이터베이스 부하를 유발하는 등 위험 요소가 많다.

🔗 원문 보기

Mastodon could soon be getting the ability to backfill posts for profiles that an instance hasn't seen before. This will fix a major issue that has made the experience of using Mastodon confusing for new users especially on smaller instances and continues to be a major pain point for experienced users.

Hopefully this won't get delayed any longer than is needed because it's a huge limitation that doesn't need to exist.

Follow this issue: https://github.com/mastodon/mastodon/pull/34597

#mastodev #mastodon #backfill

Backfilling Conversations: Two Major Approaches

https://community.nodebb.org/topic/18844/backfilling-conversations-two-major-approaches

#ActivityPub #Backfill

Progress update for Conversational Contexts

This past June, I put together a write-up about two major approaches to backfilling conversations. The ability to properly backfill conversations means we will be able to make major inroads toward solving the feeling that the fediverse is quiet.

https://community.nodebb.org/post/105743

A conversational context is what the ForumWG uses to describe what you might see as a reply tree or comment thread. One of the short-to-medium term goals of the ForumWG is to get conversational backfill working reliably.

What this means — conversational backfill means that when you encounter a post/status/note/etc. (e.g. you're mentioned or boosted/shared something), there is a reliable and comprehensive way to retrieve the entire conversation around it, so you are not interacting with the object on its own, but in its proper context with all its sibling replies.

We plan to achieve this with a combination of a top-down (FEP-driven) and bottom-up (implementor-first) approach. While this sounds incongruent, top-down approaches tend to overcomplicate and bottom-up approaches tend to violate the protocol (unintentionally of course .)

There are a number of independent top-down efforts to achieve this:

• FEP-7888: Demystifying the context property
• FEP-171b: Conversation Containers
• FEP-76ea: Conversation Threads

These FEPs are in the R&D phase.

State of the Top-Down approach

At this time, the ForumWG is only recommending the following:

• Publishers SHOULD use context for grouping related objects in a thread (but this is not the only way to use context).

There is general agreement over:

• A context SHOULD resolve to a resource.

There are concerns over:

• What that resource is (as:OrderedCollection, a new type, something else?)
• What is included in that context (plain objects or activities)

State of the Bottom-Up approach

The bottom-up approach is results-oriented, and while certain implementors may follow certain FEPs, the overarching goal is "cross-compatible conversational backfill".

Separately, these implementors are (or have signalled interest in) implementing conversational backfill:

• FEP 7888
  • NodeBB (@julian) and Discourse (@[email protected])
    • Attaches context to objects
    • context resolves to an OrderedCollection containing objects
    • Two-way conversation backfill is tested and working (7888 only).
  • WordPress (@[email protected]) and Frequency (@[email protected])
    • Attaches context to objects
    • context resolves to an OrderedCollection containing objects
    • Outgoing conversational backfill is tested and working — others can backfill an entire conversation from these implementors.
  • Lemmy (@[email protected]) and PieFed (@[email protected])
    • Have signalled interest (neither positive nor negative) in conversational backfill and are waiting and watching at this time.
• FEP 171b
  • Mitra (@[email protected])
    • Attaches context to activities
    • context resolves to an OrderedCollection containing activities
    • Incoming conversational backfill is tested and working — Mitra can backfill an entire conversation from FEP 7888 and 171b implementors ( nice!)
  • Hubzilla (@[email protected]) and Streams (@[email protected])
    • Attaches context to activities
    • context resolves to an OrderedCollection containing activities
    • Outgoing conversational backfill is tested and working (against Mitra)

What's Next

This thread will likely contain updates and discussion from related parties about their implementations and what they wish to do next. In the cruelest irony of ironies, because conversational backfill is not ubiquitous yet, you will need to "View Original URL" in order to see all of the replies.

The ForumWG will meet again on 6 March 13h00 EST where all of this will be discussed, as well as planning out the future focus items for the ForumWG.

If you are an implementor, there is no reason you cannot join the fray. Boost this post, reply to it, join the conversation(al context)!!

If you're not an implementor, boost me anyway 

Just wrapped up a call with @[email protected] and @[email protected] to review their implementations of FEP 7888, specifically in relation to conversational backfill.

 individual objects serve a context property
 that context property is a URL that resolves

One of the concerns raised was related to the OrderedCollection of items served by the context. Specifically, if the items presented in the collection were not in chronological order, NodeBB failed at importing some of the items as the inReplyTo referenced an object that did not exist.

The solution to this was to ensure that the collection items were in chronological order from oldest to newest. Once fixed:

 the context resolved to an OrderedCollection containing objects
 NodeBB was able to pull in the entire conversation

NodeBB used to guard against this by ordering all received items by chronological order, but I realized that while this worked 99%+ of the time, there are some fun (ahem...) individuals who send objects with timestamps way in the future.

Personally I think removing the sorting just to fix one edge case was premature. At the same time, I think specifying that the OrderedCollection be sorted in chronological order should be a requirement.

cc @[email protected]

#Fediverse #Frage: Ist es immer noch so, dass ein Account einer Instanz A, der einem 🔒-Account auf einer Instanz B frisch folgt (und dem von Instanz A auch niemand anders folgt), nur Posts sehen kann, die nach dem Folgen gepostet wurden?

Oder kann man sich auf den #Backfill inzwischen verlassen?

Word Search Puzzle 514

Word List : #saut #whangees #chroma #unto #tarsals #jolter #patellar #cotset #shraddha #continua #subsume #daytide #salving #oarlock #costumic #backfill #fainer #outvie

http://karafinance.com/2024/02/27/word-search-puzzle-514/