User avatar at the top of user's page is now using the standard image processing pipeline, and so is retina-compatible. Please report if anything breaks for you,
#mokum-releases: a) https://mokum.place/customize was changed to show the classic settings page; the complete catalog of all available settings is at https://mokum.place/customize/index (h/t @markizko); b) email page is now at https://mokum.place/customize/email;
Also, when you open a certain image in lightbox, you will see that it has its own URL (e.g.: /squadette/2461320/i/580971). If you send one of those URls in some messenger or share it in a social service, it will automatically use for the preview the image that is curently open.
The old settings page was replaced with the new https://mokum.place/customize page. TL;DR: most common settings are available at the first link on this page, in bold: https://mokum.place/customize/classic.
This concludes the first phase of the big settings rewrite. This page was created literally on the third day of Mokum development, it served us well but it was clear that it inhibits further progress in its current form.· псы в рапиде
It would now be possible to think about the index page independently. Some things that come to mind are a) rough categorizing of each entry on index page; b) show briefly the current state of each setting, to allow for quick eye scan; c) "favorite settings" that will allow you quick access to features that you use most; d) in some case it would be possible to use a certain setting directly on some page.· псы в рапиде
#mokum-releases: Some updates for my "reimplementing settings page" mega-project: a) there is now a classic-style settings page reassembled from new-style blocks: https://mokum.place/customize/classic (attn @metashurick);
#mokum-releases: a) <spoiler> Mokum now supports clickable spoilers;
Re: /support/2423565 I'm considering to add the "super-block" feature that will completely hide your comments **in other people's posts** from the person who you've superblocked. It's going to be available after you've blocked somebody. I think that this is going to be a one-way operation, with no opportunity to unblock. I've been reading the original post quite carefully, but I did not reply, I'm sorry. This is a difficult topic, I don't think there is a good solution, and it's not fun to deal with it.
Please clike this comment if you really think that this is needed. (I already know that this is needed, but just to assess the situation better) --->· псы в рапиде 31
It seems that we've accidentally discovered the social equivalent of the higher states of bromine, with first casualties already claimed.· псы в рапиде 7
a) Private subfeed settings are now on a separate page: https://mokum.place/customize/private-subfeed, together with the explanation of what it is. Old form was removed from the Settings page and replaced with the link.
Some files have been losing their proper color after upload. This issue has been resolved, new files should not have this problem. However, a) old files need to be reprocessed, it's going to take some time; b) WebP support was disabled for now because it was another source of this error; it will be re-enabled after investigation.
#mokum-releases: a) Ruby 2.4.9. Nothing should change, please report if anything breaks.
2.4.9 🙄· просто варежка
Mokum now supports new style of showing display names: "display names + usernames". This could be especially useful on iOS13 with its changes to Safari UI. Also, this setting was moved to the separate subpage: https://mokum.place/customize/display_names
If you see visual glitches in Mokum after upgrade to iOS 13, you should be aware that iOS 13 seems to be one of the buggiest Apple releases ever: https://tidbits.com/2019/10/21/six-reasons-why-ios-13-and-catalina-are-so-buggy/ I see a constant stream of Mokum bug reports that could not be explained by anything that Mokum does. Even if you use Chrome/iOS it still uses Safari/Webkit underneath, so is subject to the same problems. If you decided to upgrade to iOS 13 (or were coerced to do that), please keep upgrading to the latest minor versions, hopefully it will make some of the bugs go away. I'm sorry about that, but there is not much that could be done here, judging from the nature of the bugs.
a) Mokum now better handles touch-based scrolling: arriving real-time changes should not cause visual jumps while scrolling and especially when preparing to scroll;
[EN] Mokum now can import Twitter (and many other services, actually) via https://ifttt.com. The major improvement comparing to previous API capabilities is that 1) the tokens are restricted in rights (only posting is allowed), so you do not have to use your all-powerful API tokens.
2) The token could be embedded directly in URL, which means that IFTTT could be used as is, without intermediate services like hook.io.· псы в рапиде
3) images are now supported automatically.· псы в рапиде
TODO: regenerating tokens; marking imported tweets as such.· псы в рапиде
Importing your tweets to Mokum via https://ifttt.com [DRAFT]. Your Twitter account must be publicly accessible (but your Mokum account can have any visibility status). First, get an account on https://ifttt.com and login. Discussion in English: /changelog/2380245, in Russian: /squadette/2380247
API endpoint description: https://mokum.place/api/doc/index.html#/paths/api~1v1~1import...· псы в рапиде 1
#mokum-releases: I've started working on automatic URL import (basically the idea is to easier support IFTTT for now). The API endpoint is described here: https://mokum.place/api/doc/index.html#/paths/api~1v1~1import... The endpoint is DISABLED at the moment in production, some more testing is needed.
a) fixed double-tap issue in new lightbox (https://mokum.place/customize/lightbox). The problem was that it was too sensitive and did not handle people with less precise fingers (and iPads also, for similar physical reasons).
b) native image lazy loading is now on (for about a week), it should improve data consumption.· псы в рапиде
closing the lightbox in any way other than pressing the back button (i.e. swiping or pressing the 'X' icon) does not clear it from the navigation stack (or whatever this is called? in other words, it sort of "clogs" the back button -- pressing it leaves you on the current page (but, in the case of swiping the lightbox off, on a different spot), as many times as you swipe-or-X-closed lightboxes on it, and only after all that does it actually go back). Firefox, Android (I know, sorry)· очный долб 1
#mokum-releases: Mokum was upgraded to Babel 7; nothing should change but please report if anything breaks for you.
but..... Babel 5 had the best story arc.· Micah 10
Narrator: at the same time, Mokum was upgraded to Basel 3. Nothing should change... nothing at all.· Uranian Iranium 2
a) Fixed a rare issue that could break the page completely in some browsers when editing post with images (tnx @anesthesia); b) the new lightbox (https://mokum.place/customize/lightbox) now closes with animation effect; c) toolbar buttons positioning fixed in the new lightbox, images are no longer cut off in the bottom;
Small data leak (arguably, not even a leak) was found and fixed in Mokum today. Post/group visibility was NOT affected. Likes/comments pages for private and Mokum-only users are not visible to non-subscribed and anonymous users. However, this access control was only active for initial rendering of likes/comments pages. So, if user B (including anonymous) visited one of the likes/comments pages for private/protected user A, and then user A liked/commented one of the posts visible to user B, that post appeared on A's likes/comments page for that user, which shouldn't happen.
Posts visibility was not affected. Also, note that the fact of user's like or comment is not a secret so if B would hypothetically want to monitor A's likes/comments they could just monitor all the posts accessible to them. The leak fixed only somewhat helped in this hypothetical activity.· псы в рапиде
1 2 3 4 5 6 7 8 9 10