[-] chiisana@lemmy.chiisana.net 4 points 3 hours ago

I did in fact read the paper before my reply. I’d recommend considering the participants pool — this is a very common problem in most academic research, but is very relevant given the argument you’re claiming — with vast majority of the participants being students (over 60% if memory serves; I’m on mobile currently and can’t go back to read easily) and most of which being undergraduate students with very limited exposure to actual dev work. They are then prompted to, quite literally as the first question, produce code for asymmetrical encryption and deception.

Seasoned developers know not to implement their own encryption because it is a very challenging space; this is similar to polling undergraduate students to conduct brain surgery and expect them to know what to look for.

[-] chiisana@lemmy.chiisana.net 2 points 4 hours ago

Completely agree with you on the news vs science aspect. At the same time, it is worth considering that not all science researches are evergreen… I know this all too well; as a UX researcher in the late 2000s / early 2010s studying mobile UX/UI, most of the stuff our lab has done was basically irrelevant the year after they were published. Yet, the lab preserved and continues to conduct studies and add incremental knowledge to the field. At the pace generative AI/LLMs are progressing, studies against commercially available models in 2023 is largely irrelevant in the space we are in, and while updated studies are still important, I feel older articles doesn’t shine an appropriate light on the subject in this context.

A lot of words to say that despite the linked article being a scientific research, since the article is dropped here without context nor any leading discussion, it leans more towards the news spectrum, and gives off the impression that OP just want to leverage the headline to strike emotion and reinforce peoples’ believes on outdated information.

[-] chiisana@lemmy.chiisana.net 2 points 5 hours ago

While I agree “they should be doing these studies continuously” point of view, I think the bigger red flag here is that with the advancements of AI, a study published in 2023 (meaning the experiment was done much earlier) is deeply irrelevant today in late 2024. It feels misleading and disingenuous to be sharing this today.

[-] chiisana@lemmy.chiisana.net 1 points 1 day ago

If anyone is responsible to keep things around for 100+ years, they’d have a job to do… and even then, cloud providers will still make their life significantly easier than juggling a bunch of storage mediums that goes in and out of storage medium fashion.

[-] chiisana@lemmy.chiisana.net 0 points 2 days ago

You’ll be very hard pressed to find anything else that’d out last the day when all three of AWS, Azure and GCP shutdown and take their data offline.

I get it though, Lemmy doesn’t want to admit these services exist other than to dunk on them in the most anti-corporate fashion… so continue to pretend such is the case!

[-] chiisana@lemmy.chiisana.net 1 points 2 days ago* (last edited 2 days ago)

Another possibility: the console vendors are catching whiff of the whole gate keeper mess, and they don’t want to be at risk of being forced to open up their physical cartridge DRM mechanisms to allow third party cartridges for the relatively small EU market (compared to the rest of the world). Moving towards digital is much easier as result.

It is also clear as day that they’re testing the waters with Nintendo players who are generally deemed to be more casual, and lesser likely to push back compared to the more savvy other major consoles. Once this blows over, they will just move to digital everything across the board, citing successes and cost savings on the other platforms as basis for the move.

[-] chiisana@lemmy.chiisana.net 0 points 3 days ago

Upload it to the cloud and make it someone else’s problem to deal with keeping up with the physical medium changes. Then your descendants only have to worry about figuring out how to deal with an outdated file format they can no longer open… and even when they can finally open it, it’d be super low quality… just like how we have to squint really hard at videos from VCDs now days.

[-] chiisana@lemmy.chiisana.net 3 points 4 days ago

API are secure only if you can secure the authentication details. A modified app (be it as something modified and distributed on a unsanctioned channel, or custom injected by another malicious actor/app) can easily siphon out your authentication tokens to a third party unbeknownst to you the user. However, if the app verifies it came from the approved source and have not been tempered with, then it is much easier to lean on ASLR and other OS level security to make it harder to extract the authentication info.

Multiplayer game operators have obligation to curb modified clients so their actual paying clients have a levelled playing field. By ensuring their apps are only distributed via approved channels and unmodified by malicious players, this improves their odds at warding off cheaters creating a bad time for those that actually pay them to play fairly.

These are just simple cases where this kind of security is beneficial. I am glad Android is finally catching up in this regard.

[-] chiisana@lemmy.chiisana.net 6 points 6 days ago

No, they’re mostly correct; basically no one except Android users in the USA cares. Everywhere else has it figured out with third party messaging platforms that’s geographically favored, and Apple users in USA will continue to use the superior iMessage protocol with each other. Only the Android users in USA are left out from sending/receiving messaging, so they’re salivating over the update like it’s the best thing since sliced bread.

RCS is janky, inconsistent, and carrier dependent. Can’t wait for Android users in the USA to join the better rest of the world. Until GSM consortium mandates end to end encryption and force all carriers to adopt certain version of consistent minimum, RCS is and will continue to be a garbage inferior protocol that should be avoided like the plague.

