Notices by m0xEE (m0xee@breloma.m0xee.net), page 19

m0xEE (m0xee@breloma.m0xee.net)'s status on Tuesday, 03-Oct-2023 20:58:16 JST m0xEE
in reply to
@pyrate
Plan 9 wasn't always plain C, it originally used a language called Alef: https://en.wikipedia.org/wiki/Alef_(programming_language)
But they have dropped it sometime along the way. Its concurrency model got reimplemented as C library. And other ideas probably later became the foundation of Go.
@Zerglingman @p @MK2boogaloo @sysrq
In conversation about a year ago from breloma.m0xee.net permalink
Attachments
1. Alef (programming language)
  
  Alef is a discontinued concurrent programming language, designed as part of the Plan 9 operating system by Phil Winterbottom of Bell Labs. It implemented the channel-based concurrency model of Newsqueak in a compiled, C-like language. History Alef appeared in the first and second editions of Plan 9, but was abandoned during development of the third edition. Rob Pike later explained Alef's demise by pointing to its lack of automatic memory management, despite Pike's and other people's urging Winterbottom to add garbage collection to the language; also, in a February 2000 slideshow, Pike noted: "…although Alef was a fruitful language, it proved too difficult to maintain a variant language across multiple architectures, so we took what we learned from it and built the thread library for C."Alef was superseded by two programming environments. The Limbo programming language can be considered a direct successor of Alef and is the most commonly used language in the Inferno operating system. The Alef concurrency model was replicated in the third edition of Plan 9 in the form of the libthread library, which makes some of Alef...
m0xEE (m0xee@breloma.m0xee.net)'s status on Tuesday, 03-Oct-2023 20:40:22 JST m0xEE
in reply to
@pyrate
No, it's just these are the core ideas behind Inferno: https://en.wikipedia.org/wiki/Inferno_(operating_system)
It's supposed to be highly distributed, everything is running in a VM, so you could run it using any other OS as host. So it has a lot to do with JIT.
And being developed right after Plan9, it could be considered Plan10.
Most of the interesting ideas have been reimplemented/ported back into P9 though.
@Zerglingman @p @MK2boogaloo @sysrq
In conversation about a year ago from breloma.m0xee.net permalink
Attachments
1. Inferno (operating system)
  
  Inferno is a distributed operating system started at Bell Labs and now developed and maintained by Vita Nuova Holdings as free software under the MIT License. Inferno was based on the experience gained with Plan 9 from Bell Labs, and the further research of Bell Labs into operating systems, languages, on-the-fly compilers, graphics, security, networking and portability. The name of the operating system, many of its associated programs, and that of the current company, were inspired by Dante Alighieri's Divine Comedy. In Italian, Inferno means "hell", of which there are nine circles in Dante's Divine Comedy. Design principles Inferno was created in 1995 by members of Bell Labs' Computer Science Research division to bring ideas derived from their previous operating system, Plan 9 from Bell Labs, to a wider range of devices and networks. Inferno is a distributed operating system based on three basic principles: Resources as files: all resources are represented as files within a hierarchical file system Namespaces: a program's view of the network is a single, coherent namespace that...
m0xEE (m0xee@breloma.m0xee.net)'s status on Tuesday, 03-Oct-2023 20:19:02 JST m0xEE
in reply to
@pyrate
That would be Inferno 🤔
@Zerglingman @p @MK2boogaloo @sysrq

In conversation about a year ago from breloma.m0xee.net permalink
m0xEE (m0xee@breloma.m0xee.net)'s status on Tuesday, 03-Oct-2023 17:35:45 JST m0xEE
in reply to
@menherahair @dcc @kirby
> x1050
Is this real "standardized" resolution or some joke you came up with? I mean why not make it at least "Full HD" just to avoid scaling? It's 30 pixels away from 1080 :marseylaughwith:

In conversation about a year ago from breloma.m0xee.net permalink
m0xEE (m0xee@breloma.m0xee.net)'s status on Tuesday, 03-Oct-2023 17:23:17 JST m0xEE
in reply to
- † top dog :pedomustdie:
- this ad CAN be blocked, bitch
@kirby @dcc
Why the fuck do you have to scroll down? You know that timeline selector is collapsible, right?
In conversation about a year ago from breloma.m0xee.net permalink
Attachments
1. Screenshot of Pleroma FE's two column view with timeline selector collapsed.
  https://M.Breloma.m0xEE.Net/media/1bd8bc06-8f94-4753-a7c1-77135815944e/N2XtnmwlRGJlcg.jpg
