urbit/shrub
1
1
Fork 0
mirror of https://github.com/urbit/shrub.git synced 2025-01-07 05:26:56 +03:00
Code Issues Packages Projects Releases Wiki Activity

Fixed weird code for updating /circles subscriptions.

Browse Source 
No longer incorrectly uses the subscriber's ship name when getting the affected story.
This commit is contained in:
Fang 2018-01-17 00:20:34 +01:00 committed by GitHub
parent 0ba27a4e32
commit d2cc5a5658
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 17 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

26
app/hall.hoon
View File

@ -2323,17 +2323,25 @@
::REVIEW this could be considered leaky, since it ::REVIEW this could be considered leaky, since it
:: doesn't check if {who} ever knew of {nom}, :: doesn't check if {who} ever knew of {nom},
:: but does that matter? can't really check.. :: but does that matter? can't really check..
:: if the story got deleted, remove it from the circles listing.
?: ?=($remove -.det.det) `| ?: ?=($remove -.det.det) `|
=+ soy=(~(got by stories) who.qer) =+ soy=(~(got by stories) nom.det)
?. ?| ?=($new -.det.det) :: if the story got created, or something about the read permissions set
?& ?=($config -.det.det) :: for the subscriber changed, update the circles listing.
?=($permit -.dif.det.det) =; dif/?
?=(?($channel $village) sec.con.shape.soy) ?. dif ~
(~(has in sis.dif.det.det) who.qer) =+ (~(so-visible so:ta nom.det ~ soy) who.qer)
== :: if the story just got created, don't send a remove rumor, because it
:: never showed up in the first place.
?:(?=($new -.det.det) ?:(- `- ~) `-)
?| ?=($new -.det.det)
::
?& ?=($config -.det.det)
?=($permit -.dif.det.det)
?=(?($channel $village) sec.con.shape.soy)
(~(has in sis.dif.det.det) who.qer)
== ==
~ ==
`(~(so-visible so:ta nom.det ~ soy) who.qer)
:: ::
$public $public
?. ?=($public -.det) ~ ?. ?=($public -.det) ~