[-] chiisana@lemmy.chiisana.net 6 points 6 days ago

Not entirely true… the American Android users care about it; Apple users will still default to the superior iMessage as opposed to the inconsistent carrier dependant RCS; rest of the world will use geo-preferred third party messaging app that also offer consistent experience between carriers.

“Buy your mom an iPhone” people.

7
submitted 2 months ago* (last edited 2 months ago) by chiisana@lemmy.chiisana.net to c/voyagerapp@lemmy.world

This morning, when I launched Voyager, my settings were reset. I suspect the app may have upgraded and something caused the preferences to be lost. This wasn’t the first time it happened, and who knows if the underlying conditions triggering this reset would happen again.

It would be nice if we can export our preferences into a json file (or whatever format serializes easiest), and re-import them next time the preferences gets lost, so we don’t need to manually make all the changes.

17

Due to the decentralized nature, and multiple communities on same subject exist across multiple instances, it is not uncommon for people to be subscribed to multiple communities of the same subject. It is also not uncommon for people to submit the same thing to multiple communities of the same subject, thereby resulting in multiple posts of the same content appearing in the feed. Cross post or not, the duplicated content clutter the feed, making it more difficult to consume content quickly.

I think it would be helpful to declutter by hiding/collapsing these posts. A possible implementation could be to keep an index of post titles, author, and submission time; then hide/collapse (cross)posts with same title, submitted by the same author, within some time interval (say for example +/- 1hr). That way the feed wouldn’t be as cluttered.

I understand cross referencing each post against other known posts is an exponentially large task, and could be very resources consuming, so even with the time range filter, it would be prudent to make this an option and likely disable by default to prevent performance issues.

It may be nice to inform the user on the post itself that there are other similar discussions, if they’re interested for other comments/interactions, but that’d be a nice to have in the future kind of thing.

44

I have too many machines floating around, some virtual, some physical, and they're getting added and removed semi-frequently as I play around with different tools/try out ideas. One recurring pain point is I have no easy way to manage SSH keys around them, and it's a pain to deal with adding/removing/cycling keys. I know I can use AuthorizedKeysCommand on sshd_config to make the system fetch a remote key for validation, I know I could theoretically publish my pub key to github or alike, but I'm wondering if there's something more flexible/powerful where I can manage multiple users (essentially roles) such that each machine can be assigned a role and automatically allow access accordingly?

I've seen Keyper before, but the container haven't been updated for years, and the support discord owner actively kicks everyone from the server, even after asking questions.

Is there any other solution out there that would streamline this process a bit?

21

Figured I’d share my finding here…

I got the notification for iOS 16.5.1(c) rapid security response today. Despite hearing about it breaking some sites forcing Apple to pull the update a couple weeks back from a podcast (I want to say ATP but I can’t find it in the show notes so I can’t link to the episode), I decided to install it anyway. After installing and restarting the phone, I found almost nothing works. My games spins forever, all web browsers never loads any website, but surprisingly, iMessages were flowing through.

I poked around a bit, turning wifi off and on again, using cellular data only, toggle between roaming network, etc. and nothing worked. Then I noticed the little VPN icon that flashes by so I went and disabled AdGuard VPN and things seems to work again.

Originally I uninstalled the rapid security patch, and things worked again, but then I realized I’d rather put up with some ads than deal with whatever security ramifications not having the patch would cause. Bearing in mind: the intent of these rapid security patches is that Apple thinks these patches are of utmost urgency (I.E. security issue that’s actively exploited in the wild) and they don’t want to slow people down with a big iOS upgrade, so they release and apply these patches quickly. I ended up reinstalling the patch, and turned off my AdGuard in the mean time. Hopefully AdGuard catches up and release a fix next version or two.

Anyway figured I’d drop the note here in case if anyone else is searching on their Mac trying to figure out why their iPhone isn’t working after that patch.

3
submitted 1 year ago* (last edited 1 year ago) by chiisana@lemmy.chiisana.net to c/selfhosted@lemmy.world

Disclaimers:

First thing first, I'm new to the whole Fediverse, and Lemmy thing, so please don't hesitate to point out any problems you're foreseeing.

Secondly, I'm by no means saying this is the ideal implementation, something something see above. Please don't hesitate to make recommendations for improvements.

Lastly, I'm not sure if it is completely working. I'm still noticing a few issues that I will document and monitor towards the end of the post. If you know of the cause or how to debug further, please do let me know!

