Raudoitusrauta törröttää pyörätien laidalla.

Leveä lumipalle liikennevalonappipurnukoiden edessä tässä risteyksessä.

Tästä heräsi kysymys, että mitenkähän tarkasti lähiavaruutta nykyisin valvotaan. Jos sukkulaa käytettäisiin toisen valtion satelliitin nappaamiseen (luvatta), onnistuisiko se mahdollisesti todistusjälkiä jättämättä, vai seurataanko tällaisia avaruusaluksia maan pinnalta jo niin tarkasti, että syyllinen olisi ilmiselvä jo alusta asti?

@amyblais Alright, I finally managed to get through the signup. Here’s my suggestion, although it’s in moderation for now, so the link probably won’t work until it’s approved.

A ”Mark read” choice in push notifications about new messages, as seen in many IM apps, would be handy in Mattermost Mobile too. Currently the message can only be marked read by tapping the message to open the app (which is slow).

Hi @amyblais,

I could post this on the feature idea forum, but I can’t figure out how the signup on the site works. When I click on ”Create an account”, I get a prompt to verify my email address, and having done that, a page saying ”Go back to Production to finish logging in”. I don’t know what ”Production” is, and at no point was there any actual way to set up a password, so I can’t log in.

Summary

A ”Mark read” choice in push notifications about new messages, as seen in many IM apps, would be handy in Mattermost Mobile too. Currently the message can only be marked read by tapping the message to open the app (which is slow).

Environment Information

• Device Name: Samsung Galaxy A9
• OS Version: Android 10
• Mattermost App Version: 2.11.0
• Mattermost Server Version: 9.3.0

Steps to reproduce

1. Receive a message notification on the Android app.
2. Pull down the notifications.
3. Expand the received notification.

Expected behavior

Have a ”Mark read” option underneath the expanded notification.

Observed behavior

No ”Mark read” option, only ”Reply”.

I was on my Android device, saving URLs pointing to individual comments in threads at Ubiquiti’s Unifi forums, but later returning to them on my desktop realized that the hash (fragment) portion had been dropped, so that the URLs only pointed to the opening post. Hence, just one link (pointing to the first post) had been saved. This is pretty useless for threads spanning multiple pages, where finding an individual comment is tough without the exact link.

Here’s a (random) example of a URL pointing to the second comment on the third page of one thread. Sharing it from any of Android, iPhone or desktop results in a link pointing to the first post instead.

== System information ==
Ubuntu 23.10, up to date before today’s updates.

== Steps to reproduce (WIP) ==
0. have a group of packages that are kept back from updating, plus some that aren’t (screenshot demonstration attached) below
1. open update-manager
2. (try to) open the kept group, click on their (unchecked) checkboxes
3. do the same for some of the other, non-kept packages
4. repeat 2.-3. for a while

== What happens ==
Update-manager becomes unresponsive, then eventually segfaults:

update-manager[3292]: segfault at 30 ip 00007fc0718b4c41 sp 00007ffc2cca6a68 error 4 in libgobject-2.0.so.0.7800.0[7fc071889000+34000] likely on CPU 4 (core 0, socket 0)

== Other info ==
I’ve marked the steps above WIP because these are the conditions under which I found this today, but I haven’t yet tried narrowing them down, because of course I have little control over which updates are available. (For instance, the kept packages might just be a red herring.)

I initially tried to report the crash file with ubuntu-bug, but despite asking preliminary questions, in the end it never opened a browser to complete the report. I’ll try apport-collect next, but if that fails too, I’ll just attach the crash file here manually.

For Ubuntu 23.10, open a terminal and run `gnome-extensions disable ding@rastersoft.com`