This seems like an install/setup guide for an alternate package manager that installs an almost normal webserver?
I don't really get what yunohost is supposed to be providing AFA simplifying the experience, given it is apparently not it's own bootable image of a distribution.
I think most existing distributions have a webserver that comes up and serves a directory in /var and they don't serve any PHP. Unless you know php or want to do click and pray with wordpress, I would consider no PHP/etc and no enabled modules the right config to start a home blog.
As such, I think this is really too advanced for the stated audience and more of a description of a possible later option.
I think the little Arm boards are good enough now for surfing, etc.. But for a desktop with lots of RAM and cores an AMD Ryzen would be good.
The only use I really have for a lot of cores is compiling the software I am using on the machine, which seems like circular reasoning for consumption, particularly since browsers and such things with long compile times are things I least want to contribute to.
I find this article a bit disappointing compare to earlier ones from the same blog.
To summarize my dislike, I find the premise that:
1. Trying to get free as in beer CPanel style service while using Tor for your own privacy and wanting family to accept unsigned certificates as a sign of trust in you. The innapropriate trust is in a hosting company with an unclear business model which can include relying on grey areas to sell MITM access to a 3rd party for injection of spyware downloads.
I find this markedly worse than the pre-existing standard:
2. Forcing friends and family to accept your preferred large provider for file sharing or photos that is probably giving you several gb for free and has some reputation to maintain for their freemium upsell.
I would have preferred:
3. Using classic shell access ~/public_html from some small UNIX community or other non commercial site.
4. Using more unusual setups to introduce friends and family to p2p networks, filesystems and similar.
"Stockdale had no reason to think that the day’s mission was to be anything unique.
The flight in September 1965 was part of his third combat tour of North Vietnam, serving as Wing Commander of the aircraft carrier Oriskany. Despite his misgivings about the purpose of him being in Vietnam, he was a competent and skilled career fighter pilot. Nothing suggested he shouldn’t expect to make it back home that day - let alone that decade.
But sometimes life deals you a lousy hand, and it dealt Stockdale quite an unhappy one.
While trying to aid trapped American soldiers on the ground, he was suddenly falling out of the sky and hurtling towards a small Vietnamese village. His plane was on fire, the control system shot out by North Vietnamese who had used the grounded soldiers as bait, and he didn’t have much choice beyond punching out of the plane."
Good stuff, I also find Arch Linux's documentation fun and absorbing (and quite often a sufficient overview when looking into configuration) even though I've never really used Arch.
One thing I find interesting is older/slower recycled hardware and configuring/compiling everything yourself hit the same kind of yankee conservativism for me, but don't work so well together unless you go to pretty extreme minimalism, such as never using the large evergreen browsers (which can take a week to build on older hardware) or fancy compilers.
In the distant past, I used gentoo and treated a constant build cycle as its own sort of meditation. More recently, I moved to nixos and accepting it's defaults builds (and therefore cached builds) as a sort of bug oriented version of Occam's razor. The least changed system is the least likely to exhibit an unreported problem.. But it is hard to resist the pull of testing builds which brings in the draw of the best tools which is sadly still the newest instead of quality tools that last in a more traditional trade.
I generally like the technology and cs-related submissions, as well as the occasional mathematical or philosophical article. Not sure that I'm keen on the "fighting" articles that I'm seeing on the list. Those don't really match what I thought this site was for.
On the netbook theme, it was originally Microsoft that used licensing to limit the amount of RAM they could ship with (1gb?) and support(2gb). This made it impractical to sell anything in the low end on screen size, etc, but above their limit on RAM. It was already impractical to sell anything but windows unless you sold no Windows or AMD if you sold any Intel.. So Microsoft/Intel licensing and illegal behaviors kept a gap in every vendors product line between terrible and medium range for as long as they could.
I think in the next phase, the factor was Intel, older Celerons support more RAM, but Intel realized cpu constraints were no longer as significant as memory constraints, so maxing out RAM on an economy system was outperforming their middle range.
The vendors themselves are IMO far too disorganized to be behind these factors, the death of the desktop/pc is largely about consumers avoiding the results of tactics organized by Intel and Microsoft to maximize their own slices that the vendors got no piece of. The only real exception is clutterware, but even that was probably tolerated and maybe encouraged by Microsoft. They had an interest in obfuscating sources of clean media aside from paying them directly at the time and it also let them claim vendors had sources of income to seek out and later to redirect blame.
My perspective is that the volume is low enough that one reposter or even one blogger greatly influences the average direction of the site.
In that sense, I think someone going in a niche direction with posts could give a niche that interests them (and is not the main perspective of some larger site) a try on this site and have a slight headstart on bringing that niche to the larger sites..
The opposite direction for this site, would be if everything on HN were reposted here or with equal chance.. Then the site/community has no specific direction of its own, and why make comments here that could be made in the larger community with the same general focus?
The question was intended as "what should I be looking to post", since very, very few of my posts seem to get any responses. But with your list of things you're interested in, it seemed clear that very little of it turns up here.
There's very little traffic, and I'm wondering what the few people here are interested in. The lack of traffic is ... troubling. I'm not finding much of interest, and I'm thinking about giving up, but unwilling to do so without giving it a "proper go".
Tough to say, I kind of like what shows up here about half the time, which is a higher percentage than other sites but still an article every few weeks?
I'd say things that don't fit on lobsters due to site policy and are a bit more eclectic than hackernews.. I.e. no commercial potential computing.. maybe some other STEM topics?
I'm interested in peripheraly following what's going on with guix, *bsds, gopher, suckless.org, etc, but not enough to seek out and evaluate summaries, blogs, etc. Similarly for topics like hobby languages and compilers, embedded, etc.
Hey everyone! For anyone wondering what is this tool and why we need it..
I'd like to wind back couple of weeks ago when I was looking for battery monitoring/analyzing tool and was shocked to find that there existed no such tool on the market, so I decided to build one for myself!
Powir is a tool designed to help people evaluate their power and battery condition of their windows based systems. It achieves the goal by showcasing various metrics collected from the system and doing statistics to formulate an overall benchmark of your system.
Some of its features include:
- 100% portable app with no installations required: download and run! - Provides you with a simple and clean UI to list your battery and system information. - Shows you the trend in battery capacity as well estimate life since the OS was installed. - Ability to export all the data via various formats: PDF (app), JSON (processed), HTML (original report)
I was originally brought on in 2011 to bring the XanaduSpace 'prototype' written by Rob Smith up to releasable quality (after Ted came across coverage of my ZigZag-inspired operating system iX on hackaday).
XanaduSpace (or, at least the version we pieced together from chunks of various different versions -- the author didn't use revision control) was more of a demo & a POC than a prototype, and so salvaging it was more work than we expected (especially because we needed it to be cross-platform and needed to integrate a nice, responsive editor). We (myself and my buddy) ended up rewriting it entirely, and that became a different (never-released) project called XanaSpace.
Part of the XanaSpace rewrite was switching from OpenGL 1.1 to modern OpenGL -- necessary to make editing responsive, and necessary to fulfill certain demands about the amount of text we can display. But fulfilling the text quantity demands (we needed to support arbitrary unicode in arbitrary truetype fonts & be able to display the whole king james bible on screen at once) were tough, and my partner and I burnt out on it. We were working as volunteers anyhow, so we sort of skated along for a few years.
I worked a little bit on the web-based OpenXanadu, released in 2014 (wrote the code to display the little 'X' logo during loading, and also wrote a substantial amount of code to support a caching proxy that we never ended up releasing & an entire editor we also didn't end up releasing), though the current web-based version on the xanadu site (called XuCambridge, formerly XanaBurger) I didn't have any connection to. I'm still occasionally consulted on ZigZag.
Ultimately, the biggest impact of my tenure on Xanadu (aside from being able to brag about attending Ted Nelson's wedding) has been my work with documentation. Both official and internal Xanadu documentation has been a bit hard to make sense of for newcomers: Ted has a carnival-barker sensibility when it comes to style, a love of puns and neologisms that would put Pynchon to shame, extremely severe ADHD, and hasn't written a line of code since the 60s (though he has a deep intuitive understanding of data structures and their performance), so 'documentation' is mostly Ted making up new words and pontificating about how cool his ideas are -- a real shame because his ideas really are good, if you can figure out what they are. So, with his blessing (if not his oversight), I wrote an introduction to Xanadu internals aimed at software engineers not acquainted with the project: https://medium.com/@enkiv2/an-engineers-guide-to-the-docuverse-d080cdbb73a6?source=friends_link&...
By day I work as a software engineer for a heartless global corporation. By night I shitpost about hypertext and leftist politics. For a little while I worked on Project Xanadu, and I write freelance on medium (and for publications like Tedium) as a side hustle. Every november I participate in NaNoGenMo, a 'contest' for writing programs that write novels. I have released nearly 50 albums worth of experimental electronica under the name 'Infocalypse', and published two essay collections. I've been on this site for a few years, but I rarely post.