gmemstr

Author here, happy to answer questions :)

You're likely thinking of Anubis from Techaro: https://github.com/TecharoHQ/anubis

Author here - yes, I know about robots.txt! This is one of those cases where, because I was already looking at data in one place, I implemented the fix I could in the same place :p I do plan to add a robots.txt and contribute one upstream as well.

Maybe not wise to post here yet as the docs mark this as a private alpha.

I wrote about this pretty recently, but the short version is a mix of NixOS and a k3s-based Kubernetes cluster using Tailscale to connect everything together.

https://gabrielsimmer.com/blog/infrastructure-megaupdate

Isn't this just email?

Taildrop (https://tailscale.com/kb/1106/taildrop/) mostly filled this for me, although this is just for the same Tailnet. AirDrop is also pretty slick. Otherwise I chuck it onto my NAS.

Of course all of these solutions have some serious pre-requisites...

The TL;DR is there isn't much difference besides the protocol being used. Tailscale published their own comparison that seems pretty fair to both sides (they do this for a few other options as well) https://tailscale.com/compare/zerotier.

And I /just/ got my infrastructure bits and pieces running Litestream! Guess I'll have to figure out if it's worth switching to this -- my gut reaction is no, since I only really run one pod at a time, so Litestream serves the purpose of not only saving the database offsite but also restoring it. But I will be keeping a very close eye on this thanks in part to my love of SQLite.

Hats off to Ben and Fly.io, you're doing some cool stuff.

As an ex-CircleCI employee, this is really exciting because it marks a pretty significant milestone in a particular internal effort. Very much looking forward to what comes after this.

This might strike some as a weird event (Gitlab already has CI/CD!), but it _was_ highly requested and is (probably) of other similar things coming to fruition!

_Is it_ up to Mojang/Microsoft to police this? Most multiplayer activity takes place on third party servers (I'm pretty sure this is the case for their Bedrock edition as well as Java edition), which have their own teams of moderators and administrators, or are small and private. Not quite sure how phishing etc. plays into this.

It's interesting to read the proposed "SoftOps" approach - it's something I've been trying to do in my own little bubble, working on making the lives of developers easier (especially when getting their code from repo to prod), with the developers creating systems. I volunteer for a convention run entirely within VRChat, with a handful of supporting services (API for tracking players, instances and registration, frontends for admin and attendees, and so on), and while the department is named "DevOps" (too late to change it, and everyone knows what we mean), I landed on the infrastructure subteam. While part of the job was building out our new Kubernetes cluster (mostly for scaling. I'm still working on the blog post about this sort of stuff), I wanted to make sure that the developers could be completely abstracted away from _where_ their code was running, and as much as possible _how_. Of course, they're free to mess with whatever tooling I setup for them (mostly Docker images, GitHub Actions, etc), but I've found it very fulfilling to "exist to serve" (because infrastructure? servers?) the developers pushing out code. If we need some custom internal tooling to support that development cycle I'm more than happy to get something written and deployed (something for the blog post). It may be barebones but I wouldn't stop a developer from another team contributing (provided they don't have something more pressing).

All this to say... I really like supporting developers in their work, as a sort of meta-engineer.

edit: worth pointing out I do something sort of similar at my current employer, but it lands a bit more on the type of devops that the author describes as having failed, and I'm actively working to see if I can find a position that better suites my skillset!

This poll is really me being curious about what the citizens of HN use themselves. My own use case would benefit greatly from CI/CD pipelines, but beyond that I'm mostly looking for a nice web interface to expose the repository contents.

I find it particularly amusing that they're reintroducing the 512MB of memory tier, but at $4 instead of the $2.50 it was before the removal. But I suppose that's roughly inline with the basic 1GB/RAM droplet going to $6. I'm most interested to see how the managed Kubernetes offering changes shake out -- hoping I don't sense a migration in the near future.

I tried something similar with a project of mine[1], with a focus on API rather than frontend so I could build tailored apps for each device/user. At some point I should get around to finishing it -- I mostly focused on S3 and local filesystem compatibility, but being able to explore filesystems from other devices (maybe through an agent) is a neat idea.

[1] https://github.com/gmemstr/sliproad

https://gabrielsimmer.com

Plain ol' HTML and CSS, built off some components of the somehwat defunct Skeleton.css project.

While I love the idea, the requirement for Ubuntu means I can't contribute my compute though (and neither can any of the PC gamers with Windows machines, or anyone else on other distros it seems). As much as I would love to do this over mining a cryptocurrency (which I don't do in the first place), I can't.

It depends -- with a community build script, you're relying on (and trusting!) a third party to maintain it and not do anything malicious. Much easier to pay a few bucks for first party binaries. At least in my eyes.

Genuine question, what sort of risks are associated with running this on a typical residential connection?

It's a shame they've moved to a subscription model - I'm personally angling to get a development PineNote and invest time into developing for that. It's priced about the same as a reMarkable, but does include a stylus and case, so that's nice.

My biggest want is an open device - I was originally drawn to the reMarkable _because_ it seemed quite open, but this subscription model really makes me rethink things (with what I would consider "core" functionality, e.g syncing, locked behind a paywall).

Talk to your own legal counsel. End of story, really. Don't respond until you've had a chance to do that.

So, uh, what benefits does this offer over existing, usually CLI-based, solutions? As far as I can tell it's a rather simplistic GUI wrapper around a static site generator - running in Electron, no less.

I'm not trying to come off as snarky - I am genuinely confused what benefits this offers over Jekyll or Hugo.

To be fair to 1Pass, accounts also have a unique random account ID that is used in combination with email + password. But it does still kind of make you wonder...

So it's... selling randomly generated Minecraft worlds? I really can't wait for NFTs to die off. Good lord.

Makes sense, that's the portable version. Would be reasonable to package that all together.

Hate to break it to you, but in Brave's case you really can't. Their crypto and ad stuff is so ingrained in their codebase that you have to be pretty meticulous to wipe it all out on that level. https://github.com/brave/brave-browser/issues/14783

I've never heard of Syncany, but I took a similar approach for my personal file hosting application. I wonder if I could implement similar silly approaches to filestorage :p

That's not the issue here. The issue here is letting automated systems having final say on such destructive actions as terminating an account entirely, with no concrete way to appeal. From what I am aware of, few channels wrongfully suspended get reinstated through support but rather through public outcry on the likes of Twitter.

Can't run ads on them, and you risk lawsuits of all kind if you let people easily download copyrighted content. They aren't running a museum, it just happens to be the largest video sharing platform on the planet.

At some point you start to learn how mobs (creepers, zombies etc) spawn and their various behaviors, which you can exploit to set up farms to automatically harvest their loot. Some farms are incredibly simple, and others very complex, but the end result is roughly the same. Some can be adapted to also let you farm experience for enchanting. Admittedly it can break progression a bit when you have enough of them but generally one or two well optimized setups can produce a fair amount of resources.