What's the font? It looks goooood.
What's the font? It looks goooood.
The C compiler or third party libraries can provide support for parallel execution and SIMD. That article is just used by people in an attempt to argue that C's strength in being a good low level abstraction is false, which it isn't. C is the best portable abstraction over a generic CPU that I know of. If you start adding parallel features and SIMD like the article suggest, you'll end up with something that's not a portable low level abstraction. To be portable those featues would have to be implemented in slow fake variants for platforms that doesn't support it. We can always argue where to draw the line, but I think C nailed it pretty good on what to include in the language and what to leave up to extensions and libaries.
C is not a perfect abstraction, because it is portable. Non portable features for specific architectures are accessed through libraries or compiler extensions and many compilers even include memory safe features. It's a big advantage though to know Assembly for your target platform when developing in C, such that you become aware fx. that x86 actually detects integer overflow and sets an overflow flag, even though that's not directly accessible from C. Compilers often implement extensions for such features, but you can yourself extend C with small functions for architecture specific features using Assembly.
It sounds like you already know how to make Web 1.0 websites.
Just do it. It's your computer.
Fontunately it's just DNS.
Loop up the domains at one of: ns1.cloudns.net ns2.cloudns.net ns3.cloudns.net ns4.cloudns.net
Just to clarify. The gi://
resources are GObject Introspection modules which are used for multilanguage bindings to native libraries. On my system, GI modules are found in /usr/share/gir-1.0/
. They're just imported by name and sometimes version using gi://
(there are examples in the link in my first comment).
As I don't have Gnome installed I can't be sure of the path to gnome shell modules imported using resource://
, but it's probably the path I wrote, but without js/
.
It is very likely the wrong path, I just extrapolated the path from the gnome-shell git repo. I don't use Gnome myself, I'm on the enemy team using LXDE on Devuan ;)
I edited my comment with an example for your code and my best advice for figuring out the path of gnome shell imports is by browsing /usr/share/gnome-shell/js/
, the docs are not very helpful.
GNOME Shell 45 moved to ESM (ECMAScript modules). That means you MUST use the standard import declaration instead of relying on the previous imports.* approach.
https://gjs.guide/extensions/upgrading/gnome-shell-45.html
So the imports in your extensions is changed from:
const Clutter = imports.gi.Clutter;
const Gio = imports.gi.Gio;
const Main = imports.ui.main;
const Volume = imports.ui.status.volume;
to
import Clutter from 'gi://Clutter';
import Gio from 'gi://Gio';
import * as Main from 'resource:///org/gnome/shell/ui/main.js'
import * as Volume from 'resource:///org/gnome/shell/ui/status/volume.js';
You want Gobby
Aliasing and forwarding is not a good solution if you are concerned about law enforcement, because your personal e-mail is still linked with the tracker, just behind an extra hop and in addition you allow someone in between to read your e-mails. You had the answer yourself. Create a completely fresh free e-mail account somewhere, using as minimum a private tab to prevent tracking data to link anything to the account.. and if you can get a free e-mail account with IMAP/POP access so that you can use it in an e-mail client to leak less data, do that.
That's the funniest thing I've heard in a -1 years!
Or you could pick up an iron rod and strike a firehydrant like MacGyver.
I build a lot of tools like that and the first thing I do is to go to the developer tool in my browser and observe the network traffic. When you find the resource you're after you scroll back and see what requests resulted in that URL. Going from those requests you figure out in the original static HTML document and resource, which parameters are used for the construction of the URL, that might require reversing some javascript, but that's rare. After that you'll have a pretty good idea how you obtain the video resource from the original URL. Beware of cookie set by the requests, they might be needed to access the next requests. For building my tools I use Perl or sometimes just Bash or a GreaseMonkey userscript to fetch and parse the urls and construct the desired output.
Nice, but it is not entirely without JS. There is a tracking script from scorecardresearch.com