The worse is that it brings visitors from outside, into an otherwise gated community. But they come (with their kids), admire, and leave. 😂
Christmas decoration
"1000" where a number, 1000, was expected.
> Might break stuff in jenny/mutt, but I haven’t tested it.
Yup,
RE_NICK_INVALID.
jenny -e for the first time:
quark@arrakis:~$ jenny -e
Traceback (most recent call last):
File "/home/quark/.local/bin/jenny", line 710, in <module>
edit_twt_file(app)
File "/home/quark/.local/bin/jenny", line 149, in edit_twt_file
refresh_and_publish(app)
File "/home/quark/.local/bin/jenny", line 324, in refresh_and_publish
rotate(app)
File "/home/quark/.local/bin/jenny", line 545, in rotate
if len(twt_lines) <= max_num:
TypeError: '<=' not supported between instances of 'int' and 'str'
quark@arrakis:~$
error executing template timeline: template: timeline:162:48: executing "base" at <.RegisterDisabledMessage>: can't evaluate field RegisterDisabledMessage in type *internal.Context
The shot @darch posted is also ultra pale. Demarcation from background and cards is bad, specially when looking at it on mobile.
There are too many tiny fonts, the placement of the hash too close to other elements, and in a place that doesn't make much sense. The "hamburger" items are too close to the logo. The next link is not properly aligned. The double line on the context reply adds too much noise. The options for twts (only Yarn in this screenshot), are the same colour of the default text (no distinction).
Those observations are derived from the screenshot alone, and nothing else.
Autumn is here
> Technically though this limitation doesn’t need to exist, but I’m not sure we should really change it either?
It would make Yarn a bit more unique. I, for one, would love to use my real name, Jürgen. 😁
* Still not possible to twt to someone from their profile page---I believe it was possible before.
* The anonymous footer login line is still too close to footer line (it was closer to the bottom card before).
* Twt options (reply, yarn, etc.) icons and labels are still too big in both, desktop and mobile. At the very least we should dim the link colour for those a little. The important thing on a twt is the twt itself, and the poster. Those options should be there, but not stand out too much.
* The "Recent twts from ..." header on external and local profiles is too big.
A couple of $0.02, for now. 😊
local_twtxt_file is deprecated now, and we must use local_twtxt_dir instead, correct?
> So I just chose movq, because it was floating around in my head anyway (and I already had the domain)
When I go to https://movq.de/, I get:
> Nothing to see, move along
You should have written:
> Nothing to see, movq along
😂
Also keep in mind this: if help from the community is required for continuity of the non-profit, you might want to re-think that approach. We are extremely small, and niche.
I work for a Florida State university, and our reviews mean nothing. Amongst the things: you have to be Jesus, and walk on water, to get outstanding (the highest). So, nobody ever gets it; it is there for no reason. They also mean absolutely nothing but a formality---or, if really bad, a justification to sack you---and never, ever, translate to pay increases of any kind.
To paint a better picture for you. Our inflation fluctuates from 4.5% to around 6.5%, or so. This year, everyone making over $55,000/year got a 2.5% increase (before taxes), and everyone making less got a 3.5% (before taxes).
Thank you for sharing. I read the transcript; you covered a lot. Well done!
Just now I hit fork on your reply and this was the first screen I got:
Screenshot That is wrong. It has to be hash first. I refreshed the page, tapped on fork again, then got the right order the second time.
Something isn’t right, @prologic.
Under what conditions would something like that happen? I understand tapping/clicking on fork calls up a bit of JS, what could it cause it to misbehave that way? I have seeing this issue only twice.