m0xEE (m0xee@breloma.m0xee.net)'s status on Tuesday, 03-Oct-2023 17:19:15 JST m0xEE
in reply to
- † top dog :pedomustdie:
- this ad CAN be blocked, bitch
@dcc @kirby
Completely agree. It's kinda useless, so much space wasted. And I hate having Firefox fullscreen in general.

In conversation about a year ago from breloma.m0xee.net permalink
m0xEE (m0xee@breloma.m0xee.net)'s status on Tuesday, 03-Oct-2023 17:16:42 JST m0xEE
in reply to
- this ad CAN be blocked, bitch
@kirby
It's weird even in medium-width windows, it's only okay with a very narrow window — the only way you can have both the notifications and home timeline full-width.

In conversation about a year ago from breloma.m0xee.net permalink
m0xEE (m0xee@breloma.m0xee.net)'s status on Tuesday, 03-Oct-2023 17:09:09 JST m0xEE
- 'ol Mitch
@olmitch
It's worse! Someone's trying to justify the use of systemd on Gemini!
gemini://aelspire.info/posts/2023-09-18-systemd/post.gmi
:marseyshock:
The world is about to end!

"I have other things to do with life other than tinkering with my computer" — what sick kind of argumentation is that? :marseyraging:

In conversation about a year ago from breloma.m0xee.net permalink
m0xEE (m0xee@breloma.m0xee.net)'s status on Monday, 02-Oct-2023 22:19:21 JST m0xEE
in reply to
@thatguyoverthere @iska @vaartis @jihadjimmy @meso
We can just ban cancer and fine those who have it — problem solved :marseysmug2:

In conversation about a year ago from social.076.moe permalink
m0xEE (m0xee@breloma.m0xee.net)'s status on Monday, 02-Oct-2023 19:45:46 JST m0xEE
in reply to
@p
Yeah, same here! Even in Firefox I have them disabled with image.webp.enabled=false, same for VP9 with media.mediasource.vp9.enabled and probably some other Google shit that I don't even remember of.
And there've been only a few cases when I cared enough to actually download the file, convert it manually and see what's in it. Most of the time I just ignore them :marseysmug2:
Problem is, I've been encountering these more and more often in the wild as of recent. I suspect, that one of the authors of some Fedi software like Firefish has decided that saving a few kilos is worth it and implemented an automatic conversion to WebP — I just can't imagine that a lot of people have decided to adopt it all of a sudden, especially with all those vulnerabilities discovered.
I remember when they did it in Nitter and I had to patch this shit out myself for my instance. Why people decide to adopt it is beyond me — like I said earlier, the advantage is negligible in absolute most cases, even if it's only a few lines of code, the added complexity is not worth it. And I don't even see a lot of interest from developers TBH, there a just a few people, who run around submitting these patches and devs usually just go with it because: "Why not? Looks good on paper!"
Anyway, I should probably start a media proxy or something, that would do the conversion for me. Or maybe I should just keep ignoring WebP images — haven't decided yet :marseylaughwith:
@kirby @sysrq @lispi314

In conversation about a year ago from breloma.m0xee.net permalink
m0xEE (m0xee@breloma.m0xee.net)'s status on Monday, 02-Oct-2023 14:57:17 JST m0xEE
in reply to
@lispi314
I think C has little to do with it, the biggest problem is that while it's being considered "an open standard" by many, it's not that — there is only one major implementation and it's Google's own implementation, others have little to no interest contributing to it as it will remain Google's implementation in any case.
So having sole implementation that is used, in addition to obviously very popular Chrome itself, it's used by a lot of software. If that software has anything even remotely to do with images — why don't we add WebP support, right? So in addition to all the browsers, this shit is now everywhere.
Why the fuck down ffmpeg in my system depends of libwebp? I don't know. Does anyone of you use WebP for any other purposes except for posting it on the Web? I don't and I doubt that anyone does — it's advantages over existing formats is negligible for personal use, but it still makes sense for Google as they serve petabytes of data and even 10% makes a huge difference.
I might have digressed, but anyway — as it is used in software that is present virtually in every system and in addition to that, it's the same implementation, it makes libwebp a very attractive target for attacks. Monoculture is never good. These sole implementtion is closely studied by those, who intend to exploit it — this is where C factor might come into play.
Another problem is that Google doesn't give a fuck about how and where their library is used. Because they only care about how it's being used in Chrome — Chrome offers some means of isolation, if one tab gets compromised, others are safe. And to me it looks like that is exactly what they think: "Oh, it's not that bad, it's isolated!" And that is true, and same is true for Android. But is it isolated in ImageMagic — no, it's not. And when this vulnerability has hit the news, that is exactly what one person came up with in comments on HackerNews: let's isolate/containerize it for ffmpeg and ImageMagic too. That's insane! Nowadays it's assumed that everything is isolated/containerized — but in reality it's not. And it shouldn't be!
@kirby @p @sysrq

