-
I took me many years, but I’ve finally accepted the rule of three; I’ve burnt myself repeatedly on my poorly thought-out abstractions that support a single actual use case.
-
This is exactly how I work, and I went through a similar process to the article writer in coming to learn that premature abstraction fails for the same reasons premature optimisation does: before you have enough data to analyse (in the form of code that executes slowly or obvious refactoring candidates), you’re working blind, and it’s sheer luck if what you decided to optimise or abstract would’ve been a hot path or good model. Having only two similar things isn’t enough to predict what the “pivot points” of an abstraction over them and future things might be.
-
-
I don’t understand how/if webmentions are significantly different from the pingbacks everbody used to have on their WordPress blog (because I think they were enabled by default?) and then promptly disabled because of too much spam.
-
Webmentions have been modeled after pingback. They are basically a refinement.
Regarding spam, well, as always when you are exposing a write permission though the web, you are more or less vulnerable. This problem has and is still discussed within the indieweb community. A protocol, Vouch has been proposed to address this problem.
And as mentioned below, you still can moderate or simply not display your webmentions altogether.
-
-
Presumably? I mean, they got implemented, right? Someone spent the time to make that happen.
-
Did anyone ever care about pingbacks though? Even the non-spammy ones?
I can only speak for myself, but I did. It often gave me access to blogs by people with similar interests that I would have otherwise never known about to visit. It used to be that a large percentage of bloggers would list their favourite blogs somewhere on every page (sidebar/footer) so finding one blog with an author who shared similar interests could end up in a twenty five link binge.
I guess it was a different time, then again it was over a decade ago.
-
-
-
I was wondering that, unless these aren’t intended to be published in verbose and instead used more as a notification for the author and only really published publicly as a counter?
If the pingbacks had been used simply to list in the authors admin places where their articles had been mentioned and not published alongside comments to the article then there would have been a lot less spam.
-
-
-
Because I must’ve missed it if it was linked at all in the blog text, a link to the source for the GLB “director”: https://github.com/github/glb-director
-
-
kivikakk
19 days ago
|
link
| on:
What do non-Emacs users use to navigate the commit history of git?
I love magit, but trying to use
magit-log-*on a repository with more than half a million commits reeeeeeally drags on, so it’s magit for reasonable repos and plaingit log --show-notes=* --abbrev-commit --pretty=format:'%Cred%h %Cgreen(%aD)%Creset -%C(bold red)%d%Creset %s %C(bold blue)<%an>%Creset'(aliased) for monorepos.
-
For folks like me who’ve been running the experimental Metal renderer for a while, I think this is the same one.
-
-
While I got the context that this is about GNOME, I’m not really sure what the author is talking about. Are their guidelines very complicated that make icons look terrible? How does that affect blender or other apps in screenshots? And how does detail become harmful there?
-
-
Isn’t it great to be able to open a chat conversation with your virtual machine and say things like “How are you today?” or “Hey, please reboot”?
I have to admit, this sentence is extremely uncompelling.
-
-
The underlying factor that caused the github purchase to be a problem was that github was free. As long as the service is free, then selling out is always a risk.
Why not take the total server costs at the end of the month, divide by the number of users, and charge that as a monthly subscription to keep the lights on? If the system is even marginally profitable, that makes any kind of selling out (via acquisition or selling user data) less attractive.
If the system is costing the administrators money, then they have a high incentive to sell out.
-
Why not take the total server costs at the end of the month, divide by the number of users, and charge that as a monthly subscription to keep the lights on?
Nah, charge them based on use like in mainframe and cloud models. That’s more fair. Safer, too, for the host. There probably should be a baseline fee that covers administrative overhead or at least contributes something to it. The usage charges go on top of that. There could be some usage that comes with the baseline fee, though.
-
That’s an interesting point, and I’ll have to consider it. Though, I don’t see the user base growing enough to make selling out a possibility. My philosophy is that there should be many services like this one to prevent any one from growing too large and making selling out a possibility (that’s why the goal is to make everything open source - if someone wants to clone Asymptote they have my blessing).
-
-
-
True. In that circumstance I would run a cheap ($2.50/mo) VPS to keep essential services running (such as email) while fundraising.
-
-
-
-
-
Asymptote’s existance isn’t because of fear of what Microsoft might do to GitHub. I made it to test out a midpoint between large, centralized services and everybody self-hosting. I don’t think Microsoft will screw up GitHub, it’s just that the discussion around the purchase prompted this idea.
-
-
-
We can just make sure that the admins publish inappropriate stuff like ‘women are weaker then men’ or ‘women make less money because they make different choices compared to men’ on its blog every month. Then the site would be ‘unbuyable’ because of the outvogue apparent social position of the owners. The people in the know would know to ignore such posts, but the bad-headline potential of these blogs would poison the site against any future buyouts.
-
This is a rather sarcastic way of making a reasonable point - what sorts of rules about host content will Asymptote Club (or other similar “middle-ground” services) enforce, and how resistant will it be to social/political pressure to censor content? What if I want to use Asymptote Club’s gitea/CI service to actively develop machine-learning software that’s illegal in some jurisdictions but not others? What if I want to use their matrix service to host a misogynist chatroom because I believe that the accusations that the content of the chatroom actually constitutes misogyny are complete bullshit? If something hosted on Asymptote Club got into the news and invokes a social media shitstorm against it, how much can I trust that Asymptote Club will keep hosting it, and how much do I have to know about the personal politics of zebMcCorkle in order to ascertain that?
-
-
-
-
This link is more useful: https://blog.twitter.com/official/en_us/topics/company/2018/keeping-your-account-secure.html
By all accounts, Twitter did the right thing here. They’ve owned up to it are advising people to change their passwords. They seem pretty open about the whole thing so far. This looks like an “honest bug.”
@tptacek even agrees with Dan Kaminsky about it: https://twitter.com/tqbf/status/992202949018431491
-
I mean sure lets say it’s an honest bug. How was this even a possible bug?
-
lots of frameworks will go ahead and log the entire request params hash by default, and while many will automatically filter fields with “password” in the name, not all do! Who knows if this is it, but there are certainly a bunch of ways with infinite middleware layers, dozens of intermediary proxies handling request data, etc.
-
-
I hope that they provide some insight into that.
-
-
-
Does anyone know what they’re using for SNI?
-
-
As an American, I was really confused by the date of this article. I kept thinking to myself, “Wow, this post is from January and it just now made it to lobste.rs?” Then I clicked on the News homepage to see what other news they had, and promptly realized they’re using the European format (01.05.2018) on the article, but a less ambiguous format (May 01, 2018) for the News homepage.
-
-
YYYY-MM-DD is the one true international date format! :-)
DMY is definitely more widespread than MDY, I’ll agree, but it isn’t used in most of East Asia, besides the US. People in countries that don’t use either of those often find it ambiguous whether a year-last date was intended as a “European-style” or “American-style” date (which in my limited experience is what Japanese and Chinese call those two formats), since both styles are foreign. You can even find examples of all three styles on Chinese universities’ English-language pages…
-
Going by
user population size, by international standards, and by rationality (sort lexicographically!), YYYY-MM-DD is probably the only format that deserves to be called international. It’s also much less ambiguous than month-first and date-first, given that the US and Europe do the opposite thing but write it the same way. I suppose someone could write YYYY-DD-MM but I don’t remember having seen this, while I definitely am confused about whether someone is writing in the European/US style from time to time.This is as an American, born and raised. :) I still prefer to write MM/DD, though, because we speak dates that way. Maybe it’s different in other languages.
EDIT: Actually, according to Wikipedia, DMY is used by the most people! https://en.m.wikipedia.org/wiki/Date_format_by_country
-
Other than ISO 8601, I prefer DMY with the month written as a three-letter abbreviation. ex: 01 May 2018. It prevents the confusion over whether 01 is the first day of the month or the first month of the year, and reads in the order one typically cares about while preserving the rank order of the components. When I need a checksum I put the day of the week in front: Tue 01 May 2018. That lets me be confident I didn’t make a transcription error and lets the person I’m communicating with check my work if they need to.
-
-
MDY and DMY are equally unambiguous when the month is written as an abbreviation, but a numeric month papers over language differences: It doesn’t matter if you call it “Aug” or “八月”, it’s 8.
(That requires everyone to standardize on the Hindu-Arabic numerals, but, in practice, that seems like it’s happened, even in places which don’t use the Latin alphabet.)
-
-
In Hungary, though we are in Europe, we don’t use the “European format”. The hungarian standard format is “YYYY. MM. DD.”. I prefer the ISO format for anything international, as it is easy to recognize from the dashes, and avoids confusion. (In my heart I know that our format is the one true format, but I’m happy the ISO has also recognized it! 😉)
Edit: To me the D M Y format can be justified, though for me Y M D seems more logical. (specifying a time instance from the specific to the generic, or from the generic to the specific range can both be ok) What I cannot grasp is how the M D Y format appeared.
-
What I cannot grasp is how the M D Y format appeared.
The tentative progression I pieced together last time I looked into it, though note that this is definitely not scientific grade historical research, is something like this:
-
When talking about a date without the year, English has for centuries used both “May 1st” and “1st May” (or “1st of May”), unlike some languages where one or the other order strongly predominates. Nowadays there’s a strong UK/US split on that one, but in 18th-19th century England they were both common;
-
it seems to have been common for authors to form a fully qualified date by just tacking on the year to however they normally wrote the month/day, so some wrote “May 5th, 1855” and others “5th May, 1855”;
-
fairly early on, the “May 5th” and “May 5th, 1755” forms seem to have become dominant in the US for whatever reason; and finally
-
much later, when writing dates in fully numerical format became a thing, Americans kept the same MDY order that they had gotten used to for the written-out dates.
-
-
-
-
-
-
As an Australian, I get pretty annoyed every time I read a US article and have to deal with the mental switch. Even worse because I work for a US company and people throw around “we’re doing this 6/5”, and that doesn’t even look like a date to my eyes — we never just do D/M, so “number/number” looks like a fraction. once I work out it’s a date, I realise it’s an American thing and realise it must be M/D.
-
-
-
-
-
I thought it would actually be about
std::optional, not workspace issues that have nothing to do with the problem at hand.TL;DR: keep your toolchain up to date if you want to use recent language features.
-
-
-
-
-
-
Hmm as a full-time Haskeller “don’t use pattern matching” is news to me. Do you mean “don’t use pattern matching for fundamental vocabulary types like
MaybeorEither? In which case it’s a reasonable guideline. For types representing your business domain, pattern matching is perfectly good practice. IMHO exhaustiveness checking of pattern matching is an indispensable feature for modelling your domain with types. -
-
-
-
-
-
-
-
-
Nobody likes typing Float::INFINITY or 1.fdiv(0) over and over.
uhhhhhhhhhhhhhhhhhh
this seems dangerous
-
-
From a comment:
let gopher stay simple
This. I see interest in Gopher again, but they way they talk about it, they want to talk shit on like Markdown (read; HTML) parsers and essentially turn it into the web over port 70; all because the web sucks. (It does though, so I’ll give them that.)
Gopher’s strength and charm (why we talk about it in the endearing sense today) is its simplicity. Basically having something like the web just without HTTP isn’t very interesting after all.
-
There’s some good threads on this on gopher phlogs arguing over what “simple” constitutes, what makes sense as a natural extention of the protocol and what feels like reverse engineering the web. The way Alex’s wiki page on encryption started feels very much like the latter to me. It was too much as soon as he started talking about adding persistent connections, which undermine the core principle of gopher. He eventually settles on adding TLS, though, which I think falls into a more natural fit. It’s easy to implement on both client and server and can fall back easily enough. It doesn’t fundamentally change the way you interface with gopher, just makes sure that anyone listening in the middle can’t read along. I like it!
-
-
-
I still maintain that the most gopher-ish way to support encryption is via public anonymous gopher proxies which take requests over plain gopher, encrypt them, and tunnel them to an exit node on the other side.
This means:
- no existing clients need to be modified – even netcat still works fine, and produces plaintext results
- the IP a request comes from is known only to one of the two proxies
The mechanics of implementing the encrypted gopher proxies is beyond me, unfortunately. (I made an attempt, but ultimately couldn’t figure out the tooling.)
-
-
-
It is very likely that AWS, or Linux, or many other services/projects are used by governments for doing bad stuff. I don’t understand what is so different in this case.
-
-
-
-
Thanks for the reply. I read the article couple more times but still don’t see the connection.
As far as I understand, if you use AGPL there are thousands of companies who won’t use your library either.
The author’s open source projects don’t seem to be directly used for drone technology, either. Even then their argument looks weak to me.
I support protesting Google for their actions in involving in immoral projects. And I appreciate the author of this article for suggesting one another way to do that but it looks a very weak one to me.
-
I support protesting Google for their actions in involving in immoral projects. And I appreciate the author of this article for suggesting one another way to do that but it looks a very weak one to me.
I certainly don’t disagree that its persuasive power is low; I only argue there’s a big difference in “participating in directly aiding an morally defective project (like reCaptcha hypothetically asking you to select drone targets) with ones own abilities (human image recognition)” and “using a service or project (like AWS) that is also used by morally defective actors (like governments)”. The latter is impossible to avoid (like taxation, as @rama_dan points out), the former possible.
-
-
-
-
There are a few reasons for me clinging to MacOS for work (I’m a network engineer, and I code a bit too). The overshadowing first reason is called Microsoft Office. I wish I didn’t have to use it, but I have so far not been able to properly dodge it and my current employer is entangled beyond belief in the whole Microsoft ecosystem with OneDrive, Teams, Yammer, OneNote et. al. that I’m aware of nice cross-platform replacements for, but stuck with.
Similarly, I’m depending on OmniGraffle to display and create visio (compatible) drawings.
So why not just run Windows? Well, I had a go at that although not by personal choice when I started my current employment half a year ago, where I was handed a mediocre HP laptop while waiting for my Macbook Pro to be available, and it was quite terrible to work with. It became bearable when I had my emacs setup tuned, and I could sort of live inside emacs, but it was a poor substitute for the terminals and unix tools I’ve come to depend on.
Another reason, and that may just me being scared from previous experience running Linux for work, and that’s the whole multiple display thing. I have multiple displays at my home office at different rotations, and a widescreen monitor at work. Switching between multiple displays was never painless when I ran Linux, but that may have improved since then Still the point about different DPIs have been raised elsewhere here, so I believe it at least partly still applies.
And then there’s stability. It is entirely possible to have a stable Linux environment, but not perpetually. Something will break between releases and you’re forced to tinker and be unproductive. I enjoyed that part when I was younger, and I still do for my hobby systems. But for work, I just want things to work.
-
Multi monitor is definitely why I stay on OS X. Perfect it is not, but as someone that has hand edited x.org files in the past, i’ve never had a great experience with multiple monitors.
And osx with nix basically solves all my needs for a unix os. I get emacs and anything else out of there.
If I were to switch to linux on the desktop it would probably be nixos, least then I can easily move between stable islands of software at once with sane backing out of things.
-
-
Mostly plugging things in and having the window layouts work sanely. Also at issue tended to be putting the laptop to sleep and unplugging the monitor and not having anything come back up until I rebooted the laptop etc…
In a nutshell, edge cases all over, not that osx doesn’t have its own similar problems it tends not to lose the ability to display a screen.
-
-
-
Multimonitor support is 90% of why I’m planning to test drive moving away from OSX back to windows :)
-
-
-
I get all my windows moved to one monitor 95% of the time the displays come back on, and there’s a bug in the video card driver (Mac Pro Toob) that crashes everything on-screen (except the mouse pointer) and also crashes displayport audio, but leaves every application running as if everything were peachy. That one gets me every few weeks or so.
Also, I used to run 2 * UHD displays at 60hz, a third at 30hz. But now I can only run one at 60hz, both others run at 30. It’s fucked and it shits me to tears. When I bought it this was the top-shelf you could get, and while I cheaped out on core count, I went for the higher-end video option.
-
-
-
-
I predict some ppl will get overexcited & start rewriting
That really kind of put me off the article… I’ll read it, but I really don’t believe such SMS speak is appropriate for a blog post.
-
-
-
I just figured OP meant Probabilistic Programming Language.
-
-
-
-
kivikakk
GitHub Developer
5 months ago
|
link
| on:
GitHub Survived the Biggest DDoS Attack Ever Recorded
The funny thing was, most engineers at the company (myself included) had no idea this happened until people started linking this article in chat! Amazingly well-handled by our SRE team.
-
zpojqwfejwfhiunz
5 months ago
|
link
| on:
C++ Exception Handling - The gory details of an implementation
In the story submission guidelines:
When submitting a URL, the text field is optional and should only be used when additional context or explanation of the URL is needed. Commentary or opinion should be reserved for a comment, so that it can be voted on separately from the story.
-
-
Abstracts, link to other forms of same submission, Github, and so on have all been favored by Lobsters in votes or comments so far. If anything, we might need to update the guidelines to get it up-to-date on that. Far as abstracts, that’s also a time saver for readers where they can invest just a few seconds in deciding whether to invest a lot more time in main content.
-
I’ve no problem with the abstract, I’m just not clear that the submitter is the author. (Is the submitter Peter Edwards?)
-
(n00b OP here) I wasn’t sure if I should add the abstract and slides in there, since they are just copy / paste from the video description, but considering the replies, I’ll keep doing this. I think it helps people decided if they should spend an hour watching a presentation or not :)
-
-
Fun fact: GitHub once had a
humans.txtthat was generated from staff users’ profiles.Does anyone know why they stopped?
Privacy concerns. Not all staff wanted to broadcast the fact that they worked for a particular company. It also got a bit unwieldy as our numbers have grown.