[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.· Holy blyat Anatoly 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.· псы в рапиде
a) "Hide NSFW images" checkbox fixed (due to a bug it stopped hiding images 10 days after the checkbox was set), tnx @mudak;
b) some users still report "completely blank page" when opening comments; the reason is unclear but now there is a proper error reporting, please send screenshot/copy-paste if you see an error message, also the page will no longer go blank;· псы в рапиде
You can now try out new lightbox implementation: https://mokum.place/customize/lightbox. Several big user-visible things are still missing: a) no smooth loading of initial image; b) no smooth transition between images; c) no smooth hiding of lightbox; d) navigation buttons should be handled much smarter; e) no zoom-in/zoom-out. The most user-visible change: many images should load much faster because it automatically resizes images for your screen. Implemented features are tracked here: /squadette/2320662; things not in this list are literally not implemented.
For now it does not make a lot of sense to report things unless you are sure that it breaks in your browser. As usual, we will support three and a half form-factors: phones, tablets and desktops (and also niche browsers and devices).· псы в рапиде
Indeed, loads _much_ faster for me. No transitions at this speed is welcome. What I miss is the ability to hide all controls, e.g. by clicking the image.· 9000 2
Burger button menu on mobile phones was reimplemented: a bit less of JS code to download + link to "Best Of Mokum". Also, URL import finally correctly handles HTML entities ("&" etc) when importing twitter etc. Please report if anything breaks for you.
#mokum-releases: "Most Interesting" aggregate page: https://mokum.place/filter/interesting, a combination of Best Of, Most Faved and Well Said: (English: https://mokum.place/filter/interesting/en, Russian: https://mokum.place/filter/interesting/ru, Italian: https://mokum.place/filter/interesting/it, Turkish: https://mokum.place/filter/interesting/tr).
We've started experimenting with the new approach to Settings page. First subpages using the new approach is browser notifications (https://mokum.place/customize/notifications) and hiding NSFW images (https://mokum.place/customize/nsfw). For now nothing really changed, and nothing should break. Please report if anything breaks for you in those two particular areas.
a) images now automatically use Webp if supported by the browser; average Webp file is substantially smaller than JPEG, so it should have positive effect on mobile Androids;
a) posting form was refactored a bit wrt image uploading, please report if anything breaks; b) it is now possible to close drop-downs with Esc button;
As you probably noticed, since April 1st emojis are unconditionally allowed on Mokum. I'd like to explain the reasoning behind this decision and the reasoning behind the decision to disallow emojis in the past. So, from technology point of view, emojis have always been implemented with a certain disregard for backwards compatibility. Unfortunately, this situation does not seem to be improving. When new characters are added to Unicode repertoire, they are usually very quickly available for use on new devices, but non-bleeding-edge devices (95% of devices) are left with limited support options. #emoji-engineering
What's worse, modern emojis, as far as I understand, require special text rendering to support things like flags, skin tones and directions of movement. It means that older clients will show either placeholders or separate components of emoji sequence. Differences in emotion conveyed by different graphical designs on different platforms is a separate, well-known and also not really solved issue.· псы в рапиде 2
It is now possible to disable emojis via https://mokum.place/settings ("Disable emojis"). Instead of emojis you will see their numeric code which could be less annoying.
Mokum UI was updated to be more accessible: almost all post buttons and comment/post edit forms are now keyboard navigable. If you use any assistive tech or just prefer keyboard navigation and have any feedback on how Mokum handles it I'd be happy to hear, and fix anything that needs fixing.
Today's changes: a) improved comment images form;
Not really a change, but we've fixed the root cause for yesterday's morning downtime, tnx @haron. Also, "Best of" and "Well said" pages are now updated much better so hopefully they're going to be more useful.
Just for the record for future historians, because I hope that everyone has already noticed this: you can now (for a month already) attach images to the comments. Direct file upload and pasting from clipboard is supported. TODO: import from URL. Since the feature was introduced a bit less than 1000 images were attached.
There is now a way to soft-block accounts. There are two buttons on account page: "Hide" and "Hide comments". Hide, as usual, prevents account's posts from appearing in your newsfeed. Then you can use "Hide comments" button and comments by that account will be replaced by "comment hidden, click to reveal" button.
1 2 3 4 5 6 7 8 9 10