The host’s tap interface is one ip address below the address of the guest on a /31 subnet. We need to increment the op address returned from ifconfig by 1 to get the guest’s ip.
I legitimately love that Mastodon is no longer hipster enough for us and
we have to make more cut-down and minimal versions.
But Mastodon was never the only game in town. There’s a whole
plethora of stuff built on activitypub, and that’s the way it’s supposed
to be.
The main reason you know about honk is because Muskrat is in the process
of murderizing Twitter (good riddance), leading to an uptake of wider
interest in federation. One size does not fit all. Lots of nonconformists
or “hipsters” or whatever are just gonna be using shit you never heard of,
quietly, to avoid the sneering.
Sure, but I find the docs for honk to be totally opaque, which I guess is the point. Is it a full server? Is it just an ugly client? Do I have to toot the word “honk”? I don’t know the answers to these questions, but god bless those honkers anyway for keeping the internet weird.
Mostly the big versions are hard to run. People who do their own ops in repeatable ways end up designing different software to optimize what we care about: easy ops.
I was amused by your comment but on reflection decided it missed the motivation.
Now maybe @tedu making honk wasn’t your point. Maybe you were talking about users who just want a fediverse presence and are driven by a hipster need to be different. That point I’ll give you and your merriment.
Oh, I know. It’s a reasonable use case and one I appreciate. It’s just also, in this case, driven by a hipster need to be different. (“hipster” is a terribly ill-defined word I know; I’m using it loosely.)
I also imagine it’s a reference to Untitled Goose Game, which makes me enjoy it even more.
I like fzf; but it’s in no way a Linux fuzzy finder tool. In fact the author describes it as “an interactive Unix filter”, and it runs perfectly happily on my FreeBSD system.
well, it is on a redhat blog after all… I use it on a mac too. Still I found the article pretty good. I did not know about this preview feature and I am totally going to use that all the time now.
So I’m not the only one who finds squeezing Linux where it should either be completely omitted, or Unix should be used, jarring - ip(8), systemd(1), sure… but fzf(1)?
I honestly can’t think of a single situation in which I would ever transfer data to my phone using a cable. In fact, I can’t think of a single situation in which the cable has been used for anything other than charging the thing since… I don’t know, maybe the iPhone 3G?
It may be out of fashion but there remains a surprisingly comprehensive tool built into macOS Finder for syncing your data with an iPhone. For someone who doesn’t want to use the cloud for contacts, music, photos etc. they could get on perfectly well with a Mac, iPhone and Time Machine for backups. And they might appreciate higher speeds!
The speed of cloud syncing is usually irrelevant because it happens in the background. The problem with Apple is they don’t provide a “sync now, dammit” button for the times when you actually do want it to sync now.
This used to bug me, but for the last couple years the syncing has been so low latency I haven’t had problems. Maybe my experience is in some way better than average, but for me syncing 50 new photos means waiting a minute tops.
For me, it sometimes means waiting for days. Also, occasionally it just gets stuck, and the only solution seems to be to delete and recreate the photos library…
I am using the same photo library since 2013, resynced onto new MacBooks and iPhones over the years through iCloud. The initial sync takes an eternity, as it’s now ~150 GB, but other than that no problems. I wonder what’s causing our differing experiences.
My experience for many years has been that wifi provides substantially higher throughput than any hardwired connection less than gigabit ethernet. Faster than Lightning, faster than any USB, faster than Thunderbolt. Not yours?
When I buy a new phone, I typically take a backup of the old one and restore it to the new one via cable. For the other three years, yeah, charging only.
iPhone 14 “Pro” still, for some reason, has a Lightening port which is limited to USB 2.0 speeds. Why!?
I couldn’t find information on there that it is limited to USB 2.0 speeds - USB-A-to-Lightning (no e BTW) cables are USB 2.0 but they will provide a USB-C-to-Lightning cable with the new iPhone 14.
Backwards compatibility. I think their plan is to move to wireless charging and wifi/bluetooth for everything eventually. Just closing off all physical connectors completely, much like they did with Apple Watch.
I’d argue it has nothing to do with the EU. Their perspective(I believe) is cables are stupid and need to die. They clearly have won that war around headsets. They haven’t managed to with charging/sync cables yet, though I’d argue they haven’t really started waging that war yet, as they don’t quite have everything they need in place yet.
I’ll be pretty surprised if within the next 5-ish years iPhones literally have no physical connections whatsoever. Maybe they still have a button or three, but I imagine even those will likely die eventually too. They basically said it in their presentation today: “You shouldn’t know where hardware and software ends.” -@calvin comment above.
60 GHz is pretty sweet, per a friend who’s messed around with it, and Apple’s using it in the Watch for some limited stuff. A Qi+60 only iPhone is quite likely. It’ll take some getting used to, but I expect it’ll become normal pretty quickly.
Have they? Wired headphones still win for shared hardware use (charging and re-pairing is annoying) and for musicians (delay is and always will be there).
But is it noticeable? I’d be surprised if even a 1ms delay is noticeable to a human (for audio - it’s the absolute maximum latency for haptics) and that’s at the upper bound of local wireless latency unless there’s a lot of EM noise causing retransmissions.
Almost all of my gaming now is via the Xbox cloud gaming service, where the game runs on a computer in a datacenter 12ms away from my Xbox, the controller is connected to the Xbox via Bluetooth, and the audio goes via a DTS-encoded digital connection to a decoder, which then sends it to an analogue amplifier. In spite of all of the things there that are causing delays (the Internet round trip between pressing a button and getting a frame / audio sample back, in particular), I can’t tell that a game isn’t running locally (unless it’s a Series X game, in which case I notice that it looks better than if rendered locally).
A 1ms delay is absolutely fine, that’s less than what you get from a MIDI-connected electronic drumkit. Also, wireless in-ear monitors have been a thing in studios for years now. I think their delays are a little higher than that. I don’t know the exact figures (I haven’t exactly been in a band since high school so I’m not exactly up to date with the latest technology :-P) but the professional musicians I know swear it’s comparable to the delay from a digital effects pedal so… 2-3ms, maybe a little higher?
There’s no “minimum threshold” for musicians – the latency at which it starts to mess up with your playing/singing depends a lot on setup and instruments. Also, because any setup has delays, you kind of learn to deal with those – singers routinely deal with 10-15ms delays in studios, and it probably sucks the worst for them, because they get to hear their voices immediately through their sinuses and face bones. As long as the delays are constant, you can handle delays surprisingly well.
(Edit: FWIW, the thing that really kills it, even at low-latency figures, is jitter. Way back, when I was way younger and in a band and couldn’t afford a real bass amp, I’d lug my old Pentium to practice and use… gnuitar, I think (I started with something else but I can’t recall what, I switched to gnuitar after a few years). The poor thing could give me 20ms of latency (and really bad sound) on a good day, and it was good enough. 10ms, or 15ms, are just fine, but if there’s jittering between 10 and 15ms, I’m no longer able to reliably play behind of ahead of the beat).
The delay of bluetooth headphones is in the order of hundreds of milliseconds. It’s so bad that video players have to compensate for it. The wireless audio stuff for the pro market is UHF, and last I checked it was all analog.
I have no idea why bluetooth headphones, including Apple’s W2 headphones are so bad and have such high latency, but they do. You can certainly have low-latency wireless audio, just not with any existing consumer standard.
It really depends on the codec / os processing though. For example the difference between Windows and Linux/pipewire is insane. The latter has next to no delay for cases like media playback.
Yeah, I have no idea what kind of latency Bluetooth headsets have, I’m all wired, but only as a matter of personal preference (easier troubleshooting, no batteries to die/recharge etc.). Hundreds of ms would drive me nuts just for everyday listening :-D.
It really depends on what you’re doing. For example if you try to play an electric guitar with effects done on the computer with playback back into headphones, anything above 5ms is clearly noticeable. But most systems can’t achieve even that out of the box (you need either the exclusive mode on Windows or pipewire/jack on Linux).
For games, I guess even if the sound is one frame behind its not going to be that easy to tell.
I agree wired headsets have their use-cases, they likely always will.
I would argue they absolutely have won that war, People are still buying iPhones and iPads in huge numbers, even though none of them have headphone jacks anymore.
Many android phones have also followed Apple down this path as well and no longer ship with headphone jacks.
Backwards compatibility with what? Charging cables? A watch doesn’t take video or photos, or store files. Fast transfer speeds for video is pretty important to most workflows, and wireless is not going to be able to keep up. The backwards compatibility doesn’t hold up when you consider that literally everything else has moved onto the USB-C standard, including their iPads and MacBooks.
Edit: if they were really concerned, they’d make a USB-c male to lightening female adapter. Problem solved.
100%. Plus all the various lightning devices out there in the world. I think @ngp’s definition of backwards compatibility and ours are quite different.
@ngp My perspective is, they consider wires stupid. They have waged war(and won) when it comes to wired headsets. They haven’t quite started the war on charging/sync cables, but they are working on it. I imagine they didn’t expect it to take quite so long, as I agree Lightning is looking a bit long in the tooth now, but it would be idiotic of them to switch to USB-C for a few years while they finish off their cables are terrible war.
USB-C port is still far more fragile than the lighting port. It’s easier to replace a lighting cable than to take apart an iPhone and desolder a USB-C port and replace it because the little pins in the middle have been damaged.
Sounds like you need to clean the port or replace the cable. The only times I’ve had a connection issue have been when there’s been fluff in the port or the cable has a discoloured pin and will only connect the other way around. They don’t seem to be fixable when that happens but I don’t know if I’m missing a technique that works.
If you’re talking about GnuPG, then absolutely. Why can’t we have something simple like signify, eh? If you’re talking about OpenPGP then, well, even with its issues, a suitable replacement would still needs its own RFC first :^)
Yes, it looks as if OSV could be fairly easily translated to VuXML and vice versa. They seem to capture the same information in an almost identical schema, just with different serialisation formats.
An RFC with no comparison against VuXML and which looks less useful. Yay?
It looks like it comes from an era (2003) when XML was quite fresh and cool(?). Is anyone apart from FreeBSD using it? It seems like if it’s never mentioned in duscussions about security.txt, then it’s mostl likely due to eveyone involved in VuXML either not being interested any more or asleep.
Human-readable is the new shit, next will be binary ;^)
I don’t know. I think NetBSD was, not sure if they still do.
It seems like if it’s never mentioned in duscussions about security.txt, then it’s mostl likely due to eveyone involved in VuXML either not being interested any more or asleep.
It looks as if I was misunderstanding the purpose of security.txt based on the title. It is about defining a way of reporting security vulnerabilities to the project, not a way for a project to report security vulnerabilities. The only consumer of this will be a human security researcher who has found a vulnerability. There is some value in having a convention here, but any text file is fine as long as it’s easy to find. I don’t care what the structure of the file is because a human will parse it and it will be a small part of the task of finding and documenting a vulnerability.
VuXML solves the other part of the problem. Every security vulnerability in a package shipped by FreeBSD gets an entry in the VuXML stream and it’s machine-parseable and easy to aggregate. It looks as if security.txt is designed to be machine-parseable (and therefore probably possible to aggregate) but it requires a bespoke parser. I’d love to see a VuJSON, since JSON parsers are simpler and more ubiquitous than XML these days.
The main value for this kind of thing is in auditing. On a FreeBSD system, I can type pkg audit and get a report of all packages with known vulnerabilities, generated from the VuXML. I believe Debian has something similar, though I don’t know anything about their implementation details. I can also build my own auditing tool and can easily produce a VuXML stream for my own package repositories that integrates with this.
It would be great if there were tooling to allow upstream projects to more easily publish their CVEs in machine-readable format that could be converted to VuXML. There’s a small ontology problem (VuXML tells you the range of versions for packages that are vulnerable but the versions of upstrea, of the FreeBSD packages, of the Debian packages, and so on don’t always align) but that’s something that could be solved with a bit of metadata in the packages allowing some tooling to handle the mapping.
I honestly don’t care about being compatible with the GPL. The Lazarus components I use are “LGPL with linking exceptions” as far as I know, my code itself was not designed to be embedded in any other software, so the difference is mostly academic here, if I’m not mistaken.
I mean, the CDDL is effectively “MPL + GPL incompatibility” so if you don’t care about GPL one way or the other using MPL would mean anyone who finds something useful in your code could copy it to a GPL project.
It’s all academic until it’s not, and by then it’s usually too late to change :)
One of the advantages of being the project lead, main developer and license steward of a project is that it’s never too late to change.
I won’t block a license discussion once this happens. Until then, the CDDL is just fine. :-)
(I have my own prejudices against the GPL though, so the discussion will - at least - be fruitful.)
I really enjoy everything the author of neatvi has written (neatroff especially). I reached out to him once via email basically to tell him I was a fan. He was very gracious.
Don’t confuse OpenVi/OpenBSD-vi, nvi1, and nvi2. These are all different programs that share the same heritage.
OpenVi is derived from OpenBSD vi, which derives from nvi version 1.79, released in 1996. There has been 25+ years of independent development as part of the OpenBSD base system and it has diverged greatly in that time, with the development going in a different direction.
Nvi1, currently on version 1.8x, is maintained at https://repo.or.cz/nvi.git - I believe the latest version of this editor does have multibyte support, but this is not the OpenVi/OpenBSD version of the editor.
Nvi2 shares the same heritage as well, but is also quite far removed from 1996 code. It is actively maintained at https://github.com/lichray/nvi2 and also includes multibyte support.
Currently, optimizing for size using link-time garbage collection with GCC 11.2 on an x86_64 glibc Linux system gives a good idea of the changes over time and the different direction these editors have taken. OpenVi is also simplified in structure and does not have the three levels of abstraction of Nvi 1.8x - there is no library interface layer.
For OpenVi, the compiled binary is 278K, and for Nvi1 (nvi-1.81.6-45-g864873d3) the compiled binary is 528K (36K for vi, 528K for libvi).
OpenVi has a single configuration standard with no dependencies beyond curses.
Nvi1 has many options beyond trace/debug (“widechar” “gtk” “motif” “threads” “perl” “tcl” “db3/4” “internal-re”) - so at least 255 different build variations are possible.
(I’ve not yet built Nvi2 myself on Linux so I can provide an actually fair comparison yet, but I will, and I’ll summarize the data in an FAQ section of the README)
(Note that I was using the defaults here, I’m sure that it’s possible to trim down Nvi 1.8x further, but I’m comparing the default compilations, optimized for size (GCC, -Os, -fdata-sections, -ffunction-sections, link-time GC enabled), but Nvi 1.8x is a much more complicated program, and has a different feature set, and different supported options.
Well, I allowed myself to omit the fact that OpenBSD’s vi has seen some independent development past nvi 1.79, which is true. A “(based on)” should be inserted before “an old version” in my original comment. But I appreciate the thorough summary of nvi versions!
It should be noted that DragonFly BSD has imported nvi2, but with some modifications as well.
It’s unfortunate there is so much confusion surrounding the various nvi-based editors, mostly due to them all being so similarly named.
Part of why I chose to call this project OpenVi was because the name was - suprisingly - available, and does not directly imply that OpenVi is exactly Nvi1/2 or OpenBSD’s vi.
(In particular, all bugs in OpenVi should be considered my fault.)
I will confirm that Neatvi is an excellent project, but I’m a bit more interested in Nextvi - https://github.com/kyx0r/nextvi - the RTL/bidi in Neatvi is a huge strength and is done very cleanly when compared to other vi-likes
yawn systemd bashing, how boring, and how expected
anyway, this is a typical strawman response.
automounting is not a novel concept… but noone claimed it is. the post shows how systemd nicely integrates this concept with other systemd concepts so that, for example, it becomes easy to start services that depend on such a network mount, ensuring the right ordering during boot, etc.
yawn systemd bashing, how boring, and how expected
My comment wasn’t systemd-specific - it was aimed at any solution in need of a problem - my point was that automounters have existed for well over three decades and they do well what they’re good at.
Also, unless I’m missing something, the article describes automating an fstab(5) mount - it isn’t a real automount as in, mount on request/access and unmount if not in use, not to mention other features such us various substitutions (key, wildcard, variable, etc.), etc.
None of the auto mounters I know of integrated with system service ordering and dependencies very well. Also systemd already is the place where fstab handling happens, so it effectively needs to be an (auto)mounter anyway. I don’t think reinventing the wheel criticism really applies here.
I have moved from autofs to using the systemd built-in feature in the cases where we are automounting. The advantage is that systemd is already installed, so an additional package is not needed any more, it uses the same syntax for defining mounts as we’re already used to for services and service startup order can be nicely integrated into the auto mount availability.
This as done away with quite a few sleep hacks in old style scripts and so far worked perfectly and did not necessitate new hacks.
Do I need my init system to have built-in automount support? No. But it’s very convenient and very robust, so I’m more than happy to use it.
If you are concerned by bloat or unhappy with the functionality provided by systemd, feel free to continue using autofs or anything else for your mounts.
The one thing I wish was different is if I could have the mount and automount unit in a single file. systemd is very boilerplaty that way and while I see that in some cases the split makes sense, in my simple use cases, it’s just baggage
It’s like an interactive telephone book, you can index all of the users of the domain with “finger @plan.cat” and you can look up for a sepecific user like “finger [email protected]”.
It would be awesome if mail providers started to provide finger so you can quickly have information about someone (which would be, of course, the information the want to make public)
Most servers started to close the finger port for incoming connections in the late ’90s because the protocol was a great way of enumerating the valid accounts on the system. If your mail provider enables it then you can find all of the addresses that will work and that makes sending spam to that provider a lot easier.
I first saw finger in 2000 and even then it only worked on the local network and was blocked at the firewall for the machines that hosted a web server / email.
Back in Days of Yore, before the internet went mainstream and security Got Serious, most UNIX systems supported a protocol called finger.
You could say finger [email protected] and, if I updated my .plan file, see what I had written there and, depending on the server, maybe even what I was running on the machine at the moment.
People took advantage of this for all kinds of strange and wonderful things, including internet connected coffee and soda machines where you could [finger them for status].
This site resurrects the protocol but gives you a place to advertise your status without opening up a security hole in workstations you actually use/care about, and in its own way creates a kind of social network :)
It would also be neat if lobste.rs hosted a finger server. For example finger [email protected]
could return some of the information found on https://lobste.rs/u/fs111. Maybe users profiles also have a “plan” section for “what are you doing this week” answers? Not sure the utility of all this, but the idea tickles me!
While this may seem nostalgic for some folks, I was entirely unaware of this feature[1] and am excited to see how it unfolds. So far it seems to just be a landrush for short names.
His engagement with lobste.rs was much more polarising than burntsushi. The latter didn’t jump into comment sections to deliberately kick off a flame war that may not have otherwise occurred; the former did so deliberately and unashamedly. I heartily respect both their views but I can understand why they might be moderated differently.
Then clearly this community is not what the admin intended it to be before banning this domain because the stories from that domain were routinely getting above 30 points which is rare for most stories. It is time to shut this whole website down and just change it to be a private RSS feed of the admin.
It’s an attempt to avoid the Repugnant Conclusion; the mere addition of a steady attractor of upvotes can degrade the quality of life for everybody else.
Please go be loudly disappointed in the entire world (and promote sourcehut) somewhere else.
I really hope that this happened at the end of a process of attempting to politely engage, rather than as the immediate response. That reads like something from a burned-out moderator who needs to take a break.
I don’t like anyone getting banned for anything. I have a lot of respect for how much DeVault puts into his open source contributions and am envious he can live off of it. That being said, he banned me on Mastodon forever ago because I reposted an open letter a professor made during the eight of the 2020 US riots. We had a discussion over DMs and he blocked me in the end.
The more I lean about some of the stuff he’s said and done, I realize I can still respect his work while still agreeing with all the others who’ve come to the conclusion his actions are often inflammatory or childish. I’m not surprised he’s banned. He left the Fediverse a few months back too.
The reason for banning the user account was reported by the admin as apparently rude comments/encouraging arguments/arguing? The comments were usually upvoted though as far as I remember so I think the decision was mostly arbitrary.
The domain was blocked just because the admin banned the author from lobsters, not because there was something wrong with the content on that website. Drew wasn’t even the one posting his blog posts here.
Therefore at least one of those decisions is nonsensical.
You can try to create a website with semi-transparent moderation policies but that will never fix the standard power abuse by moderators like in this situation. The personal grievances usually win and no moderation log will fix this. The community enjoyed the content and @pushcx didn’t => the comments and the domain get nuked off the website.
I tried to get an answer at least to why the domain was banned but of course I never did (in the name of transparency).
The reason for banning the user account was reported by the admin as apparently rude comments/encouraging arguments/arguing? The comments were usually upvoted though as far as I remember so I think the decision was mostly arbitrary.
The domain was blocked just because the admin banned the author from lobsters, not because there was something wrong with the content on that website. Drew wasn’t even the one posting his blog posts here.
I disagree with your opinion that his behavior on the site was not rude, though I didn’t look closely at all of his posts so I can’t say for certain. What I do agree with is the domain ban. The ban itself seemed unclear and arbitrary. Moreover, as you mentioned, a domain ban affects much more than just a user, it affects all content on that domain.
Running OpenBSD on an RPI3 is much easier than it seems, only non-standard RPI requirement is doing an actual install from the SD card and requiring a serial terminal our external monitor/keyboard instead of just flashing an image and booting.
One trick I ended up doing post-install was mounting /tmp as type mfs to avoid writes to the SD card when possible.
It’s overall stable and there are a good number of arm64 pkgs to install and setup smaller network appliances like a dnscrypt-proxy or a gemini capsule.
adventure(6)Wikipedia article better describes the game ;^)
https://en.wikipedia.org/wiki/Colossal_Cave_Adventure
Thanks @jcs!
Just having a look at the script. Why do the IP addresses need converting at all? Why the need for
INET_NTOAandINET_ATONfunctions?The host’s tap interface is one ip address below the address of the guest on a /31 subnet. We need to increment the op address returned from ifconfig by 1 to get the guest’s ip.
I legitimately love that Mastodon is no longer hipster enough for us and we have to make more cut-down and minimal versions.
But Mastodon was never the only game in town. There’s a whole plethora of stuff built on activitypub, and that’s the way it’s supposed to be.
The main reason you know about honk is because Muskrat is in the process of murderizing Twitter (good riddance), leading to an uptake of wider interest in federation. One size does not fit all. Lots of nonconformists or “hipsters” or whatever are just gonna be using shit you never heard of, quietly, to avoid the sneering.
Sure, but I find the docs for honk to be totally opaque, which I guess is the point. Is it a full server? Is it just an ugly client? Do I have to toot the word “honk”? I don’t know the answers to these questions, but god bless those honkers anyway for keeping the internet weird.
While ugly is a matter of taste, the
READMEsays it is the former:Mostly the big versions are hard to run. People who do their own ops in repeatable ways end up designing different software to optimize what we care about: easy ops.
I was amused by your comment but on reflection decided it missed the motivation.
Now maybe @tedu making honk wasn’t your point. Maybe you were talking about users who just want a fediverse presence and are driven by a hipster need to be different. That point I’ll give you and your merriment.
Oh, I know. It’s a reasonable use case and one I appreciate. It’s just also, in this case, driven by a hipster need to be different. (“hipster” is a terribly ill-defined word I know; I’m using it loosely.)
I also imagine it’s a reference to Untitled Goose Game, which makes me enjoy it even more.
One can never know the origins of things in @tedu’s brain, but you certainly can wonder.
Not precisely but one can make an educated guess - think:
:^)
I like fzf; but it’s in no way a Linux fuzzy finder tool. In fact the author describes it as “an interactive Unix filter”, and it runs perfectly happily on my FreeBSD system.
well, it is on a redhat blog after all… I use it on a mac too. Still I found the article pretty good. I did not know about this preview feature and I am totally going to use that all the time now.
I’ve used it on windows too!
So I’m not the only one who finds squeezing Linux where it should either be completely omitted, or Unix should be used, jarring -
ip(8),systemd(1), sure… butfzf(1)?[At work] I use plain old Markdown documents in a on-prem instance of GitLab but, if I was to set up something from scratch, I’d start with ikiwiki.
iPhone 14 “Pro” still, for some reason, has a Lightening port which is limited to USB 2.0 speeds. Why!?
I honestly can’t think of a single situation in which I would ever transfer data to my phone using a cable. In fact, I can’t think of a single situation in which the cable has been used for anything other than charging the thing since… I don’t know, maybe the iPhone 3G?
It may be out of fashion but there remains a surprisingly comprehensive tool built into macOS Finder for syncing your data with an iPhone. For someone who doesn’t want to use the cloud for contacts, music, photos etc. they could get on perfectly well with a Mac, iPhone and Time Machine for backups. And they might appreciate higher speeds!
The speed of cloud syncing is usually irrelevant because it happens in the background. The problem with Apple is they don’t provide a “sync now, dammit” button for the times when you actually do want it to sync now.
This used to bug me, but for the last couple years the syncing has been so low latency I haven’t had problems. Maybe my experience is in some way better than average, but for me syncing 50 new photos means waiting a minute tops.
For me, it sometimes means waiting for days. Also, occasionally it just gets stuck, and the only solution seems to be to delete and recreate the photos library…
I am using the same photo library since 2013, resynced onto new MacBooks and iPhones over the years through iCloud. The initial sync takes an eternity, as it’s now ~150 GB, but other than that no problems. I wonder what’s causing our differing experiences.
Same here. Something else has to be going on for 4ad.
My experience for many years has been that wifi provides substantially higher throughput than any hardwired connection less than gigabit ethernet. Faster than Lightning, faster than any USB, faster than Thunderbolt. Not yours?
If you’re using the ProRes recording, it would be nice to be able to ingest footage to a Windows PC in a timely manner
EDIT: or, hell, to a Mac without resorting to AirDrop
When I buy a new phone, I typically take a backup of the old one and restore it to the new one via cable. For the other three years, yeah, charging only.
I couldn’t find information on there that it is limited to USB 2.0 speeds - USB-A-to-Lightning (no e BTW) cables are USB 2.0 but they will provide a USB-C-to-Lightning cable with the new iPhone 14.
GSMarena lists the phones as USB 2.0 proto.
I was hoping for an authoritative source.
Backwards compatibility. I think their plan is to move to wireless charging and wifi/bluetooth for everything eventually. Just closing off all physical connectors completely, much like they did with Apple Watch.
They will do whatever to avoid complying with the EU…
I’d argue it has nothing to do with the EU. Their perspective(I believe) is cables are stupid and need to die. They clearly have won that war around headsets. They haven’t managed to with charging/sync cables yet, though I’d argue they haven’t really started waging that war yet, as they don’t quite have everything they need in place yet.
I’ll be pretty surprised if within the next 5-ish years iPhones literally have no physical connections whatsoever. Maybe they still have a button or three, but I imagine even those will likely die eventually too. They basically said it in their presentation today: “You shouldn’t know where hardware and software ends.” -@calvin comment above.
60 GHz is pretty sweet, per a friend who’s messed around with it, and Apple’s using it in the Watch for some limited stuff. A Qi+60 only iPhone is quite likely. It’ll take some getting used to, but I expect it’ll become normal pretty quickly.
Have they? Wired headphones still win for shared hardware use (charging and re-pairing is annoying) and for musicians (delay is and always will be there).
But is it noticeable? I’d be surprised if even a 1ms delay is noticeable to a human (for audio - it’s the absolute maximum latency for haptics) and that’s at the upper bound of local wireless latency unless there’s a lot of EM noise causing retransmissions.
Almost all of my gaming now is via the Xbox cloud gaming service, where the game runs on a computer in a datacenter 12ms away from my Xbox, the controller is connected to the Xbox via Bluetooth, and the audio goes via a DTS-encoded digital connection to a decoder, which then sends it to an analogue amplifier. In spite of all of the things there that are causing delays (the Internet round trip between pressing a button and getting a frame / audio sample back, in particular), I can’t tell that a game isn’t running locally (unless it’s a Series X game, in which case I notice that it looks better than if rendered locally).
A 1ms delay is absolutely fine, that’s less than what you get from a MIDI-connected electronic drumkit. Also, wireless in-ear monitors have been a thing in studios for years now. I think their delays are a little higher than that. I don’t know the exact figures (I haven’t exactly been in a band since high school so I’m not exactly up to date with the latest technology :-P) but the professional musicians I know swear it’s comparable to the delay from a digital effects pedal so… 2-3ms, maybe a little higher?
There’s no “minimum threshold” for musicians – the latency at which it starts to mess up with your playing/singing depends a lot on setup and instruments. Also, because any setup has delays, you kind of learn to deal with those – singers routinely deal with 10-15ms delays in studios, and it probably sucks the worst for them, because they get to hear their voices immediately through their sinuses and face bones. As long as the delays are constant, you can handle delays surprisingly well.
(Edit: FWIW, the thing that really kills it, even at low-latency figures, is jitter. Way back, when I was way younger and in a band and couldn’t afford a real bass amp, I’d lug my old Pentium to practice and use… gnuitar, I think (I started with something else but I can’t recall what, I switched to gnuitar after a few years). The poor thing could give me 20ms of latency (and really bad sound) on a good day, and it was good enough. 10ms, or 15ms, are just fine, but if there’s jittering between 10 and 15ms, I’m no longer able to reliably play behind of ahead of the beat).
The delay of bluetooth headphones is in the order of hundreds of milliseconds. It’s so bad that video players have to compensate for it. The wireless audio stuff for the pro market is UHF, and last I checked it was all analog.
I have no idea why bluetooth headphones, including Apple’s W2 headphones are so bad and have such high latency, but they do. You can certainly have low-latency wireless audio, just not with any existing consumer standard.
It really depends on the codec / os processing though. For example the difference between Windows and Linux/pipewire is insane. The latter has next to no delay for cases like media playback.
Yeah, I have no idea what kind of latency Bluetooth headsets have, I’m all wired, but only as a matter of personal preference (easier troubleshooting, no batteries to die/recharge etc.). Hundreds of ms would drive me nuts just for everyday listening :-D.
It really depends on what you’re doing. For example if you try to play an electric guitar with effects done on the computer with playback back into headphones, anything above 5ms is clearly noticeable. But most systems can’t achieve even that out of the box (you need either the exclusive mode on Windows or pipewire/jack on Linux).
For games, I guess even if the sound is one frame behind its not going to be that easy to tell.
I agree wired headsets have their use-cases, they likely always will.
I would argue they absolutely have won that war, People are still buying iPhones and iPads in huge numbers, even though none of them have headphone jacks anymore.
Many android phones have also followed Apple down this path as well and no longer ship with headphone jacks.
Backwards compatibility with what? Charging cables? A watch doesn’t take video or photos, or store files. Fast transfer speeds for video is pretty important to most workflows, and wireless is not going to be able to keep up. The backwards compatibility doesn’t hold up when you consider that literally everything else has moved onto the USB-C standard, including their iPads and MacBooks.
Edit: if they were really concerned, they’d make a USB-c male to lightening female adapter. Problem solved.
The drawers full of Lightning cables iPhone users already have.
100%. Plus all the various lightning devices out there in the world. I think @ngp’s definition of backwards compatibility and ours are quite different.
@ngp My perspective is, they consider wires stupid. They have waged war(and won) when it comes to wired headsets. They haven’t quite started the war on charging/sync cables, but they are working on it. I imagine they didn’t expect it to take quite so long, as I agree Lightning is looking a bit long in the tooth now, but it would be idiotic of them to switch to USB-C for a few years while they finish off their cables are terrible war.
USB-C port is still far more fragile than the lighting port. It’s easier to replace a lighting cable than to take apart an iPhone and desolder a USB-C port and replace it because the little pins in the middle have been damaged.
This a million times! The lighting connector is pretty much bullet proof.
It definitely hasn’t been in my IPhones. Earlier this week, I woke up next to a phone that hadn’t been charged despite being plugged in all night.
Sounds like you need to clean the port or replace the cable. The only times I’ve had a connection issue have been when there’s been fluff in the port or the cable has a discoloured pin and will only connect the other way around. They don’t seem to be fixable when that happens but I don’t know if I’m missing a technique that works.
Yup,
ascii(7)manual page is very useful for this type of info. Also if one needs to %-encode a character, i.e. in a URI, etc.I would rather see better tools than PGP for new standards.
If you’re talking about GnuPG, then absolutely. Why can’t we have something simple like signify, eh? If you’re talking about OpenPGP then, well, even with its issues, a suitable replacement would still needs its own RFC first :^)
Yes, makes sense.
Yeah, Signify would probably be much better.
Or reop, but you get the gist ;^)
I’m surprised reop hasn’t caught on like signify has (first time I’m hearing of it). Seems like a great tool.
An RFC with no comparison against VuXML and which looks less useful. Yay?
Would VulnXML be comparable to OSV? https://ossf.github.io/osv-schema/
Yes, it looks as if OSV could be fairly easily translated to VuXML and vice versa. They seem to capture the same information in an almost identical schema, just with different serialisation formats.
It looks like it comes from an era (2003) when XML was quite fresh and cool(?). Is anyone apart from FreeBSD using it? It seems like if it’s never mentioned in duscussions about security.txt, then it’s mostl likely due to eveyone involved in VuXML either not being interested any more or asleep.
Human-readable is the new shit, next will be binary ;^)
I don’t know. I think NetBSD was, not sure if they still do.
It looks as if I was misunderstanding the purpose of security.txt based on the title. It is about defining a way of reporting security vulnerabilities to the project, not a way for a project to report security vulnerabilities. The only consumer of this will be a human security researcher who has found a vulnerability. There is some value in having a convention here, but any text file is fine as long as it’s easy to find. I don’t care what the structure of the file is because a human will parse it and it will be a small part of the task of finding and documenting a vulnerability.
VuXML solves the other part of the problem. Every security vulnerability in a package shipped by FreeBSD gets an entry in the VuXML stream and it’s machine-parseable and easy to aggregate. It looks as if security.txt is designed to be machine-parseable (and therefore probably possible to aggregate) but it requires a bespoke parser. I’d love to see a VuJSON, since JSON parsers are simpler and more ubiquitous than XML these days.
The main value for this kind of thing is in auditing. On a FreeBSD system, I can type
pkg auditand get a report of all packages with known vulnerabilities, generated from the VuXML. I believe Debian has something similar, though I don’t know anything about their implementation details. I can also build my own auditing tool and can easily produce a VuXML stream for my own package repositories that integrates with this.It would be great if there were tooling to allow upstream projects to more easily publish their CVEs in machine-readable format that could be converted to VuXML. There’s a small ontology problem (VuXML tells you the range of versions for packages that are vulnerable but the versions of upstrea, of the FreeBSD packages, of the Debian packages, and so on don’t always align) but that’s something that could be solved with a bit of metadata in the packages allowing some tooling to handle the mapping.
CDDL? An odd choice of a license for a new project. Is this code related/based on Sun’s old code in any way?
No, it’s not. But I can’t see a reason to use a different license.
Is GPL incompatibility a goal? If so, then CDDL is fine. Otherwise MPL may be a better choice?
I honestly don’t care about being compatible with the GPL. The Lazarus components I use are “LGPL with linking exceptions” as far as I know, my code itself was not designed to be embedded in any other software, so the difference is mostly academic here, if I’m not mistaken.
I mean, the CDDL is effectively “MPL + GPL incompatibility” so if you don’t care about GPL one way or the other using MPL would mean anyone who finds something useful in your code could copy it to a GPL project.
It’s all academic until it’s not, and by then it’s usually too late to change :)
One of the advantages of being the project lead, main developer and license steward of a project is that it’s never too late to change.
I won’t block a license discussion once this happens. Until then, the CDDL is just fine. :-) (I have my own prejudices against the GPL though, so the discussion will - at least - be fruitful.)
Given that you’ve mentioned a basic
vi(1)command as your favourite, I’m going to do the same:It’s a repeat the last command, at least in nvi :^)
In terms of
:r!...I use it daily, i.e.:This looks interesting. On a related note, if you want something closer to vi, but the lack of UTF-8 and bidirectional text in OpenVi is a problem, take a look at neatvi.
I really enjoy everything the author of neatvi has written (neatroff especially). I reached out to him once via email basically to tell him I was a fan. He was very gracious.
Agreed. When neatvi was relatively new, I submitted a small number of patches and had several questions. He was always helpful.
For UTF-8, another option is nvi. OpenBSD’s vi is actually an old version of nvi that lacks UTF-8 support.
Don’t confuse OpenVi/OpenBSD-vi, nvi1, and nvi2. These are all different programs that share the same heritage.
OpenVi is derived from OpenBSD vi, which derives from nvi version 1.79, released in 1996. There has been 25+ years of independent development as part of the OpenBSD base system and it has diverged greatly in that time, with the development going in a different direction.
Nvi1, currently on version 1.8x, is maintained at https://repo.or.cz/nvi.git - I believe the latest version of this editor does have multibyte support, but this is not the OpenVi/OpenBSD version of the editor.
Nvi2 shares the same heritage as well, but is also quite far removed from 1996 code. It is actively maintained at https://github.com/lichray/nvi2 and also includes multibyte support.
(If I remember correctly) the multibyte support in both Nvi1 and Nvi2 derives from nvi-m17n, developed as part of the KAME project by the late itojun - http://www.itojun.org/itojun.html … the last update to nvi-m17n was about 3 years ago, and is available at https://cgit.freebsd.org/ports/tree/editors/nvi-m17n/files
Currently, optimizing for size using link-time garbage collection with GCC 11.2 on an x86_64 glibc Linux system gives a good idea of the changes over time and the different direction these editors have taken. OpenVi is also simplified in structure and does not have the three levels of abstraction of Nvi 1.8x - there is no library interface layer.
For OpenVi, the compiled binary is 278K, and for Nvi1 (nvi-1.81.6-45-g864873d3) the compiled binary is 528K (36K for vi, 528K for libvi).
OpenVi has a single configuration standard with no dependencies beyond curses.
Nvi1 has many options beyond trace/debug (“widechar” “gtk” “motif” “threads” “perl” “tcl” “db3/4” “internal-re”) - so at least 255 different build variations are possible.
(I’ve not yet built Nvi2 myself on Linux so I can provide an actually fair comparison yet, but I will, and I’ll summarize the data in an FAQ section of the README)
(Note that I was using the defaults here, I’m sure that it’s possible to trim down Nvi 1.8x further, but I’m comparing the default compilations, optimized for size (GCC, -Os, -fdata-sections, -ffunction-sections, link-time GC enabled), but Nvi 1.8x is a much more complicated program, and has a different feature set, and different supported options.
Well, I allowed myself to omit the fact that OpenBSD’s vi has seen some independent development past nvi 1.79, which is true. A “(based on)” should be inserted before “an old version” in my original comment. But I appreciate the thorough summary of nvi versions!
Nope, the vi in OpenBSD is nvi - you’re confusing it with nvi2. Both are in active development: nvi and nvi2.
It should be noted that DragonFly BSD has imported nvi2, but with some modifications as well.
It’s unfortunate there is so much confusion surrounding the various nvi-based editors, mostly due to them all being so similarly named.
Part of why I chose to call this project OpenVi was because the name was - suprisingly - available, and does not directly imply that OpenVi is exactly Nvi1/2 or OpenBSD’s vi.
(In particular, all bugs in OpenVi should be considered my fault.)
I will confirm that
Neatviis an excellent project, but I’m a bit more interested inNextvi- https://github.com/kyx0r/nextvi - the RTL/bidi inNeatviis a huge strength and is done very cleanly when compared to othervi-likesAutomounters existed since the 80s but sure, let’s just reinvent the wheel… hang on a minute it’s not round any more - it’s square!
yawn systemd bashing, how boring, and how expected
anyway, this is a typical strawman response.
automounting is not a novel concept… but noone claimed it is. the post shows how systemd nicely integrates this concept with other systemd concepts so that, for example, it becomes easy to start services that depend on such a network mount, ensuring the right ordering during boot, etc.
My comment wasn’t systemd-specific - it was aimed at any solution in need of a problem - my point was that automounters have existed for well over three decades and they do well what they’re good at.
Also, unless I’m missing something, the article describes automating an
fstab(5)mount - it isn’t a real automount as in, mount on request/access and unmount if not in use, not to mention other features such us various substitutions (key, wildcard, variable, etc.), etc.None of the auto mounters I know of integrated with system service ordering and dependencies very well. Also systemd already is the place where fstab handling happens, so it effectively needs to be an (auto)mounter anyway. I don’t think reinventing the wheel criticism really applies here.
I have moved from autofs to using the systemd built-in feature in the cases where we are automounting. The advantage is that systemd is already installed, so an additional package is not needed any more, it uses the same syntax for defining mounts as we’re already used to for services and service startup order can be nicely integrated into the auto mount availability.
This as done away with quite a few
sleephacks in old style scripts and so far worked perfectly and did not necessitate new hacks.Do I need my init system to have built-in automount support? No. But it’s very convenient and very robust, so I’m more than happy to use it.
If you are concerned by bloat or unhappy with the functionality provided by systemd, feel free to continue using autofs or anything else for your mounts.
The one thing I wish was different is if I could have the mount and automount unit in a single file. systemd is very boilerplaty that way and while I see that in some cases the split makes sense, in my simple use cases, it’s just baggage
I’m not the biggest fan of systemd… But I do think your comment isn’t very constructive nor a good criticism of this feature of systemd.
What is this site about exactly ? I miss the point ^^”
It’s like an interactive telephone book, you can index all of the users of the domain with “finger @plan.cat” and you can look up for a sepecific user like “finger [email protected]”.
It would be awesome if mail providers started to provide finger so you can quickly have information about someone (which would be, of course, the information the want to make public)
Most servers started to close the finger port for incoming connections in the late ’90s because the protocol was a great way of enumerating the valid accounts on the system. If your mail provider enables it then you can find all of the addresses that will work and that makes sending spam to that provider a lot easier.
I first saw
fingerin 2000 and even then it only worked on the local network and was blocked at the firewall for the machines that hosted a web server / email.I have writing PIM in my “TODO one day”, and it would be nice feature to add.
It’s a social network from way back when: https://linux.die.net/man/1/finger
https://man.openbsd.org/finger.1
;^)
Back in Days of Yore, before the internet went mainstream and security Got Serious, most UNIX systems supported a protocol called finger.
You could say finger [email protected] and, if I updated my .plan file, see what I had written there and, depending on the server, maybe even what I was running on the machine at the moment.
People took advantage of this for all kinds of strange and wonderful things, including internet connected coffee and soda machines where you could [finger them for status].
This site resurrects the protocol but gives you a place to advertise your status without opening up a security hole in workstations you actually use/care about, and in its own way creates a kind of social network :)
Were you going to link something at [finger them for status]?
Can we get integration with the weekly “what are you doing this week?” threads? That would be cool.
It would also be neat if lobste.rs hosted a finger server. For example
finger [email protected]could return some of the information found on https://lobste.rs/u/fs111. Maybe users profiles also have a “plan” section for “what are you doing this week” answers? Not sure the utility of all this, but the idea tickles me!Well, there’s this at least:
That would be really cool indeed
While this may seem nostalgic for some folks, I was entirely unaware of this feature[1] and am excited to see how it unfolds. So far it seems to just be a landrush for short names.
[1] https://linux.die.net/man/1/finger (Search for “plan”)
Already linked below (above?) but thought will link it here, too - if nothing else, this one is more up-to-date :^)
https://man.openbsd.org/finger.1
I gues it’s better to leave on your own terms than to get your domain blocked or get kicked out.
The wording on the banner is far from being a friendly advice - I’d call it antagonistic and confrontational, hostile even.
BTW, the code itself has been added last year in this commit.
Ironically, lobste.rs was created by /u/jcs as response to HN heavy-handed moderation.
His engagement with lobste.rs was much more polarising than burntsushi. The latter didn’t jump into comment sections to deliberately kick off a flame war that may not have otherwise occurred; the former did so deliberately and unashamedly. I heartily respect both their views but I can understand why they might be moderated differently.
Thank you for saying this in a far more polite way than I was about to.
And why would that result in banning the domain? Drew wasn’t even the one posting his blog posts here and they were always upvoted.
Because many of his posts were explicit flamebait; look at the last two posts on that domain for instance.
Then clearly this community is not what the admin intended it to be before banning this domain because the stories from that domain were routinely getting above 30 points which is rare for most stories. It is time to shut this whole website down and just change it to be a private RSS feed of the admin.
It’s an attempt to avoid the Repugnant Conclusion; the mere addition of a steady attractor of upvotes can degrade the quality of life for everybody else.
Did you mean to include the one about a finger server and io_uring as one of the two? I found it interesting and informative.
I meant what was submitted to Lobsters, which were the final straws,
Thanks for the clarification. Not sure why I didn’t read it that way.
This was just an example - there’s more in the moderation log if you care to look.
Wow, this ban message from your second link:
I really hope that this happened at the end of a process of attempting to politely engage, rather than as the immediate response. That reads like something from a burned-out moderator who needs to take a break.
This was a sustained pattern of behavior over months.
Pro tip: moderators are always burnt-out.
oh wow, Drew got banned ..
I don’t like anyone getting banned for anything. I have a lot of respect for how much DeVault puts into his open source contributions and am envious he can live off of it. That being said, he banned me on Mastodon forever ago because I reposted an open letter a professor made during the eight of the 2020 US riots. We had a discussion over DMs and he blocked me in the end.
The more I lean about some of the stuff he’s said and done, I realize I can still respect his work while still agreeing with all the others who’ve come to the conclusion his actions are often inflammatory or childish. I’m not surprised he’s banned. He left the Fediverse a few months back too.
Yup. I was actually pretty interested in Sourcehut, but in the end I didn’t really want to use a service run by someone that hot-headed.
What was the nature of the letter?
https://www.youtube.com/watch?v=1nCtWHLfbqk
There are two issues here:
The reason for banning the user account was reported by the admin as apparently rude comments/encouraging arguments/arguing? The comments were usually upvoted though as far as I remember so I think the decision was mostly arbitrary.
The domain was blocked just because the admin banned the author from lobsters, not because there was something wrong with the content on that website. Drew wasn’t even the one posting his blog posts here.
Therefore at least one of those decisions is nonsensical.
You can try to create a website with semi-transparent moderation policies but that will never fix the standard power abuse by moderators like in this situation. The personal grievances usually win and no moderation log will fix this. The community enjoyed the content and @pushcx didn’t => the comments and the domain get nuked off the website.
I tried to get an answer at least to why the domain was banned but of course I never did (in the name of transparency).
I disagree with your opinion that his behavior on the site was not rude, though I didn’t look closely at all of his posts so I can’t say for certain. What I do agree with is the domain ban. The ban itself seemed unclear and arbitrary. Moreover, as you mentioned, a domain ban affects much more than just a user, it affects all content on that domain.
Negative comments are deleted when users are banned or leave; you won’t find any of his egregious comments here.
For my sins I’m tracking every submission to lobste.rs.
Here’s a gist with an extract of submissions matching ‘drewdevault’ in the URL. I consider a comments/score ration above 1.25 “controversial”.
Hopefully this can give a sampling of how Devault’s content was received by the community here.
Running OpenBSD on an RPI3 is much easier than it seems, only non-standard RPI requirement is doing an actual install from the SD card and requiring a serial terminal our external monitor/keyboard instead of just flashing an image and booting.
One trick I ended up doing post-install was mounting /tmp as type mfs to avoid writes to the SD card when possible.
It’s overall stable and there are a good number of arm64 pkgs to install and setup smaller network appliances like a dnscrypt-proxy or a gemini capsule.
s/terminal/console/