Skip to main content



Hey all, just another newbie post about Friendica here as I'm trying to learn the ropes.

I notice that some times when I follow someone - be it an account on Mastodon, Sharkey, etc - their Network Posts are blank until they post something.

So I went searching for a setting or some kind of toggle to perhaps change that to enable me to see a user's existing posts prior to the point when I followed them.

I could only find the following link below which mentioned the process.

Is there a toggle somewhere that would let people see older posts from users on Fediverse?

github.com/friendica/friendica…

Currently it works like this: to see a post or comment your server has to receive it first. This happens if any of these are true:

1you or someone else on your server is subscribed to the author of this item
2 the item is reshared by someone you or someone else on your server is subscribed to
3 you interacted with child item (e.g. reply to the post) which causes parent items to get fetched

If you just stumbled upon someone's post and there are some comments from people who never made it to your server you won't see them - and I think this is the case for any Fedi platform, not just Friendica. This is also the reason you sometimes don't see full "like" counts for others' posts.




Forth: Immediacy and postponement


When reading a #Forth tutorial, a lot of time is usually spent explaining RPN and the data and return stack, which are extremely easy to understand for most people having been exposed to some sort of STEM subjects. Then, examples pop up with words like “IMMEDIATE” and “POSTPONE” which it seems the author thinks the reader finds just as easy, while using jargon not used outside Forth programming. This is my attempt at writing the explanation I wish I had found a long time ago, written so I can better my own understanding.


1.0 Compilation

Forth words are very much like sub-routines, but just as the Forth machine has two modes, interpretation and compilation, Forth words may be thought of as having interpretation semantics and compilation semantics. The literal “5” will during interpretation have the value 5 pushed on to the data stack, but during compilation, it will simply have code which will push 5 appended to whatever word is currently being compiled. This is the case of most words, with one major exception being control flow words.


1.1 Control flow

Control flow words execute during compilation, pushing and popping references to and from the control flow stack (which may or may not be implemented using the data stack). A word like “IF” has no standards defined interpretation semantics at all. “IF” will as well as appending the “IF” test to the current word, push to the control flow stack a forward reference for where it's going to jump. That forward reference can then be resolved by an “ELSE” or “THEN” later in the source code. Words which execute during compilation, are called immediate.


2.0 IMMEDIATE

Set the compilation semantics of the last defined word to be its interpretation semantics.

GForth has a very good explanation:

complang.tuwien.ac.at/forth/gf…


3.0 POSTPONE

Compile a word's compilation semantics instead of its interpretation semantics.

Again, GForth has a very good explanation:

complang.tuwien.ac.at/forth/gf…


4.0 Putting it together

“POSTPONE” compiles whatever the next word would have done during compilation into the current word. “IMMEDIATE” makes the last defined word behave during compilation as it does during interpretation.


4.1 An example

Let us assume there exists an ALGOL fandom and define:

: FI POSTPONE THEN ; IMMEDIATE

In other words, when running “FI”, run the compilation semantics of “THEN”, and by the way, let “FI” be a word where the interpretation semantics becomes the compilation semantics. So, “FI” is now a word which during compilation behaves exactly as “THEN”. Using “SEE” on a word containing “FI” will only show the “THEN” which has been compiled into that word.

Earlier edited 20210910T190453Z, 20210911T123750Z.




"Notifier task is pending": what this means?


Friendica's web frontend shows an hourglass icon with the pop-up title "Notifier task is pending". When I initially posted, it was kind of expected since I had just posted. However, days have passed and all my posts, including the oldest one, are still displaying the icon. Why?
in reply to Daemon Silverstein

Because we have an issue lagging behind in job processing. It's catching up but at current speed would still take 11 days. Working with Friendica devs to get it sped up.