æʃliŋ, loaf of autismo @aescling@cat.family

oh ok, in app/models/status.rb:

'''
before_create :set_locality
'''

and then in there

'''
def set_locality
if account.domain.nil? && !attribute_changed?(:local_only)
self.local_only = marked_local_only?
end
end
'''

and a couple paragraphs above that:

'''
def marked_local_only?
# match both with and without U+FE0F (the emoji variation selector)
/#{local_only_emoji}\ufe0f?\z/.match?(content)
end

def local_only_emoji
'👁'
end
'''

@starfall yeah it does feel like code i would put in a service layer

@starfall feel silly for not looking in the fucking model for a status

@starfall ty

@monorail oh my god it’s in the model definition for a status. lol

@monorail that’s what i understood, but i cannot yet find where it actually does this in the codebase

@compufox no, u,,

it looks for a sigil, right? where though.

current task: where the fuck does the glitch-soc code actually determine if a post is local only

@packbat look i just, really love bread,

@packbat thankkkklkkkkkkk -nomnomnom-

@packbat just note that avacado oil is relatively expensive tho

@gayocats cat,

@Lady big example on my mind is THPS1+2, whose physical copy got has a day one update that greatly improves performance

and also is like, 10 gigs i think

@Lady yeah that’s the thing…

@xenon hell yeah

@packbat yes please

@compufox a

@gayocats cat

@chosafine i know for LCD displays you get effective input lag from ghosting of the previous frame in large parts of the screen before they all get updated; idk if more frames will reduce this ghosting or make it worse (because you leave a ghost from half a frame prior instead of a full one)