Software developer from Russia who's almost lost faith in the modern IT. Used to work at VKontakte, then Telegram. Currently building my own fediverse project to save our online social lives from greedy corporations. Follow the progress: #smithereen
I want an opinion. If you have a rule to not allow signups with some email domain, would you expect it to also apply to signup requests, when your server is in manual-approval mode?
Not "expect" directly.. Ideally I would want to have a) clear knowledge of the behavior, b) be able to inform myself about its effect (e.g. see log or alerts), and c) change a setting that allows me to override the rule in manual-approval mode.
Question is what should be default behavior. Say I launch a server exclusively for journalists, set a rule to block yahoo.com ('not trusted') and no manual approval. The time I find a 100 blocked journalists, is when I already lost them.
Mark that domain as suspicious so I take more time with this signup request.
And a third option: make signups open, except for the domain.
The second and third option require different UI and are technically specialized lists for different purposes than simple blocking. So I would answer with the first option.
Is there an #ActivityPub server where I need to parse HTML for <link type="application/activity+json" href="..."/> to get to the JSON representation of an object? I want to add support for this in #Smithereen but I need something to test against.
Can anyone recommend a free, preferably open-source, stock-looking launcher for Android that has usable pages on *both* sides of the main page? Like it used to be before Google Now was introduced (which was wonderful until someone totally ruined it with news to get promoted).
What's the thing lately with this insistence on writing proper names starting with a lowercase letter? As someone for whom English is a foreign language, I sometimes struggle to discern whether a word is a word or a name. Capitalization helps with this quite a lot. (Though in this particular case, they at least say it should be in italic, although there are many places that don't support/allow text formatting)
Making your beta-quality software available to the open internet has one good thing about it: someone, at some point, will abuse it so much, that all resource leaks you have will be exposed and will cause trouble.
It turns out I was leaking database connections while getting post likes. I don't know what it was, probably a crawler of some sort, but I had everything break with "too many connections" from MySQL every hour or two, which forced me to investigate this ¯\_(ツ)_/¯
UX tip of the day: people typically don't open your app simply because they are bored. They open it with a concrete goal in mind, and you're getting in the way with your cutesy "what's new" and "rate us" and "please update" and other similar forcibly-context-switching crap.
Brought to you by me running an instance of IDEA with default settings to debug my plugin, but mobile apps do this way more often and way more obnoxiously.
— We're on a decentralized microblogging network open to everyone, owned by no one! Finally! — Hi all, I used the open protocol of this network to bridge it to another network that would also soon open up to everyone. — No! Not that kind of open! You can't do that!!!! I did not give you consent to publicly rebroadcast my public posts! How DARE you!
By the way, it also helps to know how ActivityPub actually works. In most cases, your posts don't even reach a server where there's no one following you.
@grishka Do you think threads will also adopt a kind of one way support? it seems like they only talk about posts being seen outside the threads network. and not about fediverse posts seen from threads.
I like my approach with deactivation period better than what others do. For example, @pixelfed deletes accounts immediately and it turns out people change their minds on this stuff sometimes.
@grishka@smallcircles@pixelfed Might be an idea to give the option of immediate deletion should the person want it. An unchecked checkbox, maybe. Always good to let the person in question have full control over what happens to their data.
Oops, I broke everything on grishka.me because I initiated its transfer to a cheaper registrar last week and it only actually transferred today... and the NS records carried over. Pointing to servers that no longer know about this domain. Fixed them now, but I wonder how long the cache invalidation would take.