It's pretty straightforward: you either click on their profile or (if you know someone's username@server via some other medium), search for them on your 'home' server and you'll see their profile. Then just click the 'follow' button.
Under the covers this sets up the federated follow relationship, but the UX feels the same as following someone on twitter.
There is one slightly more complicated scenario; if for some reason you're exploring a different server and find someone there you want to follow. In that case you still click the follow button but have to provide _your_ username@server string which triggers the necessary back-and-forth to get the follow relationship set up.
That makes sense, but my case is before I know who to follow. Is there any way to explore what’s going on on a server? Like browsing a news group on Usenet or checking a subreddit before subscribing?
> Like browsing a news group on Usenet or checking a subreddit before
How would you do that on Twitter? Follow the hashtags. Why do you insist on limiting it to a server? That's not really how it is supposed to work anyway, it's not those things you mentioned.
But how do I know what hashtags are there? I don't know what to follow is my issue. I need to bootstrap my set of followed things and people and how do I do that?
If you're not a part of some clique that decides to move off Twitter together, then I doubt you'll be able to just recreate a similar environment.
Otherwise for someone who posts frequently and has a good following, then it's probably worth it to start posting on Twitter and Mastodon at the same time, that's the only way it happens. Big movers and shakers are either going to stay on Twitter or drag everyone else with them, basically unlikely to happen.
Skyscanner | London, Barcelona, Edinburgh, Budapest, Sofia | ONSITE, VISA | full-time senior hires
We're one of the biggest travel metasearch products in the world by traffic... and we want to 10x that :)
Hiring at mid to senior levels in lots of key disciplines: backend with microservices & distributed systems, big data & data science, full stack and frontend, designers, product, iOS & Android. We are growing in all of our European offices - in particular, London and Barcelona.
Our tech stack includes Java and Python for backend microservices, JS (React) for frontend, and we're deploying with Docker and Kubernetes on AWS. If you're experienced in these technologies, you'll find interesting challenges to work on and solve, as part of a great team.
I've been here for a year (one year today!) and am really enjoying the breadth and depth of the work, the quality of the people, and the amount of care that the company takes to give us a comfortable and productive working environment.
You can see our current open roles and apply at http://grnh.se/jitlcd1 - or ping me an email at richard (.) north [at] skyscanner.net for a referral. I'd be very happy to answer questions or pass you to someone who can.
I use the Chrome and Firefox docker-selenium containers in Testcontainers [1][2], my project for running containers to support JUnit tests.
I created this after numerous issues with PhantomJS compatibility and debuggability; Testcontainers instead uses the real browsers, and also offers automatic video recording of test sessions and VNC access for debugging.
Headless chrome support sounds like a good step forward, but if visibility into what's going on is limited then I feel there's going to be some way to go. Perhaps chrome remote debugging support?
Developer here! This library arose out of frustration with running Java tests that had some kind of non-Java dependencies - e.g. databases and web browsers for UI testing. Testcontainers lets you add Docker containers to your tests, linked to the lifecycle of the test rather than having to be externally managed from the outside. I've found it useful, and hope others do too.
A few blog posts outline some of the ways the library can be used:
* JUnit integration testing with Docker and Testcontainers [1]
* Fun with Disque, Java and Spinach [2]
* Better JUnit Selenium testing with Docker and Testcontainers [3]
Specifically about this issue, see the section about the MongoDB oplog further down in the article. This removes the polling interval/overhead, so should significantly improve performance and responsiveness.
Ok. It indeed seems to be the case that the polling delay can be eliminated. But I'm wondering, if db-changes are written to the client directly, is it still possible to apply security rules to that? Evidently, I don't want all my db-changes to be written to all clients, and, preferably, a security-filter should be able to determine which clients receive which updates.
Yeah - the very earliest preview versions of Meteor had this obvious gap where reads and writes were basically a free for all. However, it's changed a lot since then. As a development crutch the aptly-named 'insecure' package is installed by default (which maintains the free for all), but you're expected to remove it and able to apply fine-grained control to which clients can C/R/U/D which data.
Over time I know the term 'native' has been used for many things, but I'm pretty sure the most recent peak in usage started with the iPhone SDK, where it meant 'apps which aren't based on a web browser'. Since then, I've wanted _so much_ for web technologies to become the best platform for making apps, but the hard truth is, they're not. With 16 years more web experience than iOS, I'd still rather shoot myself than use web technologies to make an app with the same UX quality, maintainability, and development time I can achieve natively.
I'm pretty sure the native vs hybrid argument has been settled - for now, though I'm always keen to see new developments.
Seeing software vendors and articles like this pushing to use the term native to describe _the very thing which is not native_ seems a little sad and desperate at best, and an attempt to confuse at worst.
As an Android dev, I concur, native apps are the ones developed with the platform sdk.
And yes, for now, the debate also seems pretty much settled to me.
For testing ansible playbooks/roles in a vagrant VM, I find a simpler way is to use Vagrant's built-in support for Ansible as a provisioner.
This way, launching your test VM is just a `vagrant up` and running ansible against it (repeatedly, if needed) is `vagrant provision`. No need to pass inventory/key parameters at the shell this way - Vagrant calls Ansible with the right settings.
One thing that's easy to miss is to make Ansible use sudo when running against the Vagrant VM, since the vagrant user by convention has passwordless sudo rights (ansible.sudo = true in the Vagrantfile).
The use case which this really excites me about is automated testing from the GUI level. If the performance is good enough, this would be really useful for restoring DB state in between tests.
While doing single restore is fast enough, you will have problems doing multiple restores in a row as the background process needs to finish before another restore is possible (which may take several seconds when you are dealing with big databases).
Under the covers this sets up the federated follow relationship, but the UX feels the same as following someone on twitter.
There is one slightly more complicated scenario; if for some reason you're exploring a different server and find someone there you want to follow. In that case you still click the follow button but have to provide _your_ username@server string which triggers the necessary back-and-forth to get the follow relationship set up.