• 0 Posts
  • 95 Comments
Joined 1 year ago
cake
Cake day: July 1st, 2023

help-circle






  • arc@lemm.eetoTechnology@lemmy.worldRabbit R1 is Just an Android App
    link
    fedilink
    English
    arrow-up
    44
    arrow-down
    1
    ·
    2 months ago

    I saw the Marquess Brownlee review of this thing last night and I wonder why companies make this crap and who is fool enough to fund it. It’s obviously doomed to fail, as are most “smart” gadgets & devices. The best that can be said for it, is at least there is no subscription to use it and it’s not outrageously expensive but that’s damning it with faint praise.


  • Not really. Pre-musk, reporting racism & other abuses was more likely to illicit a response than not. Nowadays it is a was of time to even bother unless it is extremely overt… And all the shitheads with few exceptions who were perma banned got reinstated no matter how awful they were.

    And the situation with blueticks is self evident. It used to mean somebody noteworthy - journalists, actors, politicians, authors, scientists etc. Now it’s trolls and narcissists with money to waste on a vanity tick. Popular feeds will have pages of inane comments by these scumbags to scroll through. There are even actual Nazis with blueticks who complain/brag about the ad revenues they receive from engagement. It couldn’t be any more removed than the way it was.



  • Definitely. I think it has just about reached a critical mass users writing content to attract new users and it looks so similar to Twitter there is practically zero friction in moving. I think it’ll really kick off when we see more heavy hitters coming over - big news networks, public figures, governments etc.

    I think news orgs in particular should be removing themselves from obnoxious social media platforms (e.g. Twitter) and move to somewhere where the engagement is more genuine and not toxic rants by racists and morons.


  • Concerning logs:

    1. You can still log to text if you want by configuration (e.g. forward stuff to syslog) and you can use any tools you like to read those files you want. So if you like text logs you can get them. You can even invoke journalctl to output logs on an ad hoc / scheduled basis in a variety of text formats and delimited fields.
    2. Binary allows structured logging (i.e. each log message is comprised of fields in a record), indexing and searching options that makes searches & queries faster. Just like in a database. e.g. if you want to search by date range, or a particular user then it’s easy and fast.
    3. Binary also allows the log to be signed & immutable to prevent tampering, allow auditing, intrusion detection etc… e.g. if someone broke into a system they could not delete records without it being obvious.
    4. You can also use splunk with systemd.

    So people object to systemd writing binary logs and yet they can get text, or throw it into splunk or do whatever they like. The purpose of the binary is make security, auditing and forensics better than it is for text.

    As for scripts, the point I’m making is systemd didn’t supplant sysvinit, it supplanted upstart. Upstart recognized that writing massive scripts to start/stop/restart a process was stupid and chose an event driven model for running stuff in a more declarative way. Basically upstart used a job system that was triggered by an event, e.g. the runlevel changes, so execute a job that might be to kick off a process. Systemd chose a dependency based model for starting stuff. It seems like dists preferred the latter and moved over to it. Solaris has smf which serves a similar purpose as systemd.

    So systemd is declarative - you describe a unit in a .service file - the process to start, the user id to run it with, what other units it depends on etc. and allow the system to figure out how to launch it and take care of other issues. It means stuff happens in the right order and in parallel if it can be. It’s fairly simple to write a unit file as opposed to a script. But if you needed to invoke a script you could do that too - write a unit file that invokes the script. You could even take a pre-existing init script and write a .service file that kicks it off.


  • arc@lemm.eetolinuxmemes@lemmy.worldSystemd controversy be like
    link
    fedilink
    arrow-up
    27
    arrow-down
    1
    ·
    edit-2
    4 months ago

    Kind of sad there are still people raging over systemd. When it flares up in discussions there is the usual debunked nonsense:

    • it only logs information to binary and this is somehow bad. Except it it can be configured to log to text as well and it uses binary so it can forward secure sign records to prevent tampering as well as offering database style query operations.
    • it’s insecure because the repo has millions of lines of code. Except that they compile into hundreds of small binaries running with least privilege, and often replacing the task of far more dangerous processes (e.g. there is an NTP client in systemd which sets the time and nothing else).
    • various rants about the primary author

    What is more bizarre is the nostalgia and hearkening back to sysvinit scripts when systemd didn’t replace sysvinit! Systemd replaced upstart which replaced sysvinit. Because writing 100s of lines of script to stop/start/restart a process sucked - insecure, slow, didn’t scale, didn’t capture dependencies and everyone knew it. Upstart was the first attempt to solve the issue and was used in Debian / Ubuntu, Fedora / Red Hat, openSUSE and others until systemd came along.


  • You don’t have to take your eyes off the road to operate a control. You might need to learn where some are in a new car, but then you instinctively reach for and operate the ones you use all the time. It’s muscle memory.

    This is not the case in a touch screen where controls may or may not be visible at any given time and you have no chance of operating them unless you physically look at the screen to control where you touch it. Maybe this arrangement is fine for some non-critical functions, but it absolutely isn’t for critical ones.

    What is worse is that cars from Tesla are even getting rid of indicator stalks which is fantasically dangerous. Maybe it’s not a big deal in the US where roundabouts are uncommon but they are all over the place in Europe and the rest of the world and lack of indicators will cause crashes and fatalities. Just so Elon Musk could save a few bucks on a stalk. And if that results in a lower EuroNCAP score then boohoo for him. I can imagine the raging and legal threats that he’ll engage in if that happens.


  • Personally I think that the following car functions should be mandatory physical controls - wipers, indicators, hazards, side/headlights, door locks, defogger / defroster, electronic parking brake. forward/reverse/neutral/park. And they should be controls that have fixed position in the car (i.e. not on the wheel) with positive and negative feedback.

    And fuck Tesla or any other manufacturer that wants to cheap out on a couple of bucks by removing them. Removing physical controls has obvious safety implications to drivers who are distracted trying to find icons on a tablet.



  • Yuzu gave them the opening to sue though. If they had been more circumspect - “Oh this is to develop homebrew / indie games nudge nudge” then maybe Nintendo wouldn’t have unleashed the lawyers or done so ineffectively. After all it wouldn’t be Yuzu’s fault if some wicked website corrupted their pure intentions by releasing device keys or patches that allowed their emulator run commercial games. But they were more blatant than that.

    Also from an empathic perspective, of course Nintendo were going to sue. Yuzu should have known they would since that’s what console platforms do when something interferes with their profits. Yuzu is doubly bad since it interferes with hardware sales and game sales unlike custom firmware / cartridges which only affect game sales.

    Of course the genie is already out of the bottle. Yuzu’s source code and binaries were on github for anyone to clone / fork. All the games are out in the wild. The piracy will carry on. I think it’s fair to say the NSP is effectively dead as a platform at this point. If a NSP2 turns up this year, as rumored, then I expect it will have revised anti-piracy measures and potentially a heavy online service aspect to go with it - it’s far easier to detect pirates and wield the banhammer when a device is online.



  • I wait for “try prime for 30 days” offers. I’ll sign up for it, instantly cancel it to prevent recurring bills, and then order whatever it was I was thinking of over the last six months. Because once upon a time I’d be on Amazon all the time, browsing this and that, but it has become such a cesspool that I infrequently bother. If I wanted to wade through a sea of Chinese OEM crap and counterfeit products, then I might as well use Aliexpress and be done with it.



  • Doesn’t sound like this system is safety critical. You should be more worried if some hacker can change train signs from stop to go. If you ever ride on a train and see steel boxes by the side of the track, those are control systems and they run up and down the line. They might be locked, or possibly alarmed but that’s about the extent of their protection. A simple attack would be to just take an axe to one, or set fire to it. A more sophisticated attack could snoop on the profinet traffic and do something evil.