Amulet of Yendor
I got Amulet of Yendor in Pixel Dungeon!Show all 6 replies
yeah those damned kung-fu dwarf monks usually take me out. I did get past them once to that dwarf king boss and stupidly followed the sign leaving my weapons outside, even though I thought it might be a trap
yeah it was anti-newbie trap, there goes the best character I ever had
Someday, when I find Acme Inc. offering a new wonderful free service, I read their terms of service: "...General Public Terms of Service, Version 1, 3 March 2018, Copyright © 2018..." and I say: "Yes! I know this. I know what I can expect from them, and I know what they can expect from me. I can accept that."
Stephen Sekula likes this.
"…you will find some FOSS geeks on there…"
A quote from Linux Voice issue 021 (December 2015), page 19:
“For something more Twitter-esque, try Pump.io (https://pumpit.info), another distributed social network that’s a continuation of the once mildly popular Identica network. Pump.io’s userbase is very small in comparison to Twitter, but you will find some FOSS geeks on there and it has the potential to grow into something much bigger. ”
uıɐɾ ʞ ʇɐɯɐs likes this.
Claes Wallin (韋嘉誠) shared this.
>> Timo Kankare:
“[...] a continuation of the once mildly popular Identica network [...]”
Identi.ca was never, and still isn't, a network. it was a single server in the decentralized StatusNet network, and now it's a single server in the decentralized Pump network.
And I'd certainly wouldn't call Pump.io "twitter-esque"...
Viikon VALO #244: Linux
“Linux on suomalaisen Linus Torvaldsin alulle panema UNIX-tyyppisen käyttöjärjestelmän ydin. Sen julkistamisesta tulee 25. elokuuta 2016 kuluneeksi 25 vuotta. Sen jälkeen Linux on valloittanut maailman puhelimista ja reitittimistä palvelimiin ja supertietokoneisiin saakka. ”
sazius likes this.
2016-08-11T13:22:31Z via Pumpa CC: Public
I just checked. There is not Windows 10 downloaded to my disc. (I guess it is not available in Debian repositories, not even in non-free part...)
I plugged a new printer to computer with USB cable. Then opened Cups admin page and selected "add printer", then selected local printer. The model list did not contain the name of the printer, but I selected one of the models which had text "recommented" in its name. Then printed test page. Perfect! It was not hard.
How about scanner? I opened scanning program. There was scan button. I clicked it and the printer (I mean scanner) scanned the page. — Somehow I expected I had to fight more to get scanning to work.
Well. It is year 2015. This is how it should be.
(as a reference: Debian testing/stretch, Samsung C460W)
Some thoughts about groups in pump.io.
Group whould hava an ordinary pump.io account. So people can follow the group, and post (or share) notes to the group (to or cc).
Then there could be a special client (groupbot). When somebody sends (or shares) a note to group, groupbot whould share it with the followers. This would be the simplest case.
If there is need for acceptance for the group member, group owner (account owner) could create a pump.io list named "members" and manually add the accepted follewers to the list. Then the groupbot whould share the posts to the members (not followers).
If there is need for the moderation, group owner could create a new list, named "moderators" and add moderators to the list. The groupbot whould share the posts first to the moderators, and if a moderator (re-)shares the post back to the group, then groupbot shares it to members.
This could work as a prototype for the groups. It would not need modifications to current pump.io server implementation, only some kind of groupbot implementation.
Well, actually, I am not expert in pump.io, so I don't know if it would work... Would it?Show all 6 replies
It seems I am not alone with these thoughts. @Laura Arjona indeed has same idea.
@mnd, I had to look that issue. I read it quickly but I must read it again (and mayby again) to understand details.
@Debacle, thanks. I have missed that post although I am following you.
Issue #1027, that I refer, says that you can not comment messages which no one user from you server directly get when message was posted.
It means that if you get a shared message from group-bot when you (or anybody from your server) does not follow message author directly, than you can not comment this message.
There is more work done and ongoing in the Pump.io core than you might realize. The problem is completing it. But some of the functionality of groups can actually be used already.
Somebody here won the lottery and can send loads of cash to Evan? =)
Douglas Perkins likes this.
Share to whom?
When I press share button in pump.io client, to whom is the note shared? Can I someway specify that the note is shared to this and that people or list?
JanKusanagi @i likes this.
cmhobbs shared this.Show all 6 replies
That's a good question. I think sharing is just another action in pump.io, like posting, liking etc. So probably clients could allow you to select to whom you are sharing. I should investigate this when I have time... :-)
Of course it raises some issue that you can share a private post with "Public", i.e. post it to the rest of the world. At the very least the client should warn you if you do that so you don't do it by mistake.
OK, I added it to an old feature request for Pumpa: http://pumpa.branchable.com/bugs/Allow_public_sharing/.
Sharing without specifying recipients, as with many things in pump.io ATM, defaults to "CC:followers".
“That's a good question. I think sharing is just another action in pump.io, like posting, liking etc. So probably clients could allow you to select to whom you are sharing. I should investigate this when I have time... :-)
Or has any of the other client devs already looked into this?”
AndStatus shares to Public (as with many things it does to Public, but they're fixing that now, I think...), so we know that addressing a share works.
“Of course it raises some issue that you can share a private post with "Public", i.e. post it to the rest of the world. At the very least the client should warn you if you do that so you don't do it by mistake.”
Well, it's actually close to the current problem, where you can happily share with all your followers a very private message, very easily.
I'd say sharing a non-public message shouldn't be allowed, at the server level.
That being said, having the possibility of "sharing to especific people" is on my TODO list for Dianara, but I also might limit it to public posts. That brings a different set of problems, because if you see a post via someone sharing it, your client can't know if it was public...
jpope likes this.
What are lists in pump.io? I guess they are not !groups (like in statusnet). Is there somewhere description about them? How to use them and what purpose? Are they public or can they be private?
Say you create a "Family" list, then add your parents, siblings and some cousins to it.
Then, when posting, you can post to "Family" instead of "Followers" or "Public", and have the message addressed to them only.
It's almost the same as adding all of them manually to the "To" list when posting, but a lot faster.
And yes, they are public, and, AFAIK, can't be private ATM.