In conversation about a year ago from breloma.m0xee.net permalink
m0xEE (m0xee@breloma.m0xee.net)'s status on Monday, 02-Oct-2023 01:13:50 JST m0xEE
in reply to
@xianc78 @astheroth @newt
Yeah, I only use the masto one. I use Proton for email and VPN.

In conversation about a year ago from breloma.m0xee.net permalink
m0xEE (m0xee@breloma.m0xee.net)'s status on Monday, 02-Oct-2023 00:58:19 JST m0xEE
@newt @astheroth @xianc78
I have free librem.one account and I've never given them my address — which would make more sense if they wanted to just collect that data.
Probably they are legally required for you to give them some billing address — for IRS and whatnots, I'm not sure how it works in the US :marseyshrug:

In conversation about a year ago from breloma.m0xee.net permalink
m0xEE (m0xee@breloma.m0xee.net)'s status on Sunday, 01-Oct-2023 19:46:45 JST m0xEE
- Disinformation Purveyor :verified_think:
@thatguyoverthere
I'm not a fan of chicken meat, I prefer beef or pork any day, but shouldn't it still be richer in protein?
Or is it about nuggets not being exactly chicken? :marseyhmm:

In conversation about a year ago from breloma.m0xee.net permalink
m0xEE (m0xee@breloma.m0xee.net)'s status on Sunday, 01-Oct-2023 19:46:26 JST m0xEE
in reply to
- Disinformation Purveyor :verified_think:
@thatguyoverthere
Peppa is at least cute, unlike these fellas :marseysmug3:

In conversation about a year ago from breloma.m0xee.net permalink
m0xEE (m0xee@breloma.m0xee.net)'s status on Sunday, 01-Oct-2023 15:45:31 JST m0xEE
in reply to
@lina @dcc @ceo_of_monoeye_dating @iska @p @MK2boogaloo
:marseyerasure:
I don't see half of your posts from my instance as is and I have to look them up if I see someone replying to you.
You're like a figment of imagination of my imaginary friends :marseyemojismilemouthtighteyes:

In conversation about a year ago from breloma.m0xee.net permalink
m0xEE (m0xee@breloma.m0xee.net)'s status on Sunday, 01-Oct-2023 10:44:52 JST m0xEE
in reply to
- :gura_sus: 1e+6 litres :flag_china:
- T man :sex: :puffgiga: :puffpowerroll: (epic music enjoyer)
@theorytoe @kilostere
VP8 isn't that far behind: https://www.cve.org/CVERecord?id=CVE-2023-5217
All Google shit is fucked!
In conversation about a year ago from breloma.m0xee.net permalink
Attachments
1. No result found on File_thumbnail lookup.
  
  cve-website
m0xEE (m0xee@breloma.m0xee.net)'s status on Sunday, 01-Oct-2023 09:59:51 JST m0xEE
in reply to
- pistolero :thispersondoesnotexist:
- † top dog :pedomustdie:
@p @dcc
Sure, but if overkill is what we're going for, we have to go all-in :marseylaughwith:

In conversation about a year ago from breloma.m0xee.net permalink
m0xEE (m0xee@breloma.m0xee.net)'s status on Sunday, 01-Oct-2023 07:44:36 JST m0xEE
in reply to
- pistolero :thispersondoesnotexist:
- † top dog :pedomustdie:
@dcc
> bash script that will monitor
How dare you! Go for Nagios or Zabbix straight away, and also setup up notifications so it sends you an email and even a short message to you cell phone when something happens. Remember not to use your carrier's API, use an old Siemens S45 phone with a spare SIM-cart to send out messages. You may of course also set up XMPP notifications if that's your kink — but that would be too easy IMO :marseyhacker:
@p

In conversation about a year ago from breloma.m0xee.net permalink
m0xEE (m0xee@breloma.m0xee.net)'s status on Sunday, 01-Oct-2023 07:29:11 JST m0xEE
in reply to
- pistolero :thispersondoesnotexist:
- † top dog :pedomustdie:
@p @dcc
But it's not something like load balancing, why even do this? Why not set up monitoring of main IP and when it goes down, do a dyndns update to the backup one? And yes, of course TTL should be low enough so it propagates quickly.
Hosting your own nameserver just for this is an overkill IMO :marseyshrug:

In conversation about a year ago from breloma.m0xee.net permalink

After
Before

Public

Notices by m0xEE (m0xee@breloma.m0xee.net), page 19

User actions

Following 0

Followers 0

Groups 0

Statistics

Feeds