Notes and Assumptions:

  1. I am using an ARM server. So I'm using ARM images, you will need to make sure you're using the correct architecture image.
  2. I assume you have Traefik up and running in a separate network. I used docker compose to bring traefik up, minimal configurations, and I'm just hijacking the default network there (project folder was gateway so the complete network name is gateway_default)... there's probably better ways to do this.
  3. On note of networks, I really don't like the fact that the default postgres was left wide open on the lemmyexternalproxy network. I think I've locked my down, but you may wish to double check my work.
  4. I'm not sure if what I am doing with the hostnames are correct, but it seems to work for the most part, so I'm not complaining. If there is a better way, please do advise!
  5. I used an override file for docker compose to apply extra settings. This allows me to keep the original docker-compose.yml untouched, and I can just pull in new changes (theoretically).
  6. Since I'm using traefik, I don't need nginx running doing nothing. I replaced it with a light weight alpine image that just shuts down successfully, so it doesn't use resources.

Without further delays, here's my files:

docker-compose.override.yml:

version: "3.3"

networks:
  lemmyexternalproxy:
    internal: true
  lemmygateway:
    name: gateway_default
    external: true

services:
  lemmy:
    image: dessalines/lemmy:0.17-linux-arm64
    labels:
      - "traefik.enable=true"
      - "traefik.http.routers.lemmy.entrypoints=websecure"
      - "traefik.http.routers.lemmy.rule=Host(`lemmy.chiisana.net`) && HeadersRegexp(`Accept`, `^application/`) || Host(`lemmy.chiisana.net`) && Method(`POST`) || Host(`lemmy.chiisana.net`) && PathPrefix(`/{path:(api|pictrs|feeds|nodeinfo|.well-known)}`)"
      - "traefik.http.routers.lemmy.tls=true"
      - "traefik.http.services.lemmy-svc.loadbalancer.server.port=8536"
      - "traefik.docker.network=gateway_default"
    networks:
      - lemmygateway
  lemmy-ui:
    image: dessalines/lemmy-ui:0.17-linux-arm64
    environment:
      - LEMMY_UI_HOST=0.0.0.0:1234
      - LEMMY_UI_LEMMY_INTERNAL_HOST=lemmy:8536
      - LEMMY_UI_LEMMY_EXTERNAL_HOST=lemmy.chiisana.net
      - LEMMY_UI_HTTPS=true
      - LEMMY_UI_DEBUG=false
    labels:
      - "traefik.enable=true"
      - "traefik.http.routers.lemmy-ui.entrypoints=websecure"
      - "traefik.http.routers.lemmy-ui.rule=Host(`lemmy.chiisana.net`)"
      - "traefik.http.routers.lemmy-ui.tls=true"
      - "traefik.http.services.lemmy-ui-svc.loadbalancer.server.port=1234"
      - "traefik.docker.network=gateway_default"
    networks:
      - lemmygateway
  proxy:
    image: alpine:latest
    command: "true"
    entrypoint: "true"
    restart: "no"
  pictrs:
    image: asonix/pictrs:0.4.0-rc.3

lemmy.hjson:

  setup: {
    admin_username: "chiisana"
    admin_password: "password-redacted-duh"
    site_name: "chiisana lemmy site"
  }
  database: {
    host: "postgres"
    user: "lemmy"
    password: "password-redacted-duh"
    database: "lemmy"
  }
  email: {
    smtp_server: "smtp.mailgun.org:587"
    smtp_login: "lemmy@chiisana.net"
    smtp_password: "password-redacted-duh"
    smtp_from_address: "lemmy@chiisana.net"
    tls_type: "tls"
  }
  pictrs: {
    url: "http://pictrs:8080/"
    api_key: "API_KEY"
  }
  hostname: "lemmy.chiisana.net"
  bind: "0.0.0.0"
  port: 8536
  tls_enabled: true
}

Known issue(s)?

  1. ~~I have my registration disabled as the instance is supposed to be just for my own auth not be depended on other instances. In my /admin section, I'm seeing a ton of users from endlesstalk.org pop up as banned users. I have no idea what that is about, as endlesstalk.org seems to also be used only by one user. I'll be monitoring this and see what's to come of it.~~ Edit: Looks like this is just the way the system is designed, and not a configuration error on my part! All good here. Thanks for clarifying it @lemmy@endlesstalk.org !
  2. I'm not sure if I'm getting all the messages federated. In this community, for example, I can see most if not all recent threads. However, most threads have no comments in it. Some newer threads, I see comments, but it seems to be incomplete. I'm not sure if I'm only supposed to receive new messages, or if something else is happening. I'll be monitoring this, and hoping the federation will just catch up over time.
  3. Edit: It would appear this post itself is not federating to !selfhosted@lemmy.world for some reason... I'm partially hoping it is just caught in some kind of moderation queue, but seeing other posts made after this appear on the list leads me to believe there's still something amiss.

If you encounter any other issue, please do post back so we can try to debug it together. Hope this helps someone!

view more: next ›

chiisana

joined 1